Blog

  • Note: While the information below specifically pertains to SQL Server 2005, the concept is the same for both version 2000 and 2008.

    Shinking an MS SQL Server 2005 transaction log may be necessary if the log file grows too large due to missed backups or an extended period of high database activity. The transaction log backup will clear the log out but its size remains until the administrator manually

    October 6, 2010
  • Back in the old’n days (pre 9i) renaming an Oracle database meant modifying your control file, manually changing the name within the data dictionairy in multiple places, then finally changing the name in any external configuration files and scripts.  The process has been streamlined a bit since then with the introduction of the Oracle dbnewid utility, nid.  DBNEWID will update your

    October 6, 2010