Есть необходимость проводить переодические проверки на N серверах на предмет состояния баз и прогнозирования возможных проблем. Есть мысли что должно проверяться?

Для SQL Sever было вырабато вот это:

автор 1. Backups
a. Are databases being backed up?
List databases that have never been backed up
List databases with no backup in the last 24 hours
b. Are databases in Full recovery mode having transaction log backups?
List Full recovery mode databases that have never had a transaction log backup
List Full recovery mode databases with no transaction log backup in last 24 hours
c. List production databases using Simple and Bulk-Logged recovery modes (covered in 5.a)
d. List server disks with insufficient free space for the next full backup – this script can be helpful to prevent ‘not enough space’ issues. I have this set up on my PC.
e. How frequently are backups scheduled? If using a Maintenance Plan, what is the retention periods of the files compared to the frequency of backups?
2. Security
a. List all SQL Logins with system role access
b. List all SQL logins that are database owners
c. List all SQL login passwords that are Null, identical to the SQL Login, are “password” and are less than 5 (this might not be possible by means of TSQL) characters long
d. List if the Built-in\Administrators access is enabled
e. List if the default port of 1433 is used
f. List non default connection protocols (Defaults are Named Pipes and TCP/IP)
g. List Authentication (Windows is preferred or mixed (i.e. Windows and Standard))
h. Identify cross-database access for SQL Server logins
i. Linked servers
j. Flag if the server is publicly visible on the LAN.
k. Flag if the sa login is not locked.
l. Flag if the sa login has the default password.
3. Maintenance
a. Are indexes being rebuilt (i.e. Maintenance Plan to re-organisation of pages)
b. Report if the “Auto close” and “Auto shrink” database options are set
c. Report if the “Auto update statistics” and “auto create statistics” database options are not set
d. Transaction log > 50% of data file allocation and data file allocation over 100 MB
e. Data files with > 50% free space and data file allocation over 100 MB in size
f. Check that there is enough disk space for next file extension
g. Are regular database integrity checks performed
i.e. DBCC CheckCatalog, DBCC CheckAlloc, DBCC CheckDB, DBCC ShrinkDatabase, DBCC ShrinkFile
h. Report on databases that can not automatically grow their files
i. Report on database maximum file sizes
j. Report on file growth parameters of databases > 10 GB (i.e. by fixed MB or by percentage)
k. Report on databases with default file growth settings for data files and transaction log files. Report databases where growth value in MB is not at least 10% of the current data size.
l. If transaction log is not set to auto-grow, ensure maintenance is in place to backup the log to ensure completed transactions are cleared out.
4. SQL Server Configuration
a. Report full version and highlight less that or greater than 8.00.818
b. Report on Windows services MSSQLServer and SQLServerAgent start status
Must be manual on clustered servers but good idea to be automatic on non-cluster servers
c. Report if memory is limited
d. Report if other SQL Server add-ons such as Analysis Services, Reporting Services, etc are used.
e. Do the Pubs and Northwind databases exist?
f. Report if default server collation is non-standard.
g. SQL Mail is not configured.
h. Report on accounts used to run MSSQLServer, SQLServerAgent, and other SQL Server related services – ensure separate accounts used for each instance and obtain passwords where possible
i. Identify where > 2GB memory exists on the server and whether the appropriate switch is set to allow memory access above 2GB
5. Database Configuration
a. Report on database recovery mode (i.e. full, simple, bulk-logged)
b. Report if database compatibility level is lower that 8.0
c. Report if database access is restricted to “Single user” or members of “dbo_owner”, ”dbcreator” and “sysadmin”.
d. Report if database is set to “Read-only”
e. Report if database collation is different from the default SQL Server collation
6. Error Logs
a. List all errors in the SQL Server and SQL Agent Error logs
b. Identify logging level (all, failure, success etc)
c. What size is current and last 3 error log files
7. SQL Agent Jobs
a. Jobs that have failed
b. Jobs not scheduled to run
c. Jobs with no notification set.
d. Jobs enabled but not scheduled

Хотелось бы подобный список для DB2

ggvне, я так понял, что "чукча не читатель, чукча писатель" - читать не интересно, интересно все и сразу.

Интересно не все и сразу а направление откуда рыть. По-моему это очевидно.

Батюшки, свет!?!? Неужели в DB2 Information Center надо было заглянуть? Какой я невнимательный! Ужас.

PS А менее хамски писать коран не позволяет?