IMAGE, TEXT and NTEXT data types are stored and accessed differently from other data types.  Basically they are stored with a 16-byte binary pointer.  This means that access to the...

I wouldn't recommend it.  SQL Server will not know how to decrypt and run your stored procedure if you tried to encrypt it using this package.  "WITH ENCRYPTION" is the...

I reviewed the barcode TTF for Code 128, and it appears that the codes for "C" and "F" were not saved correctly.  I suspect it had something to do with...

Hi Greg,

Thanks for the feedback.  There are two issues with trying to decrypt data which has been encrypted using another package (like the .NET System.Security.Cryptography namespace classes):

You've already encountered the...

Here's another version of the Easter Calculation algorithm:

http://sqlservercentral.com/cs/blogs/michael_coles/archive/2005/07/16/49.aspx

And something for calculating "floating" American holidays:

http://sqlservercentral.com/cs/blogs/michael_coles/archive/2005/07/17/52.aspx

Hi Phoebe,

I don't have access to a SQL 7 installation to see what would be required to make it work on SQL 7.  The XP's themselves are standard XP's based...

If you want to "appeal to authority", check out Celko's SQL Style book.  He gives a well-rounded discussion of his interpretation of ISO naming convention standards.

Sorry for the misunderstanding.  As I pointed out in another post, if you are using the strDescription column as any part of the PK, then you will be duplicating the...

Sorry about the confusion.  Yes I am talking about using the column strDescription as the PK, or even as part of the PK.

If we imagine a single PK in the...

As long as we're beating the dead horse, might as well break out the shotgun:

I'm thinking along similar lines as you with the declaration of the primary key.  We obviously...

What columns unqiuely identify each row of the generic lookup table?

Per the implementation in the article I can add the row (16, 'CA', 'CALIFORNIA', 'Postal.State') even though the row (16,...

Notice that the name "Automobiles-to-Zipcodes" requires a quoted identifier.  See Joe Celko's SQL Programming Style, Chap. 1.1.2 ("Avoid All Special Characters in Names") and 1.1.3 ("Avoid Quoted Identifiers").

Yeah, SQL Server generates some pretty good change scripts that you can copy and paste into QA; but if you run the changes directly from EM you can end up...

Not even with Indexed Views which speaks volumes about their "usefulness".

Like I said, dynamic SQL and modifying the tables themselves are a way to do this and maintain proper DRI.

And...

One solution might be to create views which could be altered later if the user wanted to change attribute sets, or you could dynamically generate SQL queries.  You can ensure...