Categories

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

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

Filed under: Database,SQL | On : 2006 Nov 07 | From: JonGalloway.ToString() |

Efficient Debugging Messages: Why Unnecessary Method Calls Are Bad Mmmkay?

Hot releases: .NET Framework 3.0, Windows SDK, 2007 Office System + VSTO, ASP.NET AJAX, SQL Server 2005 Compact Edition

Similar Posts

SqlScriptInstaller

In my previous post I described a general-purpose Installer that can be used to create a SQL Server database during installation (and delete it again during

[SQL] Some of my favorite INFORMATION_SCHEMA utility queries

Phil just posted about using INFORMATION_SCHEMA to bulletproof your SQL change scripts . I've been working up a post on using queries against INFORMATION_SCHEMA

Asynchronous command execution in .NET 2.0

Asynchronous execution of commands was one of great new features in ADO.NET 2.0. The ability to execute commands that take long time to execute asynchronously

Call SQLCMD from .Net with Output Capture

Stark's Blog - Execute sqlcmd (oSql) from .NET and capture the output I have recently seen quite a few questions about executing sqlcmd (oSql for those

Most Popular

How To Group ListView Items with ListViewGroup VB2005

Publishing Reporting Services reports to MOSS

How to bind Generic Dictionary with dropdown list

Parse Comma Delimited TextFile with Visual Basic 2005 TextFieldParser

Using the Active Directory Membership Provider with Forms Authentication in MOSS 2007

Using a parameterized SSIS package as a data source for SQL Reporting Services