Home » SQL Server Admin

SQL Server Admin

sql server DBA 999

SQL Server- Unable to connect to SQL Server Error 26

Error Description:

SQL server error 26- Unable to connect to SQL Express Error: 26-Error Locating Server/Instance Specified

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

SQL Server- Unable to connect to SQL Server Error 26

Error Details: this sql server error 26 error locating server instance message is often encountered when connection to a SQL Server is tried and don’t know where to start to solve the problem.

We get this sql server … Read the rest

sql server DBA 999

SQL Server Error : 129, Severity: 15. Fillfactor %d is not a valid percentage;

SQL Server Error : 129 Details

SQL Server Error: 129 Severity: 15 Event Logged or not: No Description: Fillfactor %d is not a valid percentage; fillfactor must be between 1 and 100. Severity 15 Description: Indicates syntax errors in the Transact-SQL command.

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 XP_READERRRORLOG are:… Read the rest

sql server DBA 999

SQL Server Error : 130, Severity: 16. Cannot perform an aggregate function on

SQL Server Error : 130 Details

SQL Server Error: 130 Severity: 16 Event Logged or not: No Description: Cannot perform an aggregate function on an expression containing an aggregate or a subquery. 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 : 133, Severity: 15. A GOTO statement references the label ‘%

SQL Server Error : 133 Details

SQL Server Error: 133 Severity: 15 Event Logged or not: No Description: A GOTO statement references the label ‘%.*ls’ but the label has not been declared. Severity 15 Description: Indicates syntax errors in the Transact-SQL command.

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 XP_READERRRORLOG are:… Read the rest

sql server DBA 999

SQL Server Error : 28201 Severity: 10. SQLSQM.EXE cannot be launched.

SQL Server Error : 28201 Details

SQL Server Error: 28201 Severity: 10 Event Logged or not: No Description: SQLSQM.EXE cannot be launched. This can either be caused if the required information in the registry is missing or corrupted or SQLSQM.EXE cannot be found. Severity 10 Description: Informational messages that return status information or report errors that are not severe. For compatibility reasons, the Database Engine converts severity 10 to severity 0 before returning the error information to the calling application.

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 … Read the rest

sql server DBA 999

SQL Server Error : 128, Severity: 15. The name “%.*s” is not permitted in this

SQL Server Error : 128 Details

SQL Server Error: 128 Severity: 15 Event Logged or not: No Description: The name “%.*s” is not permitted in this context. Valid expressions are constants, constant expressions, and (in some contexts) variables. Column names are not permitted. Severity 15 Description: Indicates syntax errors in the Transact-SQL command.

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
Read the rest

sql server DBA 999

How to Resolve SQL Server Error 5172 – Fix SQL Server Header Error 5172

How to Resolve SQL Server Error 5172 – Fix SQL Server Header Error 5172

SQL Server stores its physical data in the primary database file, which contains the data by pages which store data. The header information of a .mdf file is stored by the first page, called a header page. This page contains the important information of this database file like file size, signature etc…. When a user attempts to attach the MDF / LDF database file stored on their system, a message box appears “The header for the “databasename.mdf” is not a valid database file header. The FILE SIZE property is incorrect. (SQL Server error 5172). It occurs when the header information of a .mdf file becomes corrupted.

Read the rest
sql server DBA 999

How to check Deadlocks in SQL Server

What is a SQL Server deadlock?What is a SQL Server deadlock?

A deadlock in SQL Server occurs when 2 processes/sessions are competing for exclusive access to data in the tables but is unable to obtain exclusive access to it because the other process/session is preventing it. This results in a situation where neither process can proceed and gets struck. The only way out of this deadlock when happens is that for one of the processes to be terminated. SQL Server automatically detects when deadlocks have occurred and takes action by killing one of the processes known as the victim.
Deadlocks are not confined to table locks now but from SQL Server 2012 onwards it can happen with memory, Multiple Active … Read the rest

sql server DBA 999

SQL Server- Unable to connect to SQL Express Error: 26-Error Locating Server/Instance Specified

Error Description:

SQL server error 26- Unable to connect to SQL Express Error: 26-Error Locating Server/Instance Specified

How to fix SQL server Unable to connect

Error Details: this sql server error 26 error locating server instance message is often encountered when connection to a SQL Server is tried and don’t know where to start to solve the problem.

We get this sql server error 26 error message only when we are trying to connect to a SQL Server named instance.

Every time we try to make a connection to SQL Server named instance, we will send a SSRP UDP packet to the server machine UDP port 1434. We need this step to know configuration information of the SQL instance, e.g., protocols enabled, TCP port, pipe name etc. Without … Read the rest

sql server DBA 999

SQL Server- a network-related or instance-specific error occurred while establishing a connection to sql server

SQL Server- a network-related or instance-specific error occurred while establishing a connection to sql server

Error Details or symptoms: Can not connect to a SQL server and you get a error a network-related or instance-specific error occurred while establishing a connection to sql server

This error is seen in SQL Express installation as its installed a named instance by default with name of instance as Servername/SQLExpress.

Some other Errors Similar:

provider: named pipes provider, error: 40 – could not open a connection to sql server which is covered here.

provider: sql network interfaces, error: 26 – error locating server/instance specified which is covered here.

Resolution:

If we are connecting from Windows PC/Client to Windows server/SQL Server (server with SQL Server … Read the rest