Level 400 Microsoft SQL Server Performance Monitoring and Tuning Webcast

Ramesh Meyyappan’s webcast about Microsoft SQL Server Performance Monintoring and Tuning.

Full with practical examples and real world scenarios.

If you signup to the Email Updates you will receive the scripts used in the webcast.

Oracle Patching – PSU or CPU ?

Any clue don’t use PSU (Patch Set Updates) ?

As described in Oracle Metalink Note 854428.1 switch back to CPU “…would require significant effort, and so is not advised”.

Please comment.

Performance Issues After Migration To SQL 2005

During reading support forums i found many issues related to performance after migrating to SQL 2005.

Some advice to increase performance:

- Rebuild indexes (DBCC DBREINDEX)

- Update statistics (SP_UPDATESTATS)

- Check the compatibility level of the database in question.

If the compatibility level is set to 80 (SQL 2000)  change it to 90 (SQL 2005).

The compatibility level is not really related to performance but needed for use new features released with SQL 2005.

Oracle Grid Control Repository Database ORA-0600 [17059]

During the daily database check i found error ORA-0600 [17059] in the alert log of the repository database (Release 10.2.0.3, Linux x86].

Error occured during weekend and a high amount of trace- and dump-files are generated and fill up the file system.

Investigation at Oracle Support show me that the Oracle Bug 5705795 (Doc ID 4167271) caused the problem.

I download Patch 5705795 for our linux system.

 (You need Patch 5731535 if using windows).

Stopped agent, opmn and iasconsole, shutdown the repository database and applied the patch.

After restart all oracle processes and the repository database the error no longer occured in the alert log.

But this time i found another error in the log (ORA-07445 [lstclo()+45] [SIGSEGV] [Address not mapped to object].

In my case the error occured because i don’t shutdown ALL databases which shared the same ORACLE_HOME.

The second database was open and caused the problem.

After bouncing and restart this database the error was cleared.

Recommendable SQL Server Posts – July 2008

Very interesting post from James DiMauro on SQLServerCentral.com about recovering a database when transaction log deleted, no backup available and you couldn’t set the database in emergency mode.

Recover database when transaction log deleted