Viewing 15 posts - 136 through 150 (of 1,160 total)
It is quite natural for the Transaction Log to grow during Rebuild index operation. Even if you implement log shipping, the transaction log backup will be *big* in size after...
January 5, 2011 at 9:42 pm
To add to the list, since you are using SQL Server 2008 you can make use of SSMS to run query against multiple servers by registering the instances....
January 5, 2011 at 12:20 pm
calvo (1/5/2011)
I found this link which may contain some possible answers for you.
The URL is hyperlinked to this forum post. Must be a typo!
This should be a good...
January 5, 2011 at 6:09 am
You can make use of -W switch in sqlcmd utility to remove the trailing space.
January 5, 2011 at 1:06 am
January 4, 2011 at 8:55 pm
You can double click on the column edge to resize it as seen in this screenshot.
January 4, 2011 at 8:52 pm
Brandie Tarvin (1/4/2011)
I overwrote the list with the account (because it's not on my box),...
January 4, 2011 at 7:07 am
Please check if the SQL Server instances was starting up when you saw the error message. You can go through the Event Viewer/SQL Server Error Log.
January 4, 2011 at 4:35 am
karthik.catchme (1/4/2011)
January 4, 2011 at 4:33 am
SQL Server "Alerts" can be configured to trigger when the Transaction Log is xx% full. As you mentioned, you have to write a custom script to meet the requirement.
January 4, 2011 at 3:18 am
Sumanta,
Are you able to connect to this instance using SSMS?
January 4, 2011 at 3:12 am
Does changing the job owner to a "sysadmin" login help?
January 3, 2011 at 8:14 pm
Did you click on "Remove Agent History" and click Ok. If yes, this will clean up history.
January 3, 2011 at 8:40 am
Hi Wallace,
You can query sysprocesses to check which session is currently active on that database and kill it.
January 3, 2011 at 8:24 am
SQL Server tracks changed data through Differential bitmap pages. Here is more information on it.
January 3, 2011 at 6:34 am
Viewing 15 posts - 136 through 150 (of 1,160 total)