If you don't have the opportunity, I would be willing to host it on my site.

Apart from being interested myself in the tool...

FWIW, http://support.microsoft.com/default.aspx?scid=kb;EN-US;305977 

Apart from what has been said already above, see if this provides additional help:

http://www.karaszi.com/sqlserver/info_datetime.asp

You should the explanations on "safe" and "independent" date formats.

It depends. Stored in a DATETIME are the clock ticks since midnight. Every second consist of 300 ticks. They are more precise than @@TIMETICKS.

See if this helps:

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx

Just throwing in a link, which might also help here:

http://www.microsoft-sap.com/

And honestly, I think an online community can't help you much with this question. That depends on too many factors...

While 8060 is the max size, there are circumstances where this doesn't hold true, if I understand it correct.

This might provide additional interesting informations:

http://www.sql.co.il/ug/01/Row%20Size%20Riddle.ppt

http://www.sqlservercentral.com/columnists/sjones/pagesize.asp

Apart from this being a merely presentational issue, have you searched the script section here already. I think Antares686 posted something useful there.

UniqueIdentifier is recomended by most of the techies

Curious, what techies you have in mind here?

As for the thread: athurgar already hit the nail...

Allow me to jump right in?

Any ideas on how to fix this without re-writing my views/queries?

I'd say, you're caught in a typical Access...

I'm not aware of a workaround, but this might be interesting to you:

http://msdn.microsoft.com/sql/default.aspx?pull=/library/en-us/dnsqldev/html/sqldev_02152005.asp

the actual datetime datatype is stored as two numbers that specify the number of days since Jan 1, 1900 and the number of milliseconds since midnight

That's incorrect information from BOL.

Now, the second 4...

Maybe this provides additional information:

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx

See if this helps:

http://www.microsoft.com/resources/documentation/sql/2000/all/reskit/en-us/part3/c1161.mspx

Honestly, though the code of such a product like a RDBMS is surely very complex, I guess you'll find your way through when you work each day with it. If...