January 11, 2011 at 3:45 am
Yes, you can do a backup and a restore without shutting down SQL Server.
For more information, see the following link:
http://msdn.microsoft.com/en-us/library/ms187510.aspx
Make sure to also check the references at the bottom.
How are you currently taking backups?
Regarding the RESTORE permissions, see the following URL:
http://msdn.microsoft.com/en-us/library/ms186858.aspx
See the section on permissions.
Regarding the data type question, maybe it is best to start a new thread in another forum (SQL Server 2005 Administering or SQL Server 2005 Strategies), since the question is not related to your original question and also not related to the backup forum.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
January 11, 2011 at 7:05 am
On #3, if you change the data type on existing data, you face the possibility of data loss, which, for most businesses, is a bad thing. So when do this sort of change, you always test it prior to running it on the production machine. For details on how to deploy to production, I'd suggest getting a copy of the Red Gate book on Team Development (Disclosure: I wrote the chapter on deploying databases).
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 11, 2011 at 7:08 am
Grant Fritchey (1/11/2011)
On #3, if you change the data type on existing data, you face the possibility of data loss, which, for most businesses, is a bad thing. So when do this sort of change, you always test it prior to running it on the production machine. For details on how to deploy to production, I'd suggest getting a copy of the Red Gate book on Team Development (Disclosure: I wrote the chapter on deploying databases).
This is already the second topic where I see you shamelessly promoting your own books 😀
(this is irony of course, don't take it seriously)
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
January 11, 2011 at 7:17 am
Koen (da-zero) (1/11/2011)
Grant Fritchey (1/11/2011)
On #3, if you change the data type on existing data, you face the possibility of data loss, which, for most businesses, is a bad thing. So when do this sort of change, you always test it prior to running it on the production machine. For details on how to deploy to production, I'd suggest getting a copy of the Red Gate book on Team Development (Disclosure: I wrote the chapter on deploying databases).This is already the second topic where I see you shamelessly promoting your own books 😀
(this is irony of course, don't take it seriously)
Busted.
Twice in one day is actually a lot for me. It just seemed applicable here.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 4 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply