Run the same script again in one month.

If that results in '%_obsolete_obsolete' tables, that would mean it hasn't been used for a month, so maybe good candidate for cleanup.

use enterprise manager, double click the job, (i.e. rightclick job, properties)

Alter the jobowner.

For backup jobs, we prefer using sa as jobowner to avoid all issues with windows accounts. (a...

Keep in mind :

(from BOL)

The recovery interval option does not affect the time it takes to undo long-running transactions. For example, if a long-running transaction takes two hours to perform...

Maybe you can use this:

dbcc checkdb (yourdb) WITH ALL_ERRORMSGS, DATA_PURITY

BOL says

DATA_PURITY

Causes DBCC CHECKDB to check the database for column values that are not valid or out-of-range. For example, DBCC...

You restruct queries on using over a certain governer cost.

But that setting goes for _all_ queries !

EXEC sys.sp_configure N'query governor cost limit', N'300'

RECONFIGURE WITH OVERRIDE

or you can shut down parallelism...

And then there is SOx :blink: ...

Nowadays we implement a service account per service. The corresponding passwords are guid-like strings, so only usable for install using an INI file.

We...

And probably you would be better off by first renaming your tobe obsolete tables, and removing them only a couple of months later

EXEC ('if 0 = (SELECT count(*) as rowCnt...

... san vendor install technician knowledge ...

Altough most SAN vendors nowadays have their own white papers for hosting databases on their san system, many technicians just don't have a clue...

- be carefull with sysindexes, because it may have an estimate count.

- adapt your script:

e.g. like this

EXEC ('if 0 = (SELECT count(*) as rowCnt from ['+@schema+'].['+@tableName +']) drop table...

Brad M. McGehee (6/26/2008)

---

When I am in a "work" environment, I call myself a DBA. If I am in a "non-work" environment, I call myself a "computer geek." When I...

you don't. 😉

- Use datatime datatype for date or time or datetime columns.

This way you are sure valid dates are entered, and you have a bunch of datetime related...

it should be ok, as long as they fix the issues that are detected.

1) read BOL. it has very good info regarding how transaction logs work and how to backup.

2) backup log

BACKUP LOG [yourdb] TO [yourdbLogBUDevice]

WITH NOINIT , --...

We use this:

With every backup job, we create backups to local drives (san or not), if available to a separated drive (non-data-files, non-log-files).

The last step of every backup job copies...

Just to add to Gails remark:

this is stated in BOL topic: "alter database"

TORN_PAGE_DETECTION { ON | OFF }

ON

Incomplete pages can be detected by the Database Engine.

OFF

Incomplete pages cannot be detected...