Using DMO to run sql scripts.

Question

Viewing 8 posts - 1 through 8 (of 8 total)

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

Andy Warren SSC Guru Points: 119902 More actions · Answer 1

I thought the "go's" would work, haven't looked lately. Can you post a chunk of the code?

Andy

Tom Goltl SSCertifiable Points: 5815 More actions · Answer 2

I copied your code for the section I am having problems with. Here is the line that won't run the entire script:

oDB.ExecuteWithResultsAndMessages sScript, , sMsg.

I get an error with the "go" in the script when I run with that command.

I changed the command to this: oDB.ExecuteImmediate sScript, SQLDMOExec_ContinueOnError

It will now run but I can't get any of the error messages from this command.

Thanks for looking.

Tom Goltl

Andy Warren SSC Guru Points: 119902 More actions · Answer 3

Man, I'll have to stop posting code that has bugs in it! Put in a debug.print to confirm that the CommandTerminator property is "GO".

Andy

Tom Goltl SSCertifiable Points: 5815 More actions · Answer 4

The commandterminator property is set to "go". But it certainly doesn't like the go's in the script.

Just so you don't get down, Your sample code is a big help to us hacks.

Tom

Andy Warren SSC Guru Points: 119902 More actions · Answer 5

I'll try to research a little more. Only thought that I have right now is maybe the terminator is case sensitive?

Andy

Tom Goltl SSCertifiable Points: 5815 More actions · Answer 6

I succesfully changed the commandterminator, but that made know difference. The error message: incorrect syntax near "go".

I'll keep on trying.

Thanks

Tom

AlistairB Newbie Points: 5 More actions · Answer 7

Use db.ExecuteImmediate (strTSQLCMD)

then test err.number, this works just fine.

We are using it to rebuild a database object by object from SQL scripts in source control - these scripts have GO statements in them.

Hope this helps. Al