Executing Scribe packages with stored procedure in SQL

Question

Post reply

Executing Scribe packages with stored procedure in SQL

mony12

SSC-Addicted

Points: 496
More actions
August 15, 2012 at 12:45 pm

#279691

Hi,
Is there anybody that has any experience launching a scribe package (dts) with in a stored procedure on a SQL 2008 R2). I have recently done an upgrade of our existing setup from a SQL 2005. The issue I'm facing is that I cannot launch my Scribe packages. It has been done with the help of xp_cmdshell and there after with sp_excutesql. The challenge is also that there are also linked servers involved. My SQL server and Scribe is linked.
I will be very grateful for A N Y help or hint out there!
Cheers 🙂

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Alexander Suprun SSCertifiable Points: 6233 More actions · Answer 1

Do you expect us to know what Scribe package is and how to run it?

Alex Suprun

mony12 SSC-Addicted Points: 496 More actions · Answer 2

asked if somebody has any experience with Scribe..not expecting everybody to know what it is :ermm:

ramkidec11 SSC Veteran Points: 234 More actions · Answer 3

HI There,

I am looking at the same issue here. Trying to run a scribe .dts package from SSIS execute process task or Execute sql task.

couldn't get it to work:-D. Any help on this would be appreciated!

thanks

ramkidec11 SSC Veteran Points: 234 More actions · Answer 4

Hi mony,

Have you managed to run the scribe jobs from SQL commands on different server?

mony12 SSC-Addicted Points: 496 More actions · Answer 5

Hi Ramkidec,

Yes, I managed to solve it considering the lack of Scribe material out there 😀

I had to make sure the linked servers where configured and also enable the xp_cmdshell. The latter one was disabled on my sql server, so check if that is the case on your server.

Last but not least I have this store procedure that is executing thru a scheduled job. Here I recommend that you do some kind of sql query that sends of an email in case the linked server is not reachable.

To launch the scribe package I create a string:

'EXEC @SomeParameter = master..xp_cmdShell ''C:\Program Files\SomePath+'\Scribe\MessageProcessor.exe '+@PackagePath+'\'+@FileName+' /RS"'''

The /RS I use to run Scribe silently in the background.

Now the important part! If you have packages that have sources connecting to different databases I strongly recommend that you use, MessageProcessor.exe, when you are running Scribe packages from stored procedures. You can use TWorkbench.exe but for some reason it cannot handle sources with different databases.

The scenario - If you run some Scribe packages with eg. SourceA and then try to run packages with SourceB it cannot swap.

It took me some time to figure this out. :angry:

Hope this helps 🙂 Let me know if you need any more information!