You are right. I should add that I'm not advocating using an index hint nor would I ever advocate that to someone.

Index hints should only be used by trained...

>> change it to simple before doing a bulk operation

Did you mean to say change it to bulk-logged before doing a bulk operation?

Bulk logged recovery does not act like simple...

>> Select * From MyTable Where MyDate > '1/1/2006' And MyOtherField = 'Jack'

might use the NC index, or might not.

That's what I said. I said these queries MAY NOT use...

What you stated above is that the "Collation for entire server is: SQL_Latin1_General_CP1_CS_AS". Databases can have a different collation defined and it is database level collation that governs the rules...

The only major difference other than the one mentioned in your question is that Full is the only recovery model that supports point in time restoration. Bulk logged (and simple)...

Possible reasons for using a table scan instead of an index:

1. The query plan is cached and it is reusing the cached plan instead of looking for a better way. See...

Personally, I would never advocate using a uniqueidentifier for your primary key. All of your indexes will be bigger and slower.

Nonetheless, if that is what your are doing, I suggest...

What is the "this" that you read today?

It works for Drop statements as well. I think they really missed the boat by not making rename part of the Alter Table statment.

Using ADO.Net 2.0 is a better option than a load balancing box.  ADO.Net 2.0 is mirroring aware. You can specify the mirror instance in the connection string and it will...

According to BOL in reference to P2P replication: All participating databases should contain identical schema and data

He doesn't want identical data.

>> it should not happen

You keep using that word. I do not think it means what you think it means.

Tell us what you are trying to accomplish, and we'll...

Here is a simpler version of that function:

CREATE FUNCTION dbo.RemoveChars(@Input VARCHAR(1000))

RETURNS VARCHAR(1000)

BEGIN

       While PatIndex('%[^0-9]%', @Input) > 0

         Begin

             Set @Input = Stuff(@Input, PatIndex('%[^0-9]%', @Input),...

I would definitely be worried if my server's performance was so poor that shortening a query by 13 characters made it run faster.

Are you updating one row at a time? If so, I would suggest selecting the data into a "work" table that isn't replicated, perform the data manipulation in the work table,...