Barkingdog (4/18/2010)

---

That was helpful.

Would this interpretation of the original code be correct?

Tom.Thomson (4/16/2010)

---

...I would stick to your original description of item-wise checking for this application despite hashbytes (MD5) being vastly better than checksum.

TheMastermind (4/16/2010)

---

Sorry! I thought anyone would be able to grasp the ABC psudocode :-).

klininger (4/16/2010)

---

Or, is there a suggestion box where I can start a petition for this to be an option rather than a feature I don't want?

dachen (4/16/2010)

---

what would be the best way to do this without updating records. i need to have traceability into what changed.

Stefan_G (4/17/2010)

---

You should also consider permanently changing the datatype of this column to datetime, or perhaps time.

Stefan_G (4/18/2010)

---

...the reason I use sys.columns is that it is slightly more efficient than sys.all_columns. sys.columns only accesses a single table, while sys.all_columns is a join.

george sibbald (4/18/2010)

---

It does the same as any other full backup, it takes the active part of the transaction log so the database can be restored to a consistent point.

vmssanthosh (4/18/2010)

---

hi

This is my way..

declare @date varchar(100)='201012'

select convert(varchar(6),dateadd(M,1,convert(date,@date+'01')),112)

Dobermann (4/18/2010)

---

Yes, I agree. Since I was creating a new table though, I knew it had but the one PK and did not have to worry about declaring clustered.

Tom.Thomson (4/18/2010)

---

Hey, Paul, for once we agree that some bad wording is a bad thing, not a minor point. Is this a record?