May 1, 2005 at 5:59 pm
I have a sql script that is ran on several different servers with the osql command that selects sql data and creates and saves an XML file from it (the reason for the sql script instead of other script languages such as vbscript is because our IT dept is small and the only language all of the others are familiar with is T-SQL). Anyway, I need the XML to use an xslt that a I created to transform into whatever XML structure our client is requesting. The problem is that I can't get the sp_oamethod to execute the transformNode command correctly and save the output. So for that small part I was going to have to build a vbscript to do the transformation, the problem is that if I run the vbscript from xp_cmdshell if their is a sytax error or something like that (there shouldn't ever be, but there is always a chance of it if we have to make a correction to the file) the wscript.exe process in windows won't clear and the only way it will clear is if the server is rebooted (taskkill won't even kill the process). Rebooting the server will not be acceptable by my boss, and I know DTS is an option, but DTS seems like overkill for such a simple task. Does anyone know how to transform and save an XML file in T-SQL or how to avoid process lock ups in a vbscript that is ran from xp_cmdshell??? **I am using the on error resume next command in vbscript but it doesn't ignore syntax errors. And all of the SQL Servers are SQL Server 2000
Thanks for any assistance,
Adam
May 2, 2005 at 3:19 pm
Just ignore this post, I put the vbscript to translate the file in a DTS package and saved it as file instead of saving it in SQL Server. I forgot that that was an option, I just didn't want to save it as a DTS package in SQL Server because I felt like it was a waste of space to have a DTS package in my list of packages that did nothing but a couple XSLT transformations.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply