HelpDesk180 Posted January 31, 2010 Report Share Posted January 31, 2010 I am backing up a system that has a practice management program using a MS SQL server database. I see lots of notes on additional licenses, special user rights, etc. and wonder if there is an easier way. Shut down the database to back it up. The "server" is running Win XP Pro. No Domain, no active directory, only one user on the system being backed up and they have full rights. Because everyone goes home at night and there is no remote access in use, is there any reason why I will not get a good backup if I just automatically stop the SQL server software when everyone leaves, run the backup, and start up the SQL program before anyone logs in in the morning? Quote Link to comment Share on other sites More sharing options...
Ramon88 Posted February 1, 2010 Report Share Posted February 1, 2010 You can have MS SQL create a backup scheme itself and backup those files with Retrospect. Quote Link to comment Share on other sites More sharing options...
HelpDesk180 Posted February 1, 2010 Author Report Share Posted February 1, 2010 OK, thanks. I will explore that. Question still stands, though. Is there a reason that backing up the closed files will not result in a restorable database? Quote Link to comment Share on other sites More sharing options...
Ramon88 Posted February 2, 2010 Report Share Posted February 2, 2010 If you stop the SQL services this shouldn't be a problem. It's just most people using MS SQL (professionally) have to run it 24/7. Stopping the services just isn't an option. But if that's not your usage profile you can use that as an advantage. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.