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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2006-10-18 : 08:07:21
|
| Sudripta writes "Hi,I have read only permission in the source (OLTP) database. The source database is running in SQL Server 2000 and the size is more than 200 GB. I need to pull data from source and load target which is running in SQL server 2005. Following are the objectives I want to achieve.a) Data should be loaded on incremental basis.b) Whatever changes take place (Update/Delete) in source, that should be replicated to already uploaded data.Here I want to mention that, the source database does not have any identification key or timestamp column like Updated_Date by which I can filter the data which are recently inserted or updated into the source and upload the same. The source does not maintain any history data also. So I do not have any track of deleted record also.I don’t have any scope to change the schema in the source. In this scenario can anybody suggest me the best approach to achieve the above mentioned objectives?I think if I can retrieve only the changes and new records form transaction log back up it can solve the problem. But I don’t know how to do that. Can log shipping help me?One more question. Say I have a table and I am exporting/importing all the data from/to my target table using SSIS or DTS. In this scenario does using query or using directly the table matters the performance?RegardsSudripta Rakshit." |
|
|
snSQL
Master Smack Fu Yak Hacker
1837 Posts |
Posted - 2006-10-18 : 14:04:33
|
| Log shipping or replication can do what you need. You say you cannot change the schema of the source, but to set up log shipping or replication you will have to be able to set those things up on the source server - you won't need to change the schema, but you will need an administrator on that server to set things up. (Hopefully you won't need schema changes, if the database is badly designed then it may not even allow replication or log shipping)When you query a table then you are using resources on the server and that may have a very small or quite a large impact on the performance of that server depending on: how busy the server is, the hardware in the server, how much data you are querying, whether or not the data you are querying is well designed and indexed, and how well your query is designed. |
 |
|
|
|
|
|
Transferring data from read-only source to destination.