Viewing 15 posts - 676 through 690 (of 1,157 total)
To add to this, running:
msdb.dbo.sp_help_job
Errors out with:
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Does the...
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 14, 2010 at 10:41 am
Does the C drive has enough space? Also cleaning up the temp directory of the SQL Server service account should help.
It is usually located at
C:\Documents and Settings\[ServiceAccount]\Local Settings\Temp
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 14, 2010 at 10:39 am
There is some other process active on the database. You need to clear that connection before bringing the database into MULTI_USER mode.
I had discussed a similar issue here[/url]
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 14, 2010 at 6:19 am
I could not repro the issue on SSMS 9.00.4035. Which version of SSMS are you using?
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 14, 2010 at 5:53 am
Operating System Error 80 = The file already exists
How are you using xp_cmdshell? Can you please post the code snippet?
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 14, 2010 at 5:41 am
Open the Maintenance Plan
Click on "Manage Connections"
By default there will be a connection named "Local server connection"
Check if there are any other conflicting connections in the same window.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 14, 2010 at 5:18 am
You can find out which process is using that file. An example explained here[/url]
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 12, 2010 at 10:54 pm
2010-09-10 13:18:29.01 spid5 Starting up database 'tempdb'. 0
2010-09-10 13:18:29.21 spid3 Recovery complete.
The first line states that the tempdb is starting.
The second line states that the Recovery is Complete....
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 12, 2010 at 10:24 pm
Schedule a transaction log backup. It ensures that the Transaction Log size is under check and most importantly provides point in time recovery option.
Read this article[/url] for more information.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 12, 2010 at 10:17 pm
This discussion would answer your question.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 12, 2010 at 11:52 am
I have a SQL Server 2005, whose tempdb grows to 19.6G (which is very large in my case). I tried to shrink it, but failed. Although no one...
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 12, 2010 at 10:54 am
I second Derrick. Think there is a job which is trying to make the connection to SQL Server
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 10, 2010 at 11:51 am
Add an output file to the Job Step (under Advanced)
In the job script after each statemet (like -- Table to hold Price Changes etc.) add a PRINT statement like
PRINT 'Starting...
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 10, 2010 at 11:41 am
The error message is because some other user is already connected to the database. Try using ROLLBACK options, check for any open transaction or locks on that database. Even I...
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 10, 2010 at 11:14 am
Have you downloaded the correct version of SP3 installer?
Please confirm the SQL Server version by executing select @@version
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 8, 2010 at 11:24 am
Viewing 15 posts - 676 through 690 (of 1,157 total)