It's likely that your problem is related to User Instance feature. See this link:

So, to you does it look like a bug in a SMO generated code?

It's all one trigger....do you suggest that there should be a separate trigger for Insert, Update and...

If you open and close connection on each insert than .. 8 sec for 252 inserts would be about right. Try to open connection, do all inserts and then...

As per Microsoft (I believe…) there are 3 personalities among programmers: Einstein, Elvis and Mort.

C++ the language and IDE settings are for Einsteins, C# is for Elvises and VB (VB.NET)...

During SharePoint setup I had some issues with connecting to sql 2008 remotely and all those issues were related to: sql 2008 being named instance so configured to use a...

I have not seen any information about a SQL Server version. Is it a Standard or an Enterprise?

SQL Server 2000 Standard cannot use more than 2 GB of memory I...

I have seen it happening several times. A very powerful production machine vs. my 3 years old laptop or my home lab, 5 years old, single core, single processor, low...

I am not a DBA and I speak from experiences as a developer. Most ORM tools support Stored Procedures. Sometimes you might need to tweak something. For example, Entity Framework...

Is 14 sec a long time for that query to execute? The original post says it takes 14 sec to return 42000 rows from a query that uses 3 very...

It seems to be .NET issue.

This: System.Data.DataRow.GetDataColumn is a DataRow method. The table is a DataTable (disconnected recordset).

So, if you are sure that the column exists in a...

I see it this way: if somebody asks what is better to use I would say SET because "you/another person after you/some seemingly unrelated change in the database" are less...

SET is safer. Code below will throw an error. With select you will get a value from one of the records. Troubleshooting logic error caused by SELECT is more difficult...

LINQ uses dynamic queries behind the scenes. You can make use of Stored Procedures with LINQ .. but you lose all the smarts. You write the queries instead of letting...

Misunderstood “Security” was a reason why developers were made to write queries like :WHERE @CustomerID IS NULL OR tblx.CustomerID = @CustomerID. Once tables grow to significant size the...

It's not so simple though. Would you rather see a dynamic select query that joins 2 tables and has 2 conditions in a WHERE clause (because other parameters are nulls)...