What steps will reproduce the problem? 1. Run a query with many inserts 2. 3.

What is the expected output? What do you see instead?

Internal Error: Microsoft.SqlServer.Management.Common.ExecutionFailureException An exception occurred while executing a Transact-SQL statement or batch.

at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType) at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand) at Tarantino.DatabaseManager.NAntTasks.Services.Impl.QueryExecutor.ExecuteNonQuery(ConnectionSettings settings, String sql) at Tarantino.DatabaseManager.NAntTasks.Services.Impl.ChangeScriptExecutor.Execute(String fullFilename, ConnectionSettings settings, ITaskObserver taskObserver) at Tarantino.DatabaseManager.NAntTasks.Services.Impl.DatabaseUpgrader.Upgrade(String scriptDirectory, String server, String database, Boolean integrated, String username, String password, DatabaseAction action, ITaskObserver taskObserver, String databaseVersionPropertyName) at Tarantino.DatabaseManager.NAntTasks.Services.Impl.ManageSqlDatabaseTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) at NAnt.Core.Tasks.CallTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) at NAnt.Core.Tasks.CallTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) at NAnt.Core.Project.Execute() at NAnt.Core.Project.Run()

What version of the product are you using? On what operating system?

Windows XP

Please provide any additional information below.

I have a sql file with a large number of insert statements. When the database is created the database has these rows inserted put the database in it's starting state.

By a large number, I'm talking 42,745 (all the zip codes in the united states).

Tim, did this get fixed?

No it did not, I am looking at issues #1 and #2 currently and would like to eventually hit #3.

have you retried this since I upgraded the framework to run against the sql 2008 binaries?

I have not, will these binaries work even if I am on 2005?