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 |
|
elwoos
Master Smack Fu Yak Hacker
2052 Posts |
 Posted - 2010-05-13 : 09:02:08
|
I'm looking for good ideas that will solve an issue I have.I need to regularly import data from an external systsem into a sql server 2000, I can't setup a linked server or anything like that as there are no drivers for this particular database that I am aware of. The external system can generate tab seperated files in a known format that I am able to import manually. Apparently the external system cannot automate the production of these files, as a result the sysadmin of the external system is intending to produce this output manually on a daily basis (am I glad this isn't me  ) For my side of this (the SQL server bits) I have setup a dts package that can import and process this data as needed. In order to streamline this whole mess process as much as possible, the sysadmin will be executing the dts package.So here is my problem. The sysadmin knows nothing about SQL Server. I am unable to install anything on her machine e.g. no DTSRUN. I want to be able to give the sysadmin something very simple to do that will load the data e.g. a batch file or a button on a web page somewhere, that will import the data from a file with a fixed file name in a fixed location i.e. as few moving parts as possible to get wrongAt the moment I have 3 options that I can think of - none of which are particularly desirable1) I setup a shared folder on the SQL Server box that the sysadmin can put the export into and I could run the dts package say every day at a fixed time. 2) Using the same shared folder as above but also give them access to dtsrun on the server, and a batch file that will call it3) Create a webpage that will let them upload the file and then press a button to call the dts packageI don't really like any of these though I think 1 is my favoured as it seems the simplest option.Does anyone have any other inspiration?thanks in advancesteve-----------Deja Moo - The feeling you've heard the same bull before. |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2010-05-13 : 10:45:22
|
| isnt it enough to ask sysadmin to put file onto a shared location . then design package in such a way it looks for file in a folder and then do required data transfer. You may schedule a sql agent job to execute this package automatically daily so that you can dispense with manual run.http://www.sqldts.com/246.aspx------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
 |
|
|
elwoos
Master Smack Fu Yak Hacker
2052 Posts |
Posted - 2010-05-14 : 04:13:04
|
| Yes thanks for that, it's similar to my option one but more sophisticated. I think its going to be the way forward.Not sure how I missed it on SQLDTS but thanks again for the linksteve-----------Deja Moo - The feeling you've heard the same bull before. |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2010-05-14 : 13:21:25
|
welcome  ------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
|
X002548
Not Just a Number
15586 Posts |
|
|
jezemine
Master Smack Fu Yak Hacker
2886 Posts |
Posted - 2010-05-14 : 18:30:12
|
that's not enterprisey enough brett!:)
elsasoft.org |
|
|
|
|
|
|
Looking for inspiration