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?
Just say No to Facebook!