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 |
|
Mmats
Starting Member
47 Posts |
Posted - 2005-04-25 : 17:09:18
|
| I wanted to set up a system that would be fault tolerant to the second. So I went for transactional replication, thinking that any changes made would be instantly replicated to the backup server. Now Im finding out that new stored procedures and new tables wont replicate? Is this correct? Do I have to use snapshots of my whole database everytime there is a change? Seems like a waste of bandwidth copying a database just for a new stored procedure. |
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2005-04-26 : 04:39:13
|
| Your needs might be better served by clustering and using suitable SAN infrastructure to copy your data in real time.-------Moo. :) |
 |
|
|
Mmats
Starting Member
47 Posts |
Posted - 2005-04-26 : 09:52:29
|
| Well what about transactional rep during the day then have a snapshot applied overnight? Or would that require me rebuilding the subscription every day? |
 |
|
|
mpetanovitch
Yak Posting Veteran
52 Posts |
Posted - 2005-04-27 : 21:21:46
|
| It would require you reconfiguring replication(publication and a push out to your subscribers) everytime a new object is added(mainly by using sp_addarticle(would have to test if it worked for things other then tables). You are able to replicate stored procedures/user defined functions or views, however the defination is only replicated in the intial snapshot. Only DATA in transactional replication is done real time.Look into log shipping(replication is the wrong tool for you), this enables you to have a warm stand-by server and all objects are kept in sync, ddl and dml.Only thing that is not replcated is your server side configurations (ie server logins). Note: a log ship server's db is offline while the log is being applied, otherwise its read only.(if its configured like that).Once you recover the db completely, during a diaster recovery for example, you can access it fully. Mike Petanovitch |
 |
|
|
Mmats
Starting Member
47 Posts |
Posted - 2005-04-28 : 16:05:34
|
| log shipping does look like the right choice, except since the destination server is outside of the network I cant add it as a destination database. I have added it in EM by its internet ip address but it still doesnt show up in the destination dropdown box. Both servers are on sql 2000 |
 |
|
|
|
|
|