Hi all,

perhaps I found the reason. I experienced the same problem: somethimes querying the table I had a "floating point exception" and a "Number out of range" message. Looking at...

Well, I solved my problem. The execution plan in Query Analyzer showed me that were involved tables even if actually they weren't. Using SET STATISTICS IO I could see that...

Verify your network connection and disk space.

Furthermore, use the task manager to check load on your CPU.

Are you sure to perform the query against the same DB as others, and...

Well, I'm using SQL Server 2K Enterprise Edition.

Yes, I created every single table with the following script, and as you can see there's the right (I hope) check constraint (my...