Password at Database level

Question

Post reply

Password at Database level

vish-531091

Right there with Babe

Points: 738
More actions
March 10, 2008 at 12:52 am

#93991

Hi All,
Can i set a password at DataBase level.
ofcourse i am SA user for the SQL server 2000.
Thanks,

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Jeff Moden SSC Guru Points: 1004307 More actions · Answer 1

Yeah... ever hear of the "DataBase Owner" role?

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Big Data Man SSCrazy Eights Points: 8536 More actions · Answer 2

Vish,

Just out of curiosity, what are you trying to achieve in terms of security?

Thanks,

Phillip Cox

MCITP - DBAdmin

SQL ORACLE One Orange Chip Points: 27807 More actions · Answer 3

You may try to create a role in a database level, and include it as an application role. You need provide password for this role.

vish-531091 Right there with Babe Points: 738 More actions · Answer 4

Hi Phillip,

Here we share same SA username and password and we donot have different usernames created for the SQL server.

Apparently, Every body who logins in uses the SAME username and password.

In such situations its hard to avoid the CATASTROPHE of somebody deleting the DB or a TABLE.

So thought if i can provide a password at Database level that would be prompted if some one tries to delete a DB or TABLE:)

I know it sounds very unorthodox but this is how things work for me here.:w00t:

EdVassie SSC Guru Points: 60472 More actions · Answer 5

If lots of people are logging on using the SA account, in SQL Server 2000 and below you can not stop them dropping databases.

You need to move to a new process where each person has their own login. The easiest way to do this is to use Windows logins and Windows groups.

Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

rlondon SSCarpal Tunnel Points: 4653 More actions · Answer 6

I agree with EdVasse. We have the same situation here where everyone logs in with the SA id and password. I am now in the process of putting together a plan to set up windows logins and groups and having everyone move off of logging in with the SA id. Once we have tested and made sure that everyone has the correct permissions, the SA password will be changed so they can no longer log in with it. I'm sure it will cause some issues for a while, but better safe than sorry.