Home/ Questions/Q 7975027
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-04T08:32:11+00:00

I have a rich client program installed on users PCs where I want to

  • 0

I have a rich client program installed on users PCs where I want to start storing some user created data on SQL Azure/SQL Server. The potential anonymous-to-me users would key in their name, email account and a password which would get stored on SQL Azure/SQL Server. Then they would start generating their own data. I’m anticipating volumes of maybe 1000 users.

There are times when those users would like to run their own queries against their own data but, obviously, I must ensure that they can never view other users data.

I’m thinking the best way to ensure security of data is for each user to be issued their own SQL Azure account and password. I will setup a SQL Azure user and long password, known only to me, which only has permissions to execute several stored procedures with appropriate parameters being passed to those SPs which will create the SQL Server accounts, logins and add the users to a role which I have created.

Obviously someone running debugging tools could figure out the user name and password but I’m thinking this isn’t a big deal. If all that particular SQL Azure account can do is execute a few SPs so what if a malicious individual starts doing that. I will only allow a very limited amount of data to be uploaded before I require payment.

The users can only insert records using stored procedures which use the following:

SELECT @uName=SYSTEM_USER

and only select appropriate parent records. All stored procedures which users can execute would have the above as required to ensure they can only work with their own records.

All views will have embedded with them WHERE clauses such as 

WHERE tbLoginName = SYSTEM_USER.

I’m new to SQL Server so I may be missing some fundamental concepts so I’d appreciate any and all comments.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The issue is, as pointed out on http://msdn.microsoft.com/en-us/library/ms189751.aspx:

    In SQL Azure, only the server-level principal login (created by the provisioning process) or members of the loginmanager database role in the master database can create new logins.

    Those accounts are also capable of alter and drop logins. So if you embed those accounts in the client application, you’re essentially granting every user permission to alter/drop other users accounts. While an average user won’t do that, a hacker will. So you cannot let a client application manage SQL Azure logins, unless only trusted users (such as your IT administrator) are permitted to use the app.

    Best Regards,

    Ming Xu.

    • 0