If you are Developer then debugging your own code is an usual practice and when you got used to perform the same on SQL Server 2000 version, it is not an easy way in SQL Server 2005 version. As you may be aware that SQL Server 2000 engine includes a debugger for stored procedures and not within SQL Server...
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...