INF & IND errors

How do I update or delete a record with this floating point error in X
field? And, what the heck causes it?
Thanks!
Chris
Are you seeing 1.#inf values? That generally has something
to do with Microsoft's implementation of the IEEE standard
for floating point values - there are some values where the
representation of the value gets hosed out.
Are you trying to use column X in the where clause of your
delete or update statement?
-Sue
On Fri, 7 Oct 2005 10:43:54 -0400, "Chris Marsh"
<cmarsh@.synergy-intl.com> wrote:

>How do I update or delete a record with this floating point error in X
>field? And, what the heck causes it?
>Thanks!
>Chris
>

INF & IND errors

How do I update or delete a record with this floating point error in X
field? And, what the heck causes it?
Thanks!
ChrisAre you seeing 1.#inf values? That generally has something
to do with Microsoft's implementation of the IEEE standard
for floating point values - there are some values where the
representation of the value gets hosed out.
Are you trying to use column X in the where clause of your
delete or update statement?
-Sue
On Fri, 7 Oct 2005 10:43:54 -0400, "Chris Marsh"
<cmarsh@.synergy-intl.com> wrote:

>How do I update or delete a record with this floating point error in X
>field? And, what the heck causes it?
>Thanks!
>Chris
>

Indexes? When should they be used?

When do we should not use the indexes?

In Inserts? In Updates? in Deletes?

If i have a massive delete like:

delete from table1 where column1='X' (2 million rows) should i have the index enabled or not?

Whats the best option? To disable indexes on massive inserts and then rebuild or to delete and recreate?

Best Regards

Luis,

You may find this thread useful.

My guess is that it may be more efficient to drop the indexes, do the action, and then rebuild the indexes. (However, that depends upon having either, 'down time' with little user activity, OR SQL 2005 Enterprise edition.