Viewing 15 posts - 46 through 60 (of 153 total)
Another possibility is that the account that runs the SQL Server process has no write permissions on that directory.
January 14, 2004 at 7:52 am
It is in the registry:
HKCU\HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\80\Tools\SQLEW\Registered Servers X
If you have a roaming profile you get the same servers on every machine.
It is easiest to export from current user, logged...
January 13, 2004 at 7:49 am
I tried it some time ago and Xandermo's suggestion will not work. I guess it needs some registry entries, probably HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\Help.
I did not consider that practical and...
January 2, 2004 at 3:37 am
Alpha3300's query will not work when you are waiting for a latch or anything else that is not a lock, as there is no blocking sid.
You need:
select spid, lastwaittype, waitresource...
December 24, 2003 at 5:42 am
I tried it on SQLServer 2000 SP3, but can not reproduce it.
Could it be that in your version SQLServer believes that in Hungarian Y is not the capital of y?
...
December 22, 2003 at 9:04 am
Have your or those "hardware people" looked at the OS.
If Windows mixed up some files positions it might cause this error. A smaller file might remove the symtoms while...
December 9, 2003 at 8:41 am
A full backup does not decrease the logfile.
A log backup creates empty room in the logfile, which it fills first before growing again.
If you make no log backups set the...
December 9, 2003 at 8:23 am
I do not know about Enterprise Manager, but if the you change the password in the administrative tools or manage, password information on shares and some other stuff is lost...
December 9, 2003 at 8:04 am
You have two transactions that lock each other. You can find out the processes by setting flag 1204. Check the books online on tips how to prevent...
November 23, 2003 at 11:44 am
On NT and Windows 2000 you can use start /wait. (On Windows 2003 that is the default.) It is meant for windows programs, not command line programs and I thought...
November 19, 2003 at 9:22 am
mstask.exe *is* the windows task scheduler. I am 100% sure.
Apparently there is a schedule that runs runs "net stop mssqlserver"
Every time this task runs you get another windows.
(maybe...
November 19, 2003 at 8:56 am
This seems to be an index problem. Rebuild the index.
November 12, 2003 at 5:25 am
Vambati, you are wrong. 😉
As Nigel said, full backups and log backups are independent.
If you do a full backup you get a backup of the database as it...
November 11, 2003 at 2:17 am
I do not know if this is relevant, but you never know. I got the same error the first time using an sql script created by the profiler. ...
November 10, 2003 at 9:46 am
The timeout event mentions the spid. Look in the trace for the last statement from that spid.
October 24, 2003 at 6:18 am
Viewing 15 posts - 46 through 60 (of 153 total)