And, check your connection settings. See if the TSQL connection & the ADO connection are the same.

Does your table variable have a primary key and is that used to join to the other tables? If not, that's going to be a performance problem right there since...

I just remembered. There's this great book by Craig Mullins called Database Administration. It doesn't dwell on technology, but goes over general concepts quite well. I'd recommend that one too.

True, but have you seen the Suite license cost per seat? We'll be adding procedures for the developers for some time to come.

Oh yeah, you can have the project deploy or drop objects, yes. It's getting objects into the project (or out) that is the problem. My developers all have the Developers...

Database design and indexing design is a tough topic and it takes time to get it right. Two books that you might want to add to your library are Inside...

Nope. The one issue that we've had, and believe me the developers have howled, is that they can not simply add procedures (or drop them either). They have to let...

To capture the rows moved have a look at the OUTPUT clause.

It's simply scanning an index along the logical chain of the index instead of along the storage chain, an allocation scan. This is usually from an ORDER BY, but can...

I'm pretty sure I'm old fashioned, but I still use OUTPUT parameters in some situations. Let's say you have a situation where the application normally creates a row in a...

Oops. Hit the "Post Reply" button too soon.

And no, this isn't a problem, depending on how you apply it. Multiple varchar fields of length 3000 would be a really poor...

You mean "compound" primary keys right? Because you can only have one primary key per table.

Although, you can have multiple unique constraints and refer to those as "alternate" keys...

Nope. That isn't possible.

What you can do, although it is VERY strongly not recommended, is pass the table name in as a string and then use dynamic TSQL to use...

Just remember that Books Online (BOL), the doucmentation installed with SQL Server, is your best friend in the world. Don't be a afraid to open it up and read up...

This is a decent overview.