August 28, 2003 at 1:19 am
Hi.
We are busy in the process of developing an "off the shelf" application with SQL server as the database server.
In this application, we want the user to have as little or no need for SQL knowledge.
Part of the application requires the periodic import of data from third party systems.
I have created the DTS and it works very well. The DTS are run using stored procs.
I have embedded the msdb sysdtspackages table into a copy table in the application database. When the application database is installed in a new client, there is a stored proc which copies the contents of this table back to the msdb database, and thereby making it available for DTS'ing.
This works very well, but what happens when we want to add new functions to the DTS and distribute these to existing customers? I could create an export file and have them import this using dts to the dts table. Alternatively, I could just save it as a dts scripted file which they would have to manually load.
At the end of the day, this application must be as easy and un-technical as possible.
I would appreiciate any feedbacks on the above. Also, how have people been able to accomplish the above.
Also, perhaps it would have been better to write a Stored procedure script to handle the importing. Updates of stored procedures using query analyser scripts are much easier to accomplish.
Thanks in advance.
August 28, 2003 at 6:16 am
Before you get too heavily tied into using DTS as part of your application, take a look at the following.
http://www.timeline.com/021903PR.htm
http://www.timeline.com/PatentMemo.pdf
Hope this helps
Phill Carter
--------------------
Colt 45 - the original point and click interface
--------------------
Colt 45 - the original point and click interface
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply