February 12, 2009 at 6:44 am
We have an application that was purchased where the creators made tables with more that 255 fields. This prevents us from doing replication. We are looking for a way to keep multiple versions of the database current. All the databases will be in the same environment. In fact, we really just want to keep a main master database and have two "slave" databases whereby other departments can do reporting off of them.
Does anyone have any experience/advice on how to go about setting up mirroring in a 2000 environment? Other software or solutions are also welcome and greatly appreciated.
Thanks,
Steve
February 12, 2009 at 10:20 am
Database mirroring isn't available before SQL 2005. Maybe you could use log shipping?
Greg
February 12, 2009 at 10:26 am
Didn't know that ... thanks. Do you know of any automated way to ship and process the log files?
February 12, 2009 at 2:44 pm
If you have Enterprise Edition, MS log shipping is available and you can implement it using a wizard. If you have Standard Edition, these articles walk you through setting up home-grown log shipping. I haven't implemented it, but I've seen it referenced in forums and blogs.
http://www.sql-server-performance.com/articles/clustering/log_shipping_70_p1.aspx
http://www.sqlservercentral.com/articles/Administering/customlogshipping/1201/
http://technet.microsoft.com/en-us/library/cc966381.aspx
Greg
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply