Handling "GO" Separators in SQL Scripts - the easy way

Posted by: JonGalloway.ToString(), on 07 Nov 2006 | View original | Bookmarked: 0 time(s)

If you've ever had to execute one or more SQL scripts from ADO.NET, you've likely run into the GO batch terminator issue. Any SQL script that does anything worthwhile has more than one batch, separated by a GO terminator. The problem is that "GO" isn't valid T-SQL, it's just a command used by the SQLCMD, OSQL and ISQL utilities that can also be used within Query Analyzer and the Query Editor window. If you try to execute T-SQL scripts with GO commands in them via ADO.NET...

Category: SQL | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 1678 | Hits: 40

Similar Posts

  • Oredev Wrap-Up more
  • Debunking the duct tape programmer more
  • RadScheduler for Silverlight learning series, part 3: Add, Edit, and Delete Appointments more
  • Speaking at the Portland Area .NET User Group on Tuesday Sept 1st more
  • OMG, where do I start? more
  • Win a Govie Award Submit an Innovative Gov 2.0 Application more
  • UppercuT - Automated Builds - Custom Tasks more
  • Trip Report from Gov 2.0 Camp more
  • OleDb Parameters to access FoxPro Data from .NET more
  • Recommended Reading I more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD