SQL Server Cannot use the special principal ‘sa’. Microsoft SQL Server, Error: 15405
Cause of Error in SQL Server ” Cannot use the special principal ‘sa’. Microsoft SQL Server, Error: 15405 “ when importing a database in your SQL instance you would find yourself with Cannot use the special principal ‘sa’. Microsoft SQL Server, Error: 15405 popping out when setting the sa user as the DBO of the…
SQL Server error 18456 cannot connect – SQL Server 2017 LOGIN FAILED ERROR 18456
SQL Server error 18456 cannot connect – SQL Server 2017 LOGIN FAILED ERROR 18456 Normally error code comes up with a description that gives us a hint about what has gone wrong. But in this case of SQL Server error 18456 on screen, no cause of login failure is displayed. This is an intended development…
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…
SQL Server- Unable to connect to SQL Express Error: 26-Error Locating Server/Instance Specified
SQL Server- Unable to connect to SQL Express Error: 26-Error Locating Server/Instance Specified Error Details: this error 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 error message only when we are trying to connect to a SQL Server…
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…
SQL Server error 40 could not open a connection to sql server 2016
SQL Server error 40 could not open a connection to sql server 2016 Error related are: error 40 could not open a connection to sql server named pipes provider could not open a connection to sql server 53 invoke sqlcmd provider named pipes provider error 40 could not open a connection to sql server named…
What’s new in SQL Server 2017 vNext
What’s new in SQL Server 2017 vNext SQL Server 2017 vNext represents a major step towards making SQL Server a platform that gives you choices of development languages, data types, on-premises and in the cloud, and across operating systems by bringing the power of SQL Server to Linux, Linux-based Docker containers, and Windows. Microsoft announced…
SQL Server- Identify location of the SQL Server Error Log file
SQL Server- Identify location of the SQL Server Error Log file The SQL Server Error Log file is per SQL Server instance. A DBA can identify the location of the SQL Server Error Log file used by an instance of SQL Server easily. DBA can identify SQL Server Error Log file used by SQL Server…
Microsoft SQL Server Error: SQL SERVER – Msg 102, Level 15, State 1, Line 2 Incorrect syntax near ‘)’ or msg 102 level 15 state 1 line 3 incorrect syntax near ‘ ‘
Microsoft SQL Server Error: SQL SERVER – Msg 102, Level 15, State 1, Line 2 Incorrect syntax near ‘)’ or msg 102 level 15 state 1 line 3 incorrect syntax near ‘ ‘ Details of Error: This error message occurs if we use GETDATE() like function as a parameter to Stored Procedure or Function Statement.…
Microsoft SQL Server Error: SQL SERVER – Msg 8152, Level 16, State 14 – String or Binary Data Would be Truncated
Microsoft SQL Server Error: SQL SERVER – Msg 8152, Level 16, State 14 – String or Binary Data Would be Truncated Details of Error: String or binary data would be truncated. The statement has been terminated. This error message below occurs when part data is been truncated while loading a table. Actual error message: Msg…
