March 24, 2008 at 3:58 am
Please i need information or example on how to replicate data between two databases one in sql 2000 and another in sql 2005. The replication should work every hour on the hour. I am totally confused on how to do this.
wouldn't this cause any slowness in the production environment ?.
Please if any person has a knowledge on how to do this i will be grateful if you could direct me in a blog or in a detailed example .
Thanx in Advance.
March 24, 2008 at 6:23 am
That is a pretty vague question. There are several types of replication (Transactional, Merge, etc.). You need to first determine what type of replication suits your needs. This is usually based on where data can be updated.
As far as replication working between 2005 and 2000 databases - other than log shipping, replication generally works fine between the two versions of SQL.
March 24, 2008 at 8:04 am
to make it more simpler let me explain to you the situation.
1 i have a live database running on my production server which is using a database that is in sql 2000
which a program is using.
2 i have the same database running on another test server which is using sql 2005 which the same copy of the program is using.
3 i do not want to stop the production server i want to stop the production server to keep on taking data from it to test. I need my test environment to be updated the same like my production every hour on the hour.
4. Either i mirror my database together which is wrong or do a transaction restore every hour but this will slow my production server. So i was thinking of replication. If there is any solution i will welcome it Please help.
March 24, 2008 at 9:33 am
So you are really trying to keep your test environment updated.
You have some options. If the application does not update the database in the test environment in any way, you could use transaction log shipping and it is likely to be the lowest impact on your production system performance. I am of course making the assumption that you are already making transaction log backups at least every hour. Log shipping will apply these logs to your test server - which must be at most read-only (it cannot be updatable) and you would be able to see the changes.
Merge replication would work, but since you are not trying to apply transactions in your test server back to production, it is unnecessary.
Transactional replication will also work. It can be scheduled to copy and apply transactions on an hourly schedule. It will be a bit more overhead than log shipping, but probably not much. It is a bit of maintenance and may require your destination database have some keys and constraints removed.
However, I would not recommend replication as a way to keep your test environment updated. I would also really question why you would want a test environment updated hourly - changing data can make development difficult and it seems like a lot of management overhead. You will have lots of problems - like how do you test a change that impacts schema? I think this still comes down to me not having a clear picture of what you are trying to do, but I think you are probably on the wrong track.
March 24, 2008 at 10:28 am
OK what i want to do is make the test environment a backup of the production environment no development is done on the test unless absolutely necessary.
November 24, 2008 at 2:31 am
hi, i also need some helps here. Anyone who knows please reply.
This is my situation:
I have a two websites (first and second) which are linking to a database in MS SQL 2000. Recently i have migrated second website to a new webserver and i have also migrated the database to a new SQL 2005 server.
Unfortunately, now the website which is linking to MS SQL 2000 cannot connect to SQL 2005 due to some NAT problem. Everytime the database been updated, i have to export out data from the table frm SQL 2005 and import into table in SQL 2000. There is only one table that need to be accessed by the 1st website.
I am thinking of using transactional replication to solve this problem, where the SQL 2005 will replicate data everyday to the SQL 2000. Does anyone have any other suggestion? Please help.
Thank you.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply