Viewing 15 posts - 7,921 through 7,935 (of 9,725 total)
Check out this link on how to read the dump log. It might help you track down your problem child.
June 2, 2010 at 10:26 am
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...
June 2, 2010 at 8:40 am
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...
June 2, 2010 at 8:35 am
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...
June 2, 2010 at 8:23 am
Check your server's Event Viewer for errors and warnings from around the time of this error.
June 2, 2010 at 8:22 am
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...
June 2, 2010 at 8:21 am
Tara-1044200 (6/1/2010)
June 2, 2010 at 8:18 am
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.
June 2, 2010 at 8:12 am
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...
June 2, 2010 at 8:09 am
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...
June 1, 2010 at 11:32 am
mchofman (6/1/2010)
June 1, 2010 at 11:21 am
mberry 51447 (6/1/2010)
somehow I dont believe that use of the UPPER function is causing this.
Every function included in a WHERE clause causes problems. It most instances, it can turn a...
June 1, 2010 at 11:11 am
mberry 51447 (6/1/2010)
Nope it is SQL_Latin1_General_CP1_CI_AS
If the database is case insensitive, do you know why the vendor put an UPPER() function in the WHERE clause?
June 1, 2010 at 10:55 am
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....
June 1, 2010 at 10:28 am
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"...
June 1, 2010 at 10:24 am
Viewing 15 posts - 7,921 through 7,935 (of 9,725 total)