Browse by Tags
All Tags »
error log (RSS)
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
Read More...
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
Read More...
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
Read More...
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
Read More...
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 initialize Name
Read More...
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
Read More...
A common mistake by DBAs for missing to check whether all the functionality of tools are working when a SQL Server Cluster environment is setup, though you may not catch hold of few issues with basic failover/failback testing initially but when the application
Read More...
Few things you need to consider before letting the users use Reporting Services within a DMZ environment where the Servers are exposed to the INternet and to safeguard the servers from hackers. In this case you must be aware that SQL Server uses TCP port
Read More...
On one of the SQL Server instance recently we have been getting the following error: SQL Server could not spawn FRunCM thread. Error: 17182, Severity: 16, State: 1. 2005-10-30 15:35:44.79 Server TDSSNIClient initialization failed with error 0xd, status
Read More...
Got a distressed call from one of the database operators stating the error on the subject, instantly I suspect that the hardware of that server is not doing well. As the error ""Error 9003: The LSN(42:132:1) passed to log scan in database '<DBName>'
Read More...
This error started generating since last 2 days on a scheduled job that uses SSIS to import content from a flat file. Eventually we found that a derived column within the table and the flat file flow where dates in YYYYMMDD are changed to MM/DD/YYYY format.
Read More...
To my surprise a deadlock information is not logged on SQL Server log, after a struggle for half-day I found that the startup parameters were messed up! It may be usual practice by adopting [ ; -T1204; -T1222 (with blank after semicolon) ] that is what
Read More...
Interesting post in MSDN forums on the error: SQLServer Error: 15404, Could not obtain information about Windows NT group/user 'mydomain\myusername', error code 0x54b. [SQLSTATE 42000]
Read More...
What to do when you get the error specified on the subject above? You might get this error message from a job which will send email to an operator when it is completed. First thing to check whether a valid email has been mentioned in the operator. Also
Read More...
Can we change the location of SQL agent error log file after the SQL Server program is installed? Yes, i n terms of configuring a specified number of SQL Server Agent error logs, this is not possible. The default number of log files for SQLAGent is 9
Read More...