Generating Output Text File From SQL Server Stored Procedure
Hello all!
I have a Stored Procedure that I use to generate a dataset that is subsequently used in a Crystal Report.
In order to track the data that is being processed, I'd like to generate an ouput file that would be created anytime the Stored Proecedure is run. Ideally, I would like this Output Text file to just contain the one particular column of data from the dataset, but it can contain the entire dataset if necessary.
Now, I've read about using xp_cmdshell and OSQL as options of outputting text. However, this is a routine Client job that will be run on demand by a user without permissions to use commands like xp_cmdshell or OSQL. Is there anything else I can try in order to facillitate this text file export?
Thanks in advance!
I have a Stored Procedure that I use to generate a dataset that is subsequently used in a Crystal Report.
In order to track the data that is being processed, I'd like to generate an ouput file that would be created anytime the Stored Proecedure is run. Ideally, I would like this Output Text file to just contain the one particular column of data from the dataset, but it can contain the entire dataset if necessary.
Now, I've read about using xp_cmdshell and OSQL as options of outputting text. However, this is a routine Client job that will be run on demand by a user without permissions to use commands like xp_cmdshell or OSQL. Is there anything else I can try in order to facillitate this text file export?
Thanks in advance!
brad2575
Could you not just save this output to a new table and save all the data into a field in the database? If you know the fields have the fields seperated out or have one filed as a text or varchar(MAX) field contain all the data (depending on the amount of data we are talking about).
ASKER
brad2575,
The issue is that we need to track the account numbers we pull in the report (which is the column of data I'd like to export to a file). This is necessary so we can then upload the .txt file to our account management system which will automatically update the accounts from that list.
By just saving a list in another table of that data we pull, we'd eliminate the increased efficiency of the project by still requiring an associate to manually process the data set and enter notations for each account into our account management system.
The issue is that we need to track the account numbers we pull in the report (which is the column of data I'd like to export to a file). This is necessary so we can then upload the .txt file to our account management system which will automatically update the accounts from that list.
By just saving a list in another table of that data we pull, we'd eliminate the increased efficiency of the project by still requiring an associate to manually process the data set and enter notations for each account into our account management system.
Ok I misunderstood what the extra data/file was being used for. I thought it was for history/tracking purposes.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
DTS solved it for me. Thank you!