If reboot is involved, then you would need to do manual failover from primary to secondary before rebooting that instance. SQL 2005 and 2008 are update insensitive, thus windows update...

SQL running on single disk is not advised especially if its business critical. RAID is acceptable to some extent. If possible try adding an external disk for backups and transaction...

Linked server will serve you better. But as mentioned by others before, if the data is large, then it would be advisable to do import export.

This would mean that you need to use Degree's of Parallelism (MAXDOP). But it will complicate your code and has hardware dependency (multiple cores).

Check this to get better idea

Thanks Shifty1981..I did go through this thread and multiple other's to see if this process makes sense. Arguably, Max memory should be the upper limit. No matter how much we...

cheers Praveen

Exactly. Incase if you have VM's on your box, I would suggest atleast 6-7 GB buffer for...

Try checking out if the login that you are using has permissions for alter. Ideally it should have sysadmin permissions.

this should do you good. Lists only active users.

USE msdb

SELECT * FROM sys.dm_exec_sessions WHERE Status != 'sleeping'

This shall probably give you a better idea to whom to keep and whom...

+1 for adding a trigger to specific user. Ideally trigger should be based on sys.dm_exec_sessions.

To clear some air from the basic question

Target Memory = Memory available for the SQL server to consume and this sets up the upper limit. This also inturn means that...