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...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
04-09-2008
Filed under: sql server, package, profiler, ssis, xml, error log, 2005, information, warning, logging, event viewer
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...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
01-16-2008
Filed under: sql server, microsoft, error, kba, 2000, error log, 2005, stored procedure, linked server, aspfaq, issues
Recently got stuck with the stored procedure sys.sp_dbmmonitorupdate which is used to monitor the database mirroring session. As usual you could do using the GUI tool, but sometimes using TSQL methods is good enough to see what is happening on your system. On the system with SQL 2005 Service pack2 when...
The following pages were recently modified. Source: Knowledge Base Product: Microsoft SQL Server 2005 Enterprise X64 Edition, SQL Server 2005 Enterprise Edition & SQL Server 2005 Standard Edition Notification Contents: New and All Modifications FIX: You cannot connect to an instance of SQL Server...