Idle Banter For non SV and non bike related chat (and the odd bit of humour - but if any post isn't suitable it'll get deleted real quick). There's also a "U" rating so please respect this. Newbies can also say "hello" here too. |
|
Thread Tools |
04-09-16, 09:08 AM | #11 |
Guest
Posts: n/a
|
Re: OMO: MS SQL Server
Either they haven't set it up right, i.e. Next, Next, Next, Finish, and they are just using a server admin account for everything, or they don't understand it enough themselves to give you access, without knowing what security impact that has on other customers, so they are scared to give you access, or it could just be a case of computer says no and they are being awkward.
If you are going to multi-tenant a SQL box then you should set up separate instances, unless its multi-tenant at the app level (i.e. a SaaS service) and the customer should never need access to the underlying DB. Ask them the direct question.... Are we on our own our own SQL instance? If they say no start asking more difficult questions like "How do you secure and separate our data from other tenants?" Are they ISO27001 accredited? If so they should have implemented RBAC and they shouldn't be using a generic admin account, otherwise they aren't compliant. Last edited by Fordward; 04-09-16 at 09:10 AM. |
04-09-16, 08:55 PM | #12 | |
Member
Join Date: Feb 2015
Location: Woking
Posts: 81
|
Re: OMO: MS SQL Server
Quote:
As someone else said, if the whole system (database and underlaying operating system were configured correctly with reasonable planning for who has access to what then it's all easy. If the systems set up sloppily then and perhaps the people with root access aren't the sharpest then administration can sink down the lowest, cheapest common denominator. If it's an issue why not just go elsewhere? Cloud database providers are ten a penny... |
|
05-09-16, 06:47 AM | #13 |
Member
Mega Poster
Join Date: Mar 2004
Location: Not in Yorkshire. (Thank God)
Posts: 4,116
|
Re: OMO: MS SQL Server
This is enterprise stuff with politics and contracts in the millions.
I was brought in to try and sort out the why/wherefores and was able to engage with the CTO of the outsource provider. The upshot is the DBA who says no does not have the authority to say yes. He works to contact to protect SLA. The CTO sees the bigger picture, he knows we were recently taken over by a massive organisation who are looking to insource strategic solutions and the contract is currently being renegotiated. We now have a set of proposal on how they are going to meet the requirement. So nothing to see here anymore. thanks for the advise on SQL Server
__________________
Not Grumpy, opinionated. |
05-09-16, 08:48 AM | #14 |
Member
Join Date: May 2015
Location: Fife
Posts: 112
|
Re: OMO: MS SQL Server
executives telling DBA's what security access to allow to a third party on a multi tenant SQL server sounds like a fun day at the office...
|
05-09-16, 09:44 PM | #15 |
Guest
Posts: n/a
|
Re: OMO: MS SQL Server
Small beer then. The likes of the NHS spend that on one app. Recently saw them contract 43 million on an electronic healthcare record system for three trusts.
Last edited by Fordward; 05-09-16 at 09:47 PM. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
FS: HP Server | TSM | Idle Banter | 0 | 03-03-10 03:47 PM |
SQL server | Gnan | Idle Banter | 2 | 31-05-06 05:40 AM |
SQL server and VB | mysteryjimbo | Idle Banter | 10 | 18-03-06 09:02 AM |