Named Instances - Pros & Cons

  • I have a SQL app that used to be a MS Access app.  The app creates snapshots of data.  In the old MS Access version it would create a new mdb with each snapshot.  The new app creates a new SQL DB with each snapshot, hence my Enterprise Manager DB list is rapidly becoming cluttered with many tiny db's.  It's becoming a bit of a pain to navigate around these now in EM.  It's a vendor app and I have no control over how it works.  I'm thinking that maybe I should move this app off into a separate instance of SQL to help with the organization & administration of these db's.

    Before doing so I would like to get up to speed on any of the pros, cons &  considerations of using named instances in SQL 2000.  Any references to articles, war stories or opinions are welcome.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply