Here's the What's New listing on 2008

http://msdn.microsoft.com/en-us/library/bb500435.aspx

I haven't been too crazy about it, but Books24x7 has a very good service.

It sounds like something in your code is trying to create the index, probably over & over again. You should check the code. I don't think you're dropping it is...

I support quite a few development teams. I usually take charge of creating their databases, setting up backups & restores and then, depending on the team, their level of expertise,...

Without the things that Gail asked for... No. No one can tell you what's wrong because we're not there and don't have a clue what's the problem on your end....

Have you updated the statistics recently and if so, have you tried updating with a full scan? There is a bit of a discrepancy between the estimated rows & the...

If you use the result set to show success, just prepare your code handle multiple result sets because you'll need one for the success criteria and one for the data...

Just so the next person along can understand, can you post the solution?

May as well pile on. This absolutely should have been CHAR(1) or NCHAR(1). VARCHAR or NVARCHAR were the worst choice under any fair interpretation of the definition. The answer stated...

Yeah, I should have mentioned that. For anything beyond a single row insert, that's the way to go.

The correct syntax is:

ALTER DATABASE xxxx SET PARAMETERIZATION FORCED

You were just missing the SET statement.

You should still see an execution plan, regardless of whether or not it's got forced parameterization....

Check out the forced parameterization topic in the Books Online (SQL Server's documentation). It lists all the various times that you can't use forced parameterization such as:

INSERT ... EXECUTE queries

Statements...

If you create a view with schemabinding then the base tables can't be modified in a way that would break the view. However, if the view doesn't exist and you're...

SCOPE_IDENTITY is not going to be affected negatively or positively by being called within a transaction. I would recommend the transaction though, just because it's a better way to manage...

And run consistency checks before you backup the database so that in the future you'll know that the backup was taken from a well structured db.