apilkington
asked on
SQL Server 2008 Default Backup behavior?
Hello,
We have a client that is using SQL Server 2008 as the database for an application that should have components of the application running 24 hours a day. I have several questions about the backup that is happening.
Every evening SQL server performs a backup of the database. When this happens it kills the connections that the various workstations running the application have to the database.
I did not specifically setup the backup on this database, is there a default backup routine that is created when a new database is created?
A second question I have is can I setup the backup so that it does not close the connections I have to the database? The applications that we are running become non functioning when they lose their connection and keep trying to connect.
I am finding that for what I need books online is not giving me the answers I need quickly enough.
Thanks
We have a client that is using SQL Server 2008 as the database for an application that should have components of the application running 24 hours a day. I have several questions about the backup that is happening.
Every evening SQL server performs a backup of the database. When this happens it kills the connections that the various workstations running the application have to the database.
I did not specifically setup the backup on this database, is there a default backup routine that is created when a new database is created?
A second question I have is can I setup the backup so that it does not close the connections I have to the database? The applications that we are running become non functioning when they lose their connection and keep trying to connect.
I am finding that for what I need books online is not giving me the answers I need quickly enough.
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for apilkington's comment http:/Q_27400975.html#36982387
for the following reason:
I was able to do research and found the main issue I was having on my own while I was waiting for a response.
Accepted answer: 0 points for apilkington's comment http:/Q_27400975.html#36982387
for the following reason:
I was able to do research and found the main issue I was having on my own while I was waiting for a response.
Odd on 17/10 you say
From SQL Server point of view Windows Server Backup is a third party tool. And now you found it by yourself.
For as far as I can read you were waiting on your client.
Ok, after looking at the article that was at the link provided and looking at the scheduled tasks on the server in question, I have figured out that the problem we are having is most likely being caused by Windows Server Backup
From SQL Server point of view Windows Server Backup is a third party tool. And now you found it by yourself.
For as far as I can read you were waiting on your client.
There is a nice server backup tool that does SQL backups and restorations by BackupAssist that works well. It is pretty cheap too.
See - http://www.backupassist.com/BackupAssist/tour_SQL.html
See - http://www.backupassist.com/BackupAssist/tour_SQL.html
ASKER
I know from looking my databases are being backed up every night at 9:00 PM and when this happens it is disconnecting our applications connections to the database.