nice, concise example to show someone why float is not a good solution for moeny. Thanks!

after you've created your new filegroup, this script might help: it writes the sql statements you could use to move some of your indexes; i've used it just for regular...

wouldn't the sp need to be recompiled after the table is truncated, as the previous executtion plan would probably be invalid? i would think the proc is slow because of...

here's a script i've used to generate the SQLs needed to change collation of a database for the existing items alzdba mentioned above;

I wouldn't try to modify this to fiddle...

you should change your design a bit;

your update trigger should populate a table of emails to be sent, and a job that runs every minute or five minutes or whatever...

i believe the issue is related to the way oracle 10 handles BLOB and CLOB columns;

if we don't use the updated drivers that are part of the Ora10 client install,...

this might be of some help; what SP is on your i searched the KB and found something that references the dccc shrink command on a win2K SP2; fixed...

I like David McFarlands idea; just looping thru the text of the view/stored proc/whatever object, looking for specific strings is MUCH better than trying to write a dynamic string reader to...

and comma delimited list after the FROM in case the older style join structure is used: FROM TABLE1,TABLE2 , TABLE3

which SQL server are you trying to connect to  from yuor host's web site?

part of your connection string: Data Source=hostsserver****,1433; is not really clear since it is...

If you've created any maintenance plans for those databases, this specific operation would be part of the scheduled job:

Data Base Maintenance>>Integrity Tab>>Checkboxes for Check Database Integrity & Include Indexes

you would...

Google and SQL Server Books On Line are your friends! use them first, and use the forums to clarify anything you didn't understand.

the first link in google for a search...

yes, you can directly restore a SQl 7 or a SQL 2000 database on SQL 2005, without any intermediate steps;

the restore process creates the mdb files in the SQL 2005...

could there be an open transaction on the server that runs indefinately? that or a table lock might lock up the query, even though normally it might be quick.

isn't this just a full outer join where the right table is null?

SELECT

 Spanish

 ,English

FROM

 Tbl1

FULL OUTER JOIN TBL2

ON Tbl1.Spanish = Tbl2.Spanish

     AND Tbl1.English = Tbl2.English

WHERE Tbl2.English IS NULL