SqlServer-QA.net

Linked Server errors, such as between SQL Server 2000 and 2005 versions are quite common in DBA-day life. When it goes wrong I would always refer (myself) and others to review HowDoI-PreventLinkedServerIssues resource from ASPFAQ site. Also the usual practice of checking of whether its a security issue to allow the logins, if so then goto ...

Very confusing error when trying to connect to a Database Engine (SQL Server 2008) using 'usual' windows authentication getting the following error:   A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other ...

SQL Server 2008 CTP5 is failed to install on Windows Server 2008 core, have no problem in Windows Server 2003. So whenever you have a problem in installing any edition of SQL Server it is better to refer to the log file that is used to log all the activities during the setup. In this case you will find more information by looking at ...

Imagine a simple installation of SQL Server Express 2005 edition fails with an error ''SQL Server service failed to start?'' Whether it may be on a X64 based operating system or on a simple desktop with XP PRO, as usual you would go with default install options. When the installation fais always best to check the error log for the reason ...

You may be aware that SP_READERRORLOG can be used from a query analyzer or query editor to read the error log contents without opening the file on the disk or from Management Studio (or Enterprise Manager). I'm not sure whether you have observed that there is a change in behaviour between SQL 2000 and 2005 versions. The problem here is ...