SqlServer-QA.net

Have you ever been in a situation that one of the database has been giving hard time!It may be the times that every DBA might go through this path without realising the root cause of the issue. The issue could be out of space on the drive where that database is located and further you might see the errors (may familiar to you):2008-11-08 ...

Log or trace of activities will help you to get detailed information on what's going wrong, that too very useful for ETL based processes. In this regard within SQL Server 2005 using SSIS you can enable such logging within the package's  runtime.   This will allow you to log the output to 5 providers, such as text ...

I was happy to see that February CTP for SQL Server 2008 was ready to download for use, in coinciding with my presentation in SQLBits I wanted to work my demos on this CTP release, nothing worked out successfully!! It is fair that new release will help developers and DBAs to test their solutions and get familiar with the next CTP of SQL ...

The message on subject is self-explanatory where your disk subsystem is referring to SQL Server that it is unable to cope up the demand.   Having AUTOGROW option enabled on a SQL Server database is a common setup that allows SQL Server automatically expands the database when additional space is required. Internally within ...

One of the client referred about the  error during the execution of Upgrade Advisor: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.    Initial thoughts lead to checking the SQL Server timeout setting which has been left with default value 0, also further ...

When SQL Server 2005 Management Studio's Object Browser shows the SQL Server Agent service with a red down arrow and the text Agent XP's disabled, the service is not started or disabled. This used to be a problem prior to Service Pack 2 for SQL Server 2005, obviously SQLAgent is important part of SQL Server tasks that you need to schedule on ...

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 ...

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 ...

Few times I get such error  Snap-in failed with a long CLSID string mentioned in the subject above. On this client machine previously I have SQL Server 2000 tools and recently installed 2005 version too, instantly error: Snap-in failed to initializeName Microsoft SQL Enterprise ManagerCLSID : {00100100-1816-11D0-8EF5-00AA0062C58F} Tried ...

You may be aware default 4 SQL Server system databases master, model, msdb & tempdb are created automatically when the SQL Server is installed. Those databases files can be located under default directory assuming C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data and when you look into this directory additional data file - ...