Check out this link on how to read the dump log. It might help you track down your problem child.

Check the dump log, and the server's event viewer. What are they saying?

The usual "fix" in SQL 2000 for me (when it came to problems like this) was re-initializing the...

It's been forever since I've used replication. I have this bizarre, vague memory that there's a setting in one of the properties windows that needs to be set in order...

I don't know if there will be a problem if you move your databases without changing your SQL Server install from 32bit to 64bit. Have you upgraded the SQL Server...

Check your server's Event Viewer for errors and warnings from around the time of this error.

Describ the steps you're taking to read the error log, please.

Also, is the log file hard drive full? Have you recently run a diskscan to verify all the sectors are...

Tara-1044200 (6/1/2010)

---

This disk is SAN configured with RAID5. I always think of keeping database files on multiuple drives hoping to have better performance but my network admin says that it...

So I guess the answer depends on how the linked server is setup. I'm betting the impersonate permission is causing your ability to use it.

Chances are your uninstall didn't uninstall cleanly or completely. Or the install upgraded a SQL Server component. I'd advise googling "Uninstall Deklarit" and see if you find any articles on...

I don't know what settings Marco used, but I created a Test sql account on a server, using Master as the default and granted no permissions.

The linked server does not...

mchofman (6/1/2010)

---

It is possible to run query at a linked server as another user with the EXECUTE AS statement. In the example below I login as user "Test" and I...

Every function included in a WHERE clause causes problems. It most instances, it can turn a...

If the database is case insensitive, do you know why the vendor put an UPPER() function in the WHERE clause?

If you don't have the auditing set up to keep this info, then there's really no way you can go back and find out who changed your server properties. Sorry....

Better method... Not really.

Simplier (and not recommended) methods? Yes.

1) Set all DBs to Single User mode.

2) Take all DBs offline (will have to click the "Disconnect connected users"...