David, very nice! Of course, it all comes down to someone putting in the descriptions for each field or you just get a list of tables and columns.

I'd be...

Ah yes, the base 36 conversion to "bad" words. Probably most people have run across this at least once in their lifetime.

It reminds me of something I did with...

Super article Jeff -- as always. Thanks especially for writing something that works in SQL 2000 (until you hit the 4000 char limit). A number of us out...

This whole discussion is NULL and VOID since NULL is no longer being supported in SQL Server. Oh wait, that was just an April Fool's joke. Sorry.

Pretty cool, but what is it? Could it be the famous sculpture made famouse by Marie Barrone?

As a developer more than a DBA, it would probably take me five times as long to finish a project if I didn't have, at the very least, Visual Studio...

I find that typically "children must play." There are those upper-level, high-profile, strongly-connected, politically-minded (that's enough adjectives) "business people" who took a database theory class while getting their degree...

Very nice.

I would make a couple of suggestions though. To avoid the loop looking at each individual character, use regular expressions to look for invalid characters:

IF (

...

It is always important to be civil on forums and in life. However, I feel the frustration that develops when you simply cannot solve a problem. I am...

Cost is usually a good indicator, but it can be misleading -- especially if you only evaluate it on test servers with limited amounts of data. When you move...

Row By Agonizing Row -- I'm surprised that you've never heard of it!

For each row in Employees you have to run the query (select min(id) from Employees group by employeeid,...

OK.

Still, wouldn't it be better to do this (set-based solution):

delete employees from employees a left join (select min(id) from employees group by employeeno, employeeid) b on a.id = b.id where...

Now that I read the article again, I come to these conclusions:

EmployeeNo and EmployeeID are duplicate fields in the Employees table

ID field only exists in the EmployeesCopy table because that...

Why not just do this?

Insert into EmployeeCopy

select * from Employee

UNION

select * from Employee

voila -- duplicates gone! However, they have to be duplicates in every field for this to work,...