DECLARE @sSQLSELECT VARCHAR(8000)

DECLARE @sSQLFROM VARCHAR(8000)

DECLARE @sSQLWHERE VARCHAR(8000)

SET @sSQLSELECT='SELECT .......'

etc

EXEC( @sSQLSELECT + @sSQLFROM + @sSQLWHERE)

Think of the BEGIN and END statements in TSQL as being like the curly braces in JavaScript, C#, C++, C, Java etc.

BEGIN = {

END = }

As with these languages TSQL...

If possible I try and avoid SHRINKFILE in live systems because there is an overhead in growing the file as data is put back in.

There is no direct equivalent.

You could try using the TOP predicate to return the TOP 1

The users within a database have a SID column which matches to the SID value of the login.

If you transfer your logins first then restoring your database will maintain your...

Yep, no DRI.

A few years back there was an discussion on this site about leaving out DRI in order to get the maximum throughput on the database. 

The example given...

In the particular vendor database (I stress vendor) it held a list of countries.

The problem you face with a database with thousands of tables are

• Comming up with a meaningful, common-sense...

Over and above the previous answer

A Primary key cannot contain nulls.

A unique index can contain a single null.

A clustered index holds its data in the leaves of the index.  You...

A login within SQL Server has a unique identifier called a SID and an encrypted password.

The way I do it is to use a SQL query to generate the sp_addlogin...

If you have 3,000 or more tables then having a meaningful naming scheme for your tables becomes VERY important, otherwise your developers get lost in the mire.  This was one...

Its is great trying to maintain hundreds of tables when the tables have meaningless names.  Anyone care to guess what A35020 holds?

Don,

In your example the Id field is an IDENTITY field and therefore there is no way that EmployeeTypeId can return an entry for CompanyStatus or whatever.

If you are talking about...

I am still in the dark as to why my MUCK table with a single field primary key can break referential integrity.

If I've got a contacts table with an AgeBandId...

OK, who has the time to design, code and test a database that needs 300+ lookup tables within the time that management have been promised the finished application

I had an application where "best practice" described in this article would have resulted in around 300 lookup tables averaging 7 entries per table.

A single table with and id, type,...