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


Deny SSMS Update


Deny SSMS Update

Author
Message
Dana
Dana
SSCertifiable
SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)

Group: General Forum Members
Points: 5970 Visits: 3453
Hello,
Our setup uses Windows integrated security.

I would like someone to be able to update using the front end (.NET), but not if they use SSMS.

Is this possible without using "Execute As" for the front end? "Execute As" would be a massive undertaking.

Thank you,
djj55
Erland Sommarskog
Erland Sommarskog
SSCertifiable
SSCertifiable (5.4K reputation)SSCertifiable (5.4K reputation)SSCertifiable (5.4K reputation)SSCertifiable (5.4K reputation)SSCertifiable (5.4K reputation)SSCertifiable (5.4K reputation)SSCertifiable (5.4K reputation)SSCertifiable (5.4K reputation)

Group: General Forum Members
Points: 5356 Visits: 875
What is the architecture of the application? Web app? Three-tier with a separate application server? Or does the user run the application from his desktop and the application connects directly to SQL Server?

In the latter case, there is only one option: Terminal Server/Citrix + network segmenting.

If you have a two-tier app, and use EXECUTE AS or an application role, you cannot achieve security, because anythijg the app can do, the user can do from SSMS. So the only option is to keep the user out from SQL Server.

If you have three tiers there a few more options.

Erland Sommarskog, SQL Server MVP, www.sommarskog.se
Dana
Dana
SSCertifiable
SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)

Group: General Forum Members
Points: 5970 Visits: 3453
Erland Sommarskog (3/6/2014)
What is the architecture of the application? Web app? Three-tier with a separate application server? Or does the user run the application from his desktop and the application connects directly to SQL Server?

In the latter case, there is only one option: Terminal Server/Citrix + network segmenting.

If you have a two-tier app, and use EXECUTE AS or an application role, you cannot achieve security, because anythijg the app can do, the user can do from SSMS. So the only option is to keep the user out from SQL Server.

If you have three tiers there a few more options.

Thank you. That was what I was afraid of as we use the desktop application connecting to SQL.
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