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 |
|
SQLCode
Posting Yak Master
143 Posts |
 Posted - 2006-03-23 : 11:54:33
|
| Hello,We have a transational db with too many people logged in all the time. We are looking at replication/log shipping for reporting/data warehouse. We initially set up snapshot replication. The problem with that is it is taking too much time in taking a snapshot everytime the server is taken down for routine maintenance. We cannot afford so much down time. The db is about 50G in size and there are several similar on the same server. Can there be other methods to do this without so much down time?Log shipping is having another problem. The logs are too big to be shipped across. What could be major reasons for logs to grow that crazily. Once in a while, one log is 15-20 times bigger than the other?Any advise, help is appreciated. |
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2006-03-23 : 12:19:13
|
| How often are you doing a complete backup?Why not use transactional replication? |
 |
|
|
Srinika
Master Smack Fu Yak Hacker
1378 Posts |
Posted - 2006-03-23 : 12:21:23
|
| Ur DB is used during the whole day or u have some off-peak timeIf u have some such u can schedule to do the replication.Do u need all ur data (50GB) for reporting? If not u can select the data, to be replicated. So that the time takes to transfer data may not be that much.U can limit the transaction log from growingRefer to : http://www.nigelrivett.net/TransactionLogFileGrows_1.html |
|
|
|
SQLCode
Posting Yak Master
143 Posts |
Posted - 2006-03-23 : 12:53:58
|
| Thanks for the help. The down time is very rare like once in a quarter or a 2 months. Hence it is futile setting up snapshot as more databses are added in succession.More time is taken for log shipping log tranfers if we chose that, not replication. |
|
|
|
JoeNak
Constraint Violating Yak Guru
292 Posts |
Posted - 2006-03-23 : 22:01:01
|
| If the reporting doesn't need to be near real time, you could set up a nightly DTS to move the data (a path you'd probably head down for a DW anyway). If it needs to be more current than that, why can't you use transactional replication like Rick suggested?Why are you logs growing like crazy? Probably after a DBREINDEX or INDEXDEFRAG. More transaction log reading if you like...http://support.microsoft.com/?kbid=873235 |
|
|
|
|
|
|
Replication - which one?