Can't you use sp_renamedb for this?

Won't ever be that bored.... unless it's a really good question.

Could've used one 100% of the time... but there always was a better way.

Congrats on the 1K mark.

I must also point out that the clustered index will be contained in all other indexes so there's no need to explicitly reindex it.

Even better to use stored procs .

That from the same guys who don't understand why their password doesn't work with cap locks on .

Yup... 2000+ sps and counting : 0 cursor needed.

It would be something like this :

Private Function exec_usp_AddTwoIntegers(ByVal FirstNumber As Integer, ByVal SecondNumber As Integer, ByRef Answer As String, Optional ByRef ReturnValue As Integer) As Integer

On Error GoTo...

If you are referring to a lookup table then, most of the time (just not to say always), there's a unique constraint on the description column. However there might...

check in the front end AND apply unique constraint. Won't affect performance unless you have 1000s insert per hour/day. Also data integrity outweight performance in any case.

I bet you can't even with the waitfor .

Wow that's good... I didn't know anyone who could type that fast .

Check out convert in books online, you'll get all the info you need.

Then propose the set based approach next time .