Viewing 15 posts - 241 through 255 (of 395 total)
You could do it that way:
Start your day with pinging your servers first.
Place all your linked servers in a table like below on a master server:
Server_ID Server_Name Status
1 Server#1 ...
October 19, 2005 at 12:52 pm
If you have an access to the linked server, why don't you created a job, run it, save results to the table and analyze it....
October 18, 2005 at 11:40 am
Try to schedule reindexing on the weekend, putting your Database in simple recovery mode before that process.
October 14, 2005 at 11:54 am
I would suggest to replace
EXEC sp_dropserver 'yourServerName'
with
EXEC sp_dropserver 'yourServerName,'droplogins'
October 14, 2005 at 11:37 am
Sometimes you might need to insert few dummy records in your DB before shrinking....
October 11, 2005 at 11:15 am
see if this link can help you: http://support.microsoft.com/default.aspx?scid=kb;en-us;328551
October 10, 2005 at 11:42 am
see if this link can help you: http://support.microsoft.com/default.aspx?scid=kb;en-us;328551
October 7, 2005 at 11:57 am
Could be a little premature at this point, but anyway... Make sure that when you restart your machine, you have to restart your counters too!
October 5, 2005 at 12:01 pm
Just to add to the above:
Function can return only one resultset at a time. Stored Proc can return more than one resultset at a time.
Also Stored Procs support output parameters while UDF's don`t.
October 5, 2005 at 11:40 am
something like that:
Backup LOG Hr_database WITH NO_LOG
GO
DBCC SHRINKFILE ('Hr_database_log',TRUNCATEONLY)
GO
October 4, 2005 at 11:30 am
just to add to Remy:
When Drop server make sure if the Mail Profile has been dropped at SQL Server Agent
and check if this server has been dropped from Linked Server`s...
September 30, 2005 at 12:18 pm
Quick note, Cory: I thought you already have SP4 installed, since I recommended installing hotfix 944 otherwise earlier.
September 30, 2005 at 11:23 am
You might want to put your db in simple mode while reindexing, to avoid shrink log later...
September 29, 2005 at 12:18 pm
Ensure on Both machines: Administrative Tools -> Services.
"Remote Procedure Call" should be started.
SQLDebugger Account on the Server should not be Disabled.
Ensure SQLDebugger has "Log on...
September 28, 2005 at 11:12 am
Viewing 15 posts - 241 through 255 (of 395 total)