I just tried the following and didn't get the results I thought I could:

select cast(convert(money,'2,199.8352') as float)

result: 2199.8352  (this is good)

select cast(convert(money,'2.199,8352') as float)

result:Server: Msg 235, Level 16, State 1,...

I thought of doing that but the precision only goes out to 4 decimal places.  There is a possibility of more.

It's pretty obscure but I was actually having this problem in an application I was working on.... it was giving me a 644 error and I found this article on...

Ahhhh....that makes sense now.

Hopefully SP4 will be out of beta soon and the 'problem' with unicode will be completely resolved.

This is more of an exercise for me to see how much impact unneccessary indexing has on the larger tables....not so much what I will be practicing in the production environment. ...

Yeah I noticed that....the script that I am running is for maintenance only and not for any kind of oltp actions so I should be okay in that respect. 

Essentially...

Awesome.  This is exactly what I was looking for.  Thanks.

I was looping through all columns in all tables using the 'sysobjects' and 'syscolumns' tables to run a basic selectivity query to determine which columns should be indexed or not.

That...

Okay that works. 

Thanks!