Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. Database & SysAdmin
  3. Database
  4. SQL Server Speed

SQL Server Speed

Scheduled Pinned Locked Moved Database
databasesql-serversysadminperformancequestion
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • 3 Offline
    3 Offline
    3fonov
    wrote on last edited by
    #1

    What can cause slowness of SQL Server 2005 Enterprise? When start same DB on Enterprise and Express, express are mach more faster (100 times) Thanks for advises.

    M 1 Reply Last reply
    0
    • 3 3fonov

      What can cause slowness of SQL Server 2005 Enterprise? When start same DB on Enterprise and Express, express are mach more faster (100 times) Thanks for advises.

      M Offline
      M Offline
      Mike Dimmick
      wrote on last edited by
      #2

      Typically your databases on Express are set to the Simple recovery model. This keeps only the transaction logs required to roll back active transactions. It rapidly overwrites the log records once the corresponding transaction is committed. In contrast databases on the true server editions of SQL Server default to the Full recovery model, which logs everything that's done and keeps log records until the log is backed up, in order that recovery can occur to the point of failure if the data files are lost (and you restore a full backup). If you're not backing up the transaction log through a SQL Server-aware product, they simply keep growing. This may well take longer to scan on opening a database. Also, SQL Server Express Edition only actually opens databases and performing the roll forward of logged committed operations and rollback of logged uncommitted operations when that database is accessed (this is the 'auto close' option). The full editions of SQL Server open and recover all database at service startup. The time to perform recovery is also affected by the disk subsystem you're running the process on - it will be directly proportional to the read speed of the disks. If you're running on RAID 5, check that you haven't got a failed disk - your read speed will have gone through the floor. You will also get a complete failure if another drive fails.

      Stability. What an interesting concept. -- Chris Maunder

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups