Question

I have a SQL Sever 2008 R2/64-bit database server for which I’m writing some fairly basic scripting utilities with the Sql Server Management Objects (SMO). My project is a 32-bit VS2010 executable written in C#.

Most of the effort has been fairly simple and successful. The only problem I’m having is in the firing of my custom event handler that should be called in response to a Scripting Error.

The Scripter object exposes a ScriptingError event, which I have attempted to leverage thusly:

//srv contains a valid server name
Scripter scrp = new Scripter(srv);

//scrp_ScriptingError is my handler
scrp.ScriptingError += new ScriptingErrorEventHandler(scrp_ScriptingError); 

My handler is declared thusly:

   static void scrp_ScriptingError(object sender, ScriptingErrorEventArgs e)
   {
       // my handler goes here, just printing e.Current.Urn to the console
       // This is merely representative, have had other things here, but
       // the handler never fires
       Console.WriteLine(e.Current.Value);
   }

All this compiles cleanly.

My code is invoked via simple scrp.Script(urns); where urns is just an array of the database objects being scripted out. Nothing fancy:

    try
    {
        sc = scripter.Script(urns);
    }
    catch (Exception e)
    {
        WriteLog(String.Format("Failure during scripting: {0}: Inner exception message (if any): {1}",e.Message,((e.InnerException==null)?"[None]":e.InnerException.Message)));
    }
    using (System.IO.StreamWriter file = new System.IO.StreamWriter(fileName,true))
    {
        foreach(String currentLine in sc)
        {
            file.WriteLine(currentLine);
            file.WriteLine("GO");
        }
    }

The problem is that, no matter what I’ve tried so far, when errors occur during scripting, my ScriptingError handler never fires.

Even in debug mode within VS2010, when I set a breakpoint within the handler, and fire my scripting code, and know an error will occur, only an exception will be thrown, but the breakpoint in my ScriptingError handler never trips.

I’m in trees-for-forest mode now, not sure what I’ve done wrong. Am I expecting the wrong things for the ScriptingError handler?

I have searched the MSDN docs on the SMO objects and found virtually nothing on ScriptingError handlers other than the basic API calls themselves, and precious few examples on the Internet. It seems incredibly simple and straightforward to me – just assigning an event handler to the event – but there’s some battery-not-included notice I’ve failed to note.

Pointers to my error are greatly appreciated, with a polite request for minimal brickbats if the error is exceptionally stupid on my part 🙂

Answer 1

I am not at a pc right know, but I think you should try to set the ContinueScriptingOnError option. Otherwise there would be no reason for SMO to invoke the event, but rather through an exception instead.