Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

How DBAs Manage SQL Server Express for Applications Expand / Collapse
Author
Message
Posted Monday, January 31, 2011 12:10 PM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: 2 days ago @ 9:59 AM
Points: 886, Visits: 1,544
I know there's no Express for Applications like there is VB for Applications (called VBA) but there are a lot of Express installs that are application specific.

My question is what do you more seasoned DBAs do about managing the SQL Server Express installs that are application specific, setups of Express done by the installation of some application.

Do you treat them like your regular SQL Server installs, creating best practice like login /accts for it to use and setting up backups and so on or do you take a hands off approach and let the person who is in charge of the application that uses the SQL Express instance also deal with the SQL Express instance?

If you have IT Admins installing applications that include an install of SQL Express that the apps install configures and what not do you still actively try to manage it like its one of your regular SQL Server instances or do you take a hands off approach and opt to let whomever is responsible for the application also be responsible for the SQL Server Express instance it is using?

Recently we’ve had several instances of Express installed on different systems, all part of an application install. I started to go thru each and set up everything (Monitoring jobs, Logins, the whole 9 yards) but then I thought that perhaps I should not be doing this and opt instead to let the Express install be handled as part of the application itself. I had such a hard time trying to get any “How To setup/Configure SQL Server Express” documentation for any of these apps that installed express that I decided to consider treating them as any other application that doesn’t use SQL Server, that is let someone else manage them.

Thoughts? How do you handle application specific installs of SQL Express Version XXXX?

Thanks


Kindest Regards,

Just say No to Facebook!
Post #1056364
Posted Monday, January 31, 2011 12:20 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 10:31 PM
Points: 3,116, Visits: 11,388
I go with "Don't ask, don't tell".

We have about 300 instances of SQL Server Express/MSDE/etc. that I know of, so I just leave them alone.

I have enough to worry about with our 300 "regular" SQL Server instances.



Post #1056376
Posted Monday, January 31, 2011 12:24 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 5:23 PM
Points: 6,131, Visits: 7,170
When an application installs Express, it usually is expecting complete control over the server itself. They're coding it for non-IT people to be able to use the product and completely hands off the database.

I let it do this unless I'm directly invited into the process/problem. Unless *I'm* the one advocating the Express, I'm going to assume the Application is going to handle everything it needs to.

If not, it needs to get off Express and into one of my real servers, and the application is done being allowed to do anything it wants at the server level willy-nilly. Kind of all or nothing. I don't want half the power and all of the responsibility.



- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions | Forum Netiquette
For index/tuning help, follow these directions. |Tally Tables

Twitter: @AnyWayDBA
Post #1056379
Posted Monday, January 31, 2011 12:51 PM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: 2 days ago @ 9:59 AM
Points: 886, Visits: 1,544
Michael Valentine Jones (1/31/2011)
I go with "Don't ask, don't tell".

We have about 300 instances of SQL Server Express/MSDE/etc. that I know of, so I just leave them alone.

I have enough to worry about with our 300 "regular" SQL Server instances.




So your saying a formula of "Don't Ask + Don't Tell = Don't Manage" is the rule of thumb for this?

Thanks


Kindest Regards,

Just say No to Facebook!
Post #1056391
Posted Monday, January 31, 2011 1:01 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 10:31 PM
Points: 3,116, Visits: 11,388
YSLGuru (1/31/2011)
Michael Valentine Jones (1/31/2011)
I go with "Don't ask, don't tell".

We have about 300 instances of SQL Server Express/MSDE/etc. that I know of, so I just leave them alone.

I have enough to worry about with our 300 "regular" SQL Server instances.




So your saying a formula of "Don't Ask + Don't Tell = Don't Manage" is the rule of thumb for this?

Thanks


It is for me, but that doesn't mean it's the right thing for your organization.

Our instances are mostly imbedded in backup software, software distribution servers, and other vendor supplied apps. There are no instances of custom applications; those go on regular SQL Servers.



Post #1056402
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse