Books Online - part of a standard SQL Server client install.

I think its one of those limits that, if you need to know, you probably should be rethinking your design. Not sure I'd want to debug something that goes...

If you are selecting the 'Y' records, then I would think an index would help. I don't like the idea of a separate table if, sometimes, you want all...

Is the development server single processor and production multi? I've had problems with parallel execution plans in the past. You can set the maximum degree of parallelism to...

If you're serching for 'Y', the query engine is going to do a table scan anyway but it would use the index for 'N'. So it depends on the...

Thre's always physical security. Stick it on a CD rather than a network drive. Keep a copy locked in a safe for comparison.

There is no such thing as 100% security - you just can make it more or less difficult for someone to break.

However you do it, if you add a checksum,...

cast(Null as varchar(20) ?

Seems odd. Do you need to use nulls at all? Better avoided. Empty strings or zeros should work.

I'd prefer to assign DATEADD(... GETDATE())...

I think you have another bad practice there - no housekeeping. Always explicitly drop a temp table as soon as you have finished with it. Remember that #...

The problem with SELECT * isnt so much the query performance per se but the bandwidth requirement returning the data. In most scenarios, you are generating far more network...

There was a long thread on this recently : http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=29&messageid=293555

If the index is clustered, random GUIDs aree going to generate lots of page splits on inserts.

This doesn't look like a production query as you have hard coded the numbers so speed shouldn't be an issue. A solution would be ... where personnum 595...

Do you really need every column of every row of every table in the view? Im sure that there must be a lot of redundant there. Some summary...

The important thing is whether you will be adding on to the end of the table (ie sequential keys) or inserting into the middle. If the latter, you will...

For basic security, all table access should be through stored procedures anyway so simply deny access to the relevant procedures. Nobody has direct access to the tables.