Home » SQL Server » Page 25

SQL Server

sql server DBA 999

SQL Server Error : 1941, Severity: 16. Cannot create nonunique clustered index

SQL Server Error : 1941 Details

SQL Server Error: 1941 Severity: 16 Event Logged or not: No Description: Cannot create nonunique clustered index on view ‘%.*ls’ because only unique clustered indexes are allowed. Consider creating unique clustered index instead. Severity 16 Description: Indicates general errors that can be corrected by the user.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE Read the rest

sql server DBA 999

SQL Server Error : 1940, Severity: 16. Cannot create %S_MSG on view ‘%.*ls’. It

SQL Server Error : 1940 Details

SQL Server Error: 1940 Severity: 16 Event Logged or not: No Description: Cannot create %S_MSG on view ‘%.*ls’. It does not have a unique clustered index. Severity 16 Description: Indicates general errors that can be corrected by the user.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL, NULL, N'asc'
Go

The parameters … Read the rest

sql server DBA 999

SQL Server Error : 1939, Severity: 16. Cannot create %S_MSG on view ‘%.*ls’ bec

SQL Server Error : 1939 Details

SQL Server Error: 1939 Severity: 16 Event Logged or not: No Description: Cannot create %S_MSG on view ‘%.*ls’ because the view is not schema bound. Severity 16 Description: Indicates general errors that can be corrected by the user.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL, NULL, N'asc'
Go

The parameters for … Read the rest

sql server DBA 999

SQL Server Error : 1938, Severity: 16. Index cannot be created on view ‘%.*ls’

SQL Server Error : 1938 Details

SQL Server Error: 1938 Severity: 16 Event Logged or not: No Description: Index cannot be created on view ‘%.*ls’ because the underlying object ‘%.*ls’ has a different owner. Severity 16 Description: Indicates general errors that can be corrected by the user.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL, NULL, N'asc'
Go
Read the rest

sql server DBA 999

SQL Server Error : 1937, Severity: 16. Cannot create %S_MSG on view ‘%.*ls’ bec

SQL Server Error : 1937 Details

SQL Server Error: 1937 Severity: 16 Event Logged or not: No Description: Cannot create %S_MSG on view ‘%.*ls’ because it references another view ‘%.*ls’. Consider expanding referenced view’s definition by hand in indexed view definition. Severity 16 Description: Indicates general errors that can be corrected by the user.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server
Read the rest

sql server DBA 999

SQL Server Error : 1935, Severity: 16. Cannot create index. Object ‘%.*ls’ was

SQL Server Error : 1935 Details

SQL Server Error: 1935 Severity: 16 Event Logged or not: No Description: Cannot create index. Object ‘%.*ls’ was created with the following SET options off: ‘%.*ls’. Severity 16 Description: Indicates general errors that can be corrected by the user.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL, NULL, N'asc'
Go

The parameters … Read the rest

sql server DBA 999

SQL Server Error : 1934, Severity: 16. %ls failed because the following SET opt

SQL Server Error : 1934 Details

SQL Server Error: 1934 Severity: 16 Event Logged or not: No Description: %ls failed because the following SET options have incorrect settings: ‘%.*ls’. Verify that SET options are correct for use with %S_MSG. Severity 16 Description: Indicates general errors that can be corrected by the user.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server messages in
Read the rest

sql server DBA 999

SQL Server Error : 1931, Severity: 16. The SQL statement cannot be executed bec

SQL Server Error : 1931 Details

SQL Server Error: 1931 Severity: 16 Event Logged or not: No Description: The SQL statement cannot be executed because filegroup ‘%.*ls’ is offline. Use the sys.database_files or sys.master_files catalog view to determine the state of the files in this filegroup and then restore the offline file(s) from backup. Severity 16 Description: Indicates general errors that can be corrected by the user.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the … Read the rest

sql server DBA 999

SQL Server Error : 1930, Severity: 16. Cannot convert a nonclustered index to a

SQL Server Error : 1930 Details

SQL Server Error: 1930 Severity: 16 Event Logged or not: No Description: Cannot convert a nonclustered index to a clustered index because a foreign key constraint references the index. Remove the foreign key constraint and then retry the operation. Severity 16 Description: Indicates general errors that can be corrected by the user.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog 0,
Read the rest

sql server DBA 999

SQL Server Error : 1929, Severity: 16. Statistics cannot be created on object ‘

SQL Server Error : 1929 Details

SQL Server Error: 1929 Severity: 16 Event Logged or not: No Description: Statistics cannot be created on object ‘%.*ls’ because the object is not a user table or view. Severity 16 Description: Indicates general errors that can be corrected by the user.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL, NULL, N'asc'
Read the rest