That makes sense.

GSquared (5/13/2008)

---

(As an aside, please keep the code a little narrower. I dislike horizontal scrolling. Not a big deal, but I'd appreciate it.)

Nope. No explanation for that....

Matt Miller (5/13/2008)

---

I know:) Concatenation is different.:D

It just seems inconsistent behavior. As in -

Primary Key - trim it

comparison - trim it

concatenation - don't trim it

storage - don't...

Matt Miller (5/13/2008)

---

GSquared (5/13/2008)

---

I just checked my databases and servers, and ANSI padding is False on all of them, but per BOL:

Important:

In a future version of SQL Server...

It looks as though the ANSI_PADDING setting is taken from the connection NOT the database default. I ran the following in 2 databases (AdventureWorks which had ANSI_PADDING ON and...

I error out on this as well, but even if I run SET ANSI_PADDING ON this code errors out as well.

But try this:

SET Ansi_Padding ON

CREATE TABLE #T(k VARCHAR(10))

INSERT #T

SELECT 'a'...

I just checked all my servers (2005 and 2000) and in the model database ANSI PADDINGS is false meaning OFF and I have never messed with the default on a...

Kelvin,

Thanks for the positive feedback.

Have fun with creating the custom component. I have considered it, but I am not confident/comfortable in .NET and have not found a custom component...

GSquared (5/13/2008)

---

(Your test data doesn't work as written, since you tried to insert the value 1 into your ID field twice, after defining it as the primary key.)

Yes, your tests...

How about the "rules" for this process? I think it is way too complex to try to figure out all the rules from the code.

You may want...

See this is why I always post, I can be wrong and learn something. Here is what I tried before I answered though.

Switched AdventuteWorks to Full Recovery

Started a...

serge.laot (5/13/2008)

---

Yes, but this is not the problem.

The exact problem is that for SQL norm if you compare two string with different lengths the first thing done by SQL is...

To my knowledge SQL Server will not allow you to run a full backup and a transaction log backup concurrently so whichever one that starts first will "win".

Reindexing will definitely grow the log file. I would just run my full backup and a TX Log backup after the reindexing job

Begin Try

Begin Transaction

Update source set model = 1 where client 2

COmmit Transaction

End Try

Begin Catch

Rollback transaction

End Catch

Begin Try

Begin Transaction

UPdate...