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 - 2000-12-28 : 11:48:20
|
John writes "I know that DTS can be used to store queries to be run as jobs that will return Excel, but I dont want to use DTS because I have 4 developers that will be building queries and ownership is an issue. My scenario is that we have a legacy mainframe system that has a COBOL based retrieval language that we are replacing with SQL Server and T-SQL. We have about 400 retrievals that run every month and another 350 that run quarterly. What we woul dlike to do is to be able to convert the retrievals to T-SQL queries and return the data to an Excel spreadsheet and have it emailed to the appropriate requestor every month. I fiddled with using DTS but had some problems with ownership of the dts package preventing it from running. I dont want to give the people building the queries too much power on the SQL Server. I have thought that maybe using COld Fusion would solve the problem partially, but the queries would still have to be scheduled to run on their appropriate day. Any ideas, hints, etc you can give me that could help make this a better solution? We already have a database that has all of the retrievals request info and what day it runs, who it gets emailed to etc in it. Currently we have to log into the mainframe, request each retrieval and run it. That night a batch job on the mainframe runs our requests, and ftp's the files to our file server. In the morning we have a VB app that processes whats in that days directory and emails it all out. I want to eliminate all of the middle man and use just SQL Server if at all possible.
Thanks for any ideas.
John" |
|
|
|
|
|
Returning Query reults to Excel