SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


How DBAs Manage SQL Server Express for Applications


How DBAs Manage SQL Server Express for Applications

Author
Message
YSLGuru
YSLGuru
SSCarpal Tunnel
SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)

Group: General Forum Members
Points: 4224 Visits: 1667
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!
Michael Valentine Jones
Michael Valentine Jones
SSChampion
SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)

Group: General Forum Members
Points: 13651 Visits: 11848
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.
Evil Kraig F
Evil Kraig F
SSCoach
SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)

Group: General Forum Members
Points: 19307 Visits: 7660
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
YSLGuru
YSLGuru
SSCarpal Tunnel
SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)

Group: General Forum Members
Points: 4224 Visits: 1667
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!
Michael Valentine Jones
Michael Valentine Jones
SSChampion
SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)SSChampion (13K reputation)

Group: General Forum Members
Points: 13651 Visits: 11848
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.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search