May 4, 2016 at 7:53 pm
Hi Guys,
I have a new SQL2014 instance for a new vendor system.
The vendor wants to save time by restoring a copy of the database, whereas I'd ordinarily CREATE a new database for a new system.
My questions is: can I take their word that the database is free of dubious history and legacy artefacts or should I insist on a new, clean database?
Thanks,
Steve.
May 4, 2016 at 8:44 pm
I would have no problem restoring the vendor's database. Unless you have reason not to trust the specific vendor, and even then I'd probably ask for the backup to review and restore myself.
You expected them to create a new (empty) database, and then create scripts that create the tables, stored procedures, etc., and insert data that is required for the database to be in a usable state (lookup tables for example)? That seems quite a time consuming and unusual approach to get a copy of their database onto your new system. Remember, the database they're trying to get you to restore isn't a blank slate, it's the storage side of their existing product, which could have quite a complex structure even if it doesn't contain any of your business's data in it yet.
I suppose an exception could be if your company worked in a field that was so sensitive that employees needed to audit all vendor supplied code, then asking them to write a script that you would then audit and execute is a good idea.
May 4, 2016 at 9:48 pm
Andrew P (5/4/2016)
...Unless you have reason not to trust the specific vendor, and even then I'd probably ask for the backup to review and restore myself.
Well...the grapevine has a rumour that their support is a bit lacking, though I don't see that as a reason in and of itself.
Andrew P (5/4/2016)
You expected them to create a new (empty) database, and then create scripts ... and insert data .... That seems quite a time consuming and unusual approach t.... Remember, the database they're trying to get you to restore isn't a blank slate...
They already have the scripts, etc, for use with other clients that they can't restore for, so no extra work there in that sense. However the purpose behind my question is to gauge if I'm being unreasonable in my concerns or if there are "issues" that might haunt me if we restore.
In my previous lives as a vendor employee we always took the script approach, knowing that our dev/test databases had all manner of garbage from internal use, and our other customers' databases were no-go's. So, do they maintain a "for deployment" database for new customers? Or do they source control scripts?
Thanks for your feedback, it's got me thinking. I might just ask them outright about the history of the database.
May 5, 2016 at 12:10 am
FYI for anyone needs an answer like I did: the vendor maintains a suite of databases specifically for deployment, built from scratch.
So I'll be fine to go with the restore approach.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply