Post reply

Copy small tables: which method?

  • March 6, 2007 at 4:55 pm

    #116468

    I'm the lone application developer in a SQL Server 2000 shop.  I am modifying a VB6 app (I know, don't get me started!   ) that loads up some small (< 10,000 rows) tables, massages the rows, then copies the tables to another server for use by a different VB6 application (it truncates the destination tables first) through linked servers:

    INSERT INTO tableA SELECT * from OtherServer..TableA

    My knee-jerk reaction was to replace this code with a call to a DTS package that copies the tables as objects.  But our database servers are all Compaq blade servers, so the interconnection is pretty fast and solid.  These particular apps are used by max three people, hardly ever concurrently.  I'm wondering if this is a bad way to do it after all.  The current app uses embedded SQL, I could put the TRUNCATE.. INSERT into a stored proc and still sleep at night...

    What do you think?

    There is no "i" in team, but idiot has two.

  • March 7, 2007 at 7:39 am

    #693572

    By pass the VB 6 app and run with DTS. Copying/massaging data between servers is what DTS packages were made for. The application is old code and just something else legacy that will have to be maintained. Get rid of it while you can and have an excuse =)

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply