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 |
|
lordlion
Starting Member
3 Posts |
 Posted - 2001-03-14 : 03:32:40
|
| This is a question that has been thorn in my side for months... I pray that someone can give me some direction. As I have mentioned in my previous post, I am a victim of company manpower shortages and need to get up to speed on MSSQL in a hurry, so I'll thank all of you now for lending a hand.(shortage due to lack of funds to hire someone)My Problem:I have hundreds of MSDE databases scattered around the US and I need to move the data contained in their database and bring it home to our NOC and I need to do it as fast as possible.Currently, I have a written a down and dirty VB app that will one by one, transfer the data to the NOC. It is very time consuming and clunky.What I am looking for here is not for someone to completely solve my problem for me, but to point a finger at what they believe to be the best course of action for me. I want to reach my goal completely with SQL Server and not rely on custom developed apps running external to SQL. I would like this to be an automated system which will, once run, will wait a pre-determined length of time, then run again. (an agent?) Anyway, I am sure you get the idea, the data being pulled is not significant, the table structure on the remote MSDE machines is identical to that of the NOC so don’t get wrapped around the axle on that. Your thoughts on what would be the best way to have SQL go out over the internet, connect to my remote MSDE machines and append their data to its own. I hope this is some good food for thought for everyone... Thanks in advance...Craig |
|
|
|
|
|
How to bring the data home