Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
hinelpatel
Starting Member
1 Post |
 Posted - 2003-06-15 : 17:08:35
|
| Hello,We have a 24/7 20MB SQL Server database which is expected to grow to 30MB max in the next 5 years!..so pretty small database but no downtime and not too many transactions..am a newbie DBA and was hoping to get some tips on the best backup strategy for this ..>Considered using Log Shipping as we will be having a secondary database server . BUT is it a good idea to use log shipping for this small a system....????> Considered taking transaction log backups every 1/2 hr to 2 different disks...would this have a great impact on the system???? again the database is about 20 MB..> Would we gain more security if we have transaction log .ldf file and the data files on 2 different SERVERS?? my manager suggested this and am not sure what we can gain from this approach..the logic was if the primary server went down we can apply the transaction log to the secondary and bring it up???? but if the secondary went down then we are in big trouble anyways???? thoughts, advice will be greatly appreciated :)thanks |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2003-06-15 : 22:07:14
|
quote:
>Considered using Log Shipping as we will be having a secondary database server . BUT is it a good idea to use log shipping for this small a system....????
Depends on the necessary downtime requirements. Log shipping won't hurt.quote:
> Considered taking transaction log backups every 1/2 hr to 2 different disks...would this have a great impact on the system???? again the database is about 20 MB..
Shouldn't, your backups should run in a mater of seconds.quote:
> Would we gain more security if we have transaction log .ldf file and the data files on 2 different SERVERS?? my manager suggested this and am not sure what we can gain from this approach..the logic was if the primary server went down we can apply the transaction log to the secondary and bring it up???? but if the secondary went down then we are in big trouble anyways????
Not possible, so I would say no.-Chadhttp://www.clrsoft.comSoftware built for the Common Language Runtime. |
 |
|
|
debug
Starting Member
29 Posts |
Posted - 2003-06-17 : 03:05:39
|
| hi ,It all depends on the criticality of the database. If the database his highly critical.. Log shipping would be one of the best options foa standy, If the database is not so critical then a Full backup once per day as a sched task would suffice.RegardsDU |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-06-17 : 12:29:17
|
| We log ship our biggest databases all the way down to our smallest databases (less than 5MB right now). It might seem like an overkill for such a small database, but we've got high availability requirements.Tara |
|
|
|
|
|
|
Best Backup Strategy?