Viewing 15 posts - 301 through 315 (of 333 total)
SQL Server Dump can tell you what is loaded there.
May not be easy
February 14, 2006 at 12:10 am
SQL Edition doesnot make a difference.
It looks to me that file header is corrupt
sp_attach_single_file_db will work if files are taken out cleanly and it was "graceful" shutdown of SQL Server....
February 14, 2006 at 12:07 am
Returning result set makes a lot of difference.
If i understand correctly... Once request is reached to SQL Server it will process in same time (assuming same load)
February 13, 2006 at 4:49 am
One more logical reason of instance is as below:
MSDE is free version of SQL Server and used by AntiVirus software, backup softwares etc. Now, if there is no concept of...
February 13, 2006 at 4:27 am
Try workaround given by Crystal
'MYSERVERNAME\Administrator' is not having rights to login to SQL server
February 13, 2006 at 4:12 am
there must be a .txt file generated in the log folder. Please paste the content of that file
February 13, 2006 at 4:09 am
=======
Some DBAs recommend that you backup the T-Log after a full database backup. However, I don't understand why that may be necessary since the full database backup captures all the...
February 13, 2006 at 4:07 am
17883 is not so easy to debug. There can be many reasons of thread not yielding properly (in 60 seconds) I would recommend you to open a case with Microsoft...
February 13, 2006 at 3:57 am
February 10, 2006 at 7:34 am
1. create a login using enterpise manager.
2. Make him part of public role and give access to the database
3. Use below scripts
Grant select on <table_name> to <Login_Name>
Grant insert on <table_name>...
February 10, 2006 at 7:28 am
1. Who is the owber of the job? (Windows account or sa)
2. Whats is the startup account of SQL Server and SQL Agent?
3. By which account you connected to SQL...
February 10, 2006 at 7:17 am
Agree with Gordon.
OS level backup happening on the server.
February 10, 2006 at 7:10 am
Please post output of this file sp1_serv_uni.out. Below is the location on your machine.
C:\Program Files\Microsoft SQL Server\MSSQL\Install\sp1_serv_uni.out
It will give more clear picture.
February 10, 2006 at 6:59 am
I can think of below reasons:
1. Job is not scheduled to run
Below is the procedure which runs in background.
sp_help_job, this in turn executes below.
EXECUTE master.dbo.xp_sqlagent_enum_jobs 1, dbo
HTH
February 10, 2006 at 6:57 am
can you be more specific about "log files"? Is it transaction Log?
February 10, 2006 at 6:47 am
Viewing 15 posts - 301 through 315 (of 333 total)