I have used views for that, but only for a very limited number of values, since it can't be effectively indexed.

Unique indexes are potentially extremely valuable, even for...

Or take a step back and consider whether "dob" shouldn't be stored as separate columns to begin with, in accordance with standard data normalization (if you need to constantly look...

While it's still available in the cache, just at it would be for index_usage_stats, you can likely use:
sys.dm_db_index_operational_stats

If the table is active, that data is very...

As a very slight simplification, you could also do this (I prefer CAST when possible since it's ANSI-standard, whereas CONVERT is not):

CAST((CP + 9) / 10 AS int)

The key thing to remember is this:
Data does not have to stored in physical sequence in order to be able to read in key sequence.

That is, the...

I certainly agree that the overhead of a variable isn't needed.

But tThe RIGHT function is going to implicitly convert the value to varchar anyway, so I would stick...

ALTER TRIGGER [dbo].[xxatr_slauf_AufartChangeU]
ON [dbo].[XXASLAuf]
AFTER UPDATE
AS
SET NOCOUNT ON;
IF UPDATE(aufart)
BEGIN
  DECLARE @aufintnr VARCHAR(8000)
  SET @aufintnr = ''
  SELECT @aufintnr...

Best practice is to explicitly specify the table name/alias for every column in a query.  Otherwise, if one of the tables adds a column with the same name, the same...

Other issues:
1) if there's an error in a db file (such as would show up in a DBCC CHECKDB), it won't reattach
2) during a reattach, the file gets...