sa user in sqlserver 2008 r2 problem.

Question

1.00/5 (1 vote)

See more:

i am created dll file for connection to db and it fine working. And i have install new server , at this server i'm installing this software. but on new server problem in connection on sa user. so please tell me how to define sa user on db.

Posted 16-Sep-13 22:18pm

Abhilask kumar

Add a Solution

Comments

Maciej Los 17-Sep-13 4:21am

What kind of connection-string do you use?

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2013-09-16T22:24:00

You should not be connecting as the sa user through your software at all - it is a super user ID which is set up by default, and is extremely dangerous - it should be removed from the SQL instance, or at least have the name and password changed to prevent unauthorised people accessing the system - and it sounds like it has in this case.

You should create users with permission to access the specific database(s) they need, and limit their permissions to the minimum needed to do their job - it is dangerous to give "generic full permissions" to a user id that should only add, select and update records as that gives unauthorised people another route to copy or damage your DB.

Probably, you need to talk to whoever set up the SQL instance, and find out what user ids you should be using instead of sa.