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 |
|
morphviper
Yak Posting Veteran
60 Posts |
 Posted - 2009-04-23 : 11:30:03
|
| I am useing Snap shot Replication and the location where it stores the Snapshots file is getting very large and eating up my hard drive. How do I get sql server to only keep a couple of these or current and not every snapshot since it started? I figure it is a setting that I am missing but any help would be greatly appreciated. |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-04-23 : 23:30:01
|
| why not transactional replication if you are running it continously. |
 |
|
|
cat_jesus
Aged Yak Warrior
547 Posts |
Posted - 2009-04-24 : 08:50:56
|
| Sodeep, Shouldn't you also be running a daily snapshot even when doing transactional replication? I don't know what the best practice is, but I've found it very handy to keep one snapshot around.An infinite universe is the ultimate cartesian product. |
|
|
|
morphviper
Yak Posting Veteran
60 Posts |
Posted - 2009-04-24 : 10:27:44
|
| I wanted to do that (Transactional), but the person who created the tables did not put in a primary key. This seems to be a data dump and they want it pushed to the reporting db.To add a primary key would changed thing in the app that is attached to it and would require a project. They don't want a project for this.so any ideas would be helpful. |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-04-24 : 12:09:47
|
| Then Why don't you go with Backup/Restore approach? |
|
|
|
morphviper
Yak Posting Veteran
60 Posts |
Posted - 2009-04-24 : 13:30:24
|
| Only two tables and there are over a hundred table in the db. and the reporting db houses many from many. I actually found a solution.thank you everyone for the ideas and thoughts. |
|
|
|
|
|
|
SnapShot Replication Files using too much HD