Browse by Tags

There are lots of troubleshooting articles about how to diagnose connectivity problems when setting up database mirroring, especially errors such as these: Msg 1418, Level 16, State 1, Line 2 The server network address "tcp://mirrortest.com:5023" can not be reached or does not exist. Check the network...

Here's something which I've been looking at this week, surrounding the autoclose database option. When you restore any database to a SQL Server 2005 SP2 or later instance, you'll more than likely get errors of this nature written to the log. 2008-11-12 17:24:16.58 spid13s SQL Server has encountered 5...

Well if you do you should check out the blog of my colleague and Microsoft pool team partner Spike, who works in the SQL Support team here with me in Stockholm, but specialises in the area that we refer to as developer support. This is a very broad area and encompasses many technologies but to give you...

Here's another example of SQL Server producing a dump file which can help you diagnose critical problems. The scenario here is a a clustered SQL Server 2005 instance fails over and we need to investigate why. A good place to start in such problems (as it is with many problems) is to look into the SQL...

Here's something I was looking at yesterday which is worth a quick look. It's quite a common scenario and one that's relatively easy to address. Your SQL Server 2005 instance suddenly throws the following to the error log (apparently without warning): 2008-09-09 08:30:44.810 Server Using 'dbghelp.dll...