Comments on: Beware Vendor Databases http://sqlchicken.com/2009/12/beware-vendor-databases/ SQL Server DBA Tips & Tricks Thu, 09 Feb 2012 21:40:16 -0500 hourly 1 http://wordpress.org/?v=3.3.1 By: Jorge Segarra http://sqlchicken.com/2009/12/beware-vendor-databases/comment-page-1/#comment-382 Jorge Segarra Wed, 06 Jan 2010 01:22:03 +0000 http://sqlchicken.com/?p=497#comment-382 Good call Joseph (on the QA). I especially like your awareness of SQL Express' action of turning AUTO_CLOSE to on, many wouldn't think to look at something like that. QA review is something we should all try and practice even if you don't have something official setup we can definitely benefit from doing something on our own (like you have!) Good call Joseph (on the QA). I especially like your awareness of SQL Express’ action of turning AUTO_CLOSE to on, many wouldn’t think to look at something like that. QA review is something we should all try and practice even if you don’t have something official setup we can definitely benefit from doing something on our own (like you have!)

]]> By: Joseph Abreu http://sqlchicken.com/2009/12/beware-vendor-databases/comment-page-1/#comment-381 Joseph Abreu Mon, 04 Jan 2010 20:03:37 +0000 http://sqlchicken.com/?p=497#comment-381 I believe this happens most often with databases developed in SQL Express by developers and then packaged without any DBA review or SQL Server quality analysis of those packaged databases. AUTO_CLOSE defaults to enabled in every SQL Express environment I've set up for development and I have it on my checklist of items to review whenever restoring/attaching databases provided by a developer/vendor other than myself. As for sysadmin requirements by vendors, haven't developers ever heard of using roles before??? I'm sure their application went through a QA process but often the database they provide with their application doesn't get as thorough of a QA review from the perspective of a DBA. I believe this happens most often with databases developed in SQL Express by developers and then packaged without any DBA review or SQL Server quality analysis of those packaged databases. AUTO_CLOSE defaults to enabled in every SQL Express environment I’ve set up for development and I have it on my checklist of items to review whenever restoring/attaching databases provided by a developer/vendor other than myself.

As for sysadmin requirements by vendors, haven’t developers ever heard of using roles before??? I’m sure their application went through a QA process but often the database they provide with their application doesn’t get as thorough of a QA review from the perspective of a DBA.

]]> By: Jorge Segarra http://sqlchicken.com/2009/12/beware-vendor-databases/comment-page-1/#comment-369 Jorge Segarra Tue, 29 Dec 2009 11:54:31 +0000 http://sqlchicken.com/?p=497#comment-369 Ha, sorry to hear that Kelly! One thing I learned from Jonathan Kehayias is that you can work with the vendor to help them figure out exactly what they really need. Not only will you be doing them (and any future customers) a favor but you'll be honing your skills as well. Run a server-side trace on the database and take a look at exactly what the application is doing. If its only doing SELECT calls or maybe executing some stored procedures at most then they definitely don't have a case for sysadmin rights. Ha, sorry to hear that Kelly! One thing I learned from Jonathan Kehayias is that you can work with the vendor to help them figure out exactly what they really need. Not only will you be doing them (and any future customers) a favor but you’ll be honing your skills as well. Run a server-side trace on the database and take a look at exactly what the application is doing. If its only doing SELECT calls or maybe executing some stored procedures at most then they definitely don’t have a case for sysadmin rights.

]]> By: Kelly http://sqlchicken.com/2009/12/beware-vendor-databases/comment-page-1/#comment-368 Kelly Mon, 28 Dec 2009 22:38:02 +0000 http://sqlchicken.com/?p=497#comment-368 OMG!! I feel your pain. I still have a vendor crying that they need sysadmin rights on the production database. The whole thing is a port from MySQL and I don't think any of their developers know what an index is. But I guess that's what we get paid for. OMG!! I feel your pain. I still have a vendor crying that they need sysadmin rights on the production database. The whole thing is a port from MySQL and I don’t think any of their developers know what an index is.

But I guess that’s what we get paid for.

]]> By: Tweets that mention Beware Vendor Databases | The SQL UPDATE Statement -- Topsy.com http://sqlchicken.com/2009/12/beware-vendor-databases/comment-page-1/#comment-367 Tweets that mention Beware Vendor Databases | The SQL UPDATE Statement -- Topsy.com Mon, 28 Dec 2009 21:53:08 +0000 http://sqlchicken.com/?p=497#comment-367 [...] This post was mentioned on Twitter by Jorge Segarra, Max Trinidad. Max Trinidad said: RT @SQLChicken: [NEW BLOG POST]: Beware Vendor Databases http://bit.ly/8ax0HZ #sqlserver #sqlhelp Very Interesting blog!! [...] [...] This post was mentioned on Twitter by Jorge Segarra, Max Trinidad. Max Trinidad said: RT @SQLChicken: [NEW BLOG POST]: Beware Vendor Databases http://bit.ly/8ax0HZ #sqlserver #sqlhelp Very Interesting blog!! [...]

]]>