In our Oracle DB's we have a role that we assign to users to set up password
limitations, see below
Expire in 90 days
Lock 5 days after expiration
Keep 5 passwords (not to reuse)
Keep passwords for unlimited time
Enforce Password compliance, i.e. at least 1 Caps, 1 number, 1 special
character and at least 8 characters long Lock after 5 failed login attempts
Lock for 30 days
can this be replicated in MS SQL Svr?
Thanks for any help,
MPMThis is why your applications should support Windows logins (i.e., give a Windows user or group
permission to login to SQL Server). In such Case, Windows handles this for you.
There is currently no support for password aging or policies for SQL server logins. There will be in
next version, though.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"MANCPOLYMAN" <MANCPOLYMAN@.discussions.microsoft.com> wrote in message
news:B86CA4E2-733F-4F9B-907B-BF02C678EFC3@.microsoft.com...
> In our Oracle DB's we have a role that we assign to users to set up password
> limitations, see below
> Expire in 90 days
> Lock 5 days after expiration
> Keep 5 passwords (not to reuse)
> Keep passwords for unlimited time
> Enforce Password compliance, i.e. at least 1 Caps, 1 number, 1 special
> character and at least 8 characters long Lock after 5 failed login attempts
> Lock for 30 days
> can this be replicated in MS SQL Svr?
> Thanks for any help,
> MPM|||Hello Tibor,
In regards to MPM's question. If I use the windows log ins but want to
limit the users access via stored procdures is there a simple method of
accomplishing this? Currently my applcation uses several hunderd stored
procedures. Manaully setting them all is almost impossible which leave
creating a program to do it but every time a change is made to the
application all the user permissions have to be updated.
Also I am assuming SQL 2005 which should be release in Nov will have the
aging MPM talked about, will they also have a better way of setting security
for accessing selected data?
Regards,
John
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Ouu1xoujFHA.476@.TK2MSFTNGP14.phx.gbl...
> This is why your applications should support Windows logins (i.e., give a
> Windows user or group permission to login to SQL Server). In such Case,
> Windows handles this for you.
> There is currently no support for password aging or policies for SQL
> server logins. There will be in next version, though.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "MANCPOLYMAN" <MANCPOLYMAN@.discussions.microsoft.com> wrote in message
> news:B86CA4E2-733F-4F9B-907B-BF02C678EFC3@.microsoft.com...
>> In our Oracle DB's we have a role that we assign to users to set up
>> password
>> limitations, see below
>> Expire in 90 days
>> Lock 5 days after expiration
>> Keep 5 passwords (not to reuse)
>> Keep passwords for unlimited time
>> Enforce Password compliance, i.e. at least 1 Caps, 1 number, 1 special
>> character and at least 8 characters long Lock after 5 failed login
>> attempts
>> Lock for 30 days
>> can this be replicated in MS SQL Svr?
>> Thanks for any help,
>> MPM
>
Showing posts with label assign. Show all posts
Showing posts with label assign. Show all posts
Friday, March 9, 2012
Password Role
In our Oracle DB's we have a role that we assign to users to set up password
limitations, see below
Expire in 90 days
Lock 5 days after expiration
Keep 5 passwords (not to reuse)
Keep passwords for unlimited time
Enforce Password compliance, i.e. at least 1 Caps, 1 number, 1 special
character and at least 8 characters long Lock after 5 failed login attempts
Lock for 30 days
can this be replicated in MS SQL Svr?
Thanks for any help,
MPM
This is why your applications should support Windows logins (i.e., give a Windows user or group
permission to login to SQL Server). In such Case, Windows handles this for you.
There is currently no support for password aging or policies for SQL server logins. There will be in
next version, though.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"MANCPOLYMAN" <MANCPOLYMAN@.discussions.microsoft.com> wrote in message
news:B86CA4E2-733F-4F9B-907B-BF02C678EFC3@.microsoft.com...
> In our Oracle DB's we have a role that we assign to users to set up password
> limitations, see below
> Expire in 90 days
> Lock 5 days after expiration
> Keep 5 passwords (not to reuse)
> Keep passwords for unlimited time
> Enforce Password compliance, i.e. at least 1 Caps, 1 number, 1 special
> character and at least 8 characters long Lock after 5 failed login attempts
> Lock for 30 days
> can this be replicated in MS SQL Svr?
> Thanks for any help,
> MPM
|||Hello Tibor,
In regards to MPM's question. If I use the windows log ins but want to
limit the users access via stored procdures is there a simple method of
accomplishing this? Currently my applcation uses several hunderd stored
procedures. Manaully setting them all is almost impossible which leave
creating a program to do it but every time a change is made to the
application all the user permissions have to be updated.
Also I am assuming SQL 2005 which should be release in Nov will have the
aging MPM talked about, will they also have a better way of setting security
for accessing selected data?
Regards,
John
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Ouu1xoujFHA.476@.TK2MSFTNGP14.phx.gbl...
> This is why your applications should support Windows logins (i.e., give a
> Windows user or group permission to login to SQL Server). In such Case,
> Windows handles this for you.
> There is currently no support for password aging or policies for SQL
> server logins. There will be in next version, though.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "MANCPOLYMAN" <MANCPOLYMAN@.discussions.microsoft.com> wrote in message
> news:B86CA4E2-733F-4F9B-907B-BF02C678EFC3@.microsoft.com...
>
limitations, see below
Expire in 90 days
Lock 5 days after expiration
Keep 5 passwords (not to reuse)
Keep passwords for unlimited time
Enforce Password compliance, i.e. at least 1 Caps, 1 number, 1 special
character and at least 8 characters long Lock after 5 failed login attempts
Lock for 30 days
can this be replicated in MS SQL Svr?
Thanks for any help,
MPM
This is why your applications should support Windows logins (i.e., give a Windows user or group
permission to login to SQL Server). In such Case, Windows handles this for you.
There is currently no support for password aging or policies for SQL server logins. There will be in
next version, though.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"MANCPOLYMAN" <MANCPOLYMAN@.discussions.microsoft.com> wrote in message
news:B86CA4E2-733F-4F9B-907B-BF02C678EFC3@.microsoft.com...
> In our Oracle DB's we have a role that we assign to users to set up password
> limitations, see below
> Expire in 90 days
> Lock 5 days after expiration
> Keep 5 passwords (not to reuse)
> Keep passwords for unlimited time
> Enforce Password compliance, i.e. at least 1 Caps, 1 number, 1 special
> character and at least 8 characters long Lock after 5 failed login attempts
> Lock for 30 days
> can this be replicated in MS SQL Svr?
> Thanks for any help,
> MPM
|||Hello Tibor,
In regards to MPM's question. If I use the windows log ins but want to
limit the users access via stored procdures is there a simple method of
accomplishing this? Currently my applcation uses several hunderd stored
procedures. Manaully setting them all is almost impossible which leave
creating a program to do it but every time a change is made to the
application all the user permissions have to be updated.
Also I am assuming SQL 2005 which should be release in Nov will have the
aging MPM talked about, will they also have a better way of setting security
for accessing selected data?
Regards,
John
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Ouu1xoujFHA.476@.TK2MSFTNGP14.phx.gbl...
> This is why your applications should support Windows logins (i.e., give a
> Windows user or group permission to login to SQL Server). In such Case,
> Windows handles this for you.
> There is currently no support for password aging or policies for SQL
> server logins. There will be in next version, though.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "MANCPOLYMAN" <MANCPOLYMAN@.discussions.microsoft.com> wrote in message
> news:B86CA4E2-733F-4F9B-907B-BF02C678EFC3@.microsoft.com...
>
Password Role
In our Oracle DB's we have a role that we assign to users to set up password
limitations, see below
Expire in 90 days
Lock 5 days after expiration
Keep 5 passwords (not to reuse)
Keep passwords for unlimited time
Enforce Password compliance, i.e. at least 1 Caps, 1 number, 1 special
character and at least 8 characters long Lock after 5 failed login attempts
Lock for 30 days
can this be replicated in MS SQL Svr?
Thanks for any help,
MPMThis is why your applications should support Windows logins (i.e., give a Wi
ndows user or group
permission to login to SQL Server). In such Case, Windows handles this for y
ou.
There is currently no support for password aging or policies for SQL server
logins. There will be in
next version, though.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"MANCPOLYMAN" <MANCPOLYMAN@.discussions.microsoft.com> wrote in message
news:B86CA4E2-733F-4F9B-907B-BF02C678EFC3@.microsoft.com...
> In our Oracle DB's we have a role that we assign to users to set up passwo
rd
> limitations, see below
> Expire in 90 days
> Lock 5 days after expiration
> Keep 5 passwords (not to reuse)
> Keep passwords for unlimited time
> Enforce Password compliance, i.e. at least 1 Caps, 1 number, 1 special
> character and at least 8 characters long Lock after 5 failed login attempt
s
> Lock for 30 days
> can this be replicated in MS SQL Svr?
> Thanks for any help,
> MPM|||Hello Tibor,
In regards to MPM's question. If I use the windows log ins but want to
limit the users access via stored procdures is there a simple method of
accomplishing this? Currently my applcation uses several hunderd stored
procedures. Manaully setting them all is almost impossible which leave
creating a program to do it but every time a change is made to the
application all the user permissions have to be updated.
Also I am assuming SQL 2005 which should be release in Nov will have the
aging MPM talked about, will they also have a better way of setting security
for accessing selected data?
Regards,
John
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Ouu1xoujFHA.476@.TK2MSFTNGP14.phx.gbl...
> This is why your applications should support Windows logins (i.e., give a
> Windows user or group permission to login to SQL Server). In such Case,
> Windows handles this for you.
> There is currently no support for password aging or policies for SQL
> server logins. There will be in next version, though.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "MANCPOLYMAN" <MANCPOLYMAN@.discussions.microsoft.com> wrote in message
> news:B86CA4E2-733F-4F9B-907B-BF02C678EFC3@.microsoft.com...
>
limitations, see below
Expire in 90 days
Lock 5 days after expiration
Keep 5 passwords (not to reuse)
Keep passwords for unlimited time
Enforce Password compliance, i.e. at least 1 Caps, 1 number, 1 special
character and at least 8 characters long Lock after 5 failed login attempts
Lock for 30 days
can this be replicated in MS SQL Svr?
Thanks for any help,
MPMThis is why your applications should support Windows logins (i.e., give a Wi
ndows user or group
permission to login to SQL Server). In such Case, Windows handles this for y
ou.
There is currently no support for password aging or policies for SQL server
logins. There will be in
next version, though.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"MANCPOLYMAN" <MANCPOLYMAN@.discussions.microsoft.com> wrote in message
news:B86CA4E2-733F-4F9B-907B-BF02C678EFC3@.microsoft.com...
> In our Oracle DB's we have a role that we assign to users to set up passwo
rd
> limitations, see below
> Expire in 90 days
> Lock 5 days after expiration
> Keep 5 passwords (not to reuse)
> Keep passwords for unlimited time
> Enforce Password compliance, i.e. at least 1 Caps, 1 number, 1 special
> character and at least 8 characters long Lock after 5 failed login attempt
s
> Lock for 30 days
> can this be replicated in MS SQL Svr?
> Thanks for any help,
> MPM|||Hello Tibor,
In regards to MPM's question. If I use the windows log ins but want to
limit the users access via stored procdures is there a simple method of
accomplishing this? Currently my applcation uses several hunderd stored
procedures. Manaully setting them all is almost impossible which leave
creating a program to do it but every time a change is made to the
application all the user permissions have to be updated.
Also I am assuming SQL 2005 which should be release in Nov will have the
aging MPM talked about, will they also have a better way of setting security
for accessing selected data?
Regards,
John
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Ouu1xoujFHA.476@.TK2MSFTNGP14.phx.gbl...
> This is why your applications should support Windows logins (i.e., give a
> Windows user or group permission to login to SQL Server). In such Case,
> Windows handles this for you.
> There is currently no support for password aging or policies for SQL
> server logins. There will be in next version, though.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "MANCPOLYMAN" <MANCPOLYMAN@.discussions.microsoft.com> wrote in message
> news:B86CA4E2-733F-4F9B-907B-BF02C678EFC3@.microsoft.com...
>
Saturday, February 25, 2012
Password assign on linked server.
Hello,
Is it possible to know a password that was assign in the creation of a
linked server?
I have tha hash of the user password in Oracle and if i change user password
its possible to do the rollback. But in SQL Server if i need to rollback the
operation i dont know what was the old password.
Thanks and best regards.
Is it not possible for you to change the password of the account that
the Linked Server is using to connect with? You don't need to know the
previous password to change it. Obviously this may not be feasible in
your environment but I don't know of how you can retrieve the password
directly.
ALI
|||Hi Ali,
I need to know the password before change it because it might be possible
that i need to rollback this operation. So to change the password i need to
know what is the older password.
Thanks and best regards.
"zashah@.gmail.com" wrote:
> Is it not possible for you to change the password of the account that
> the Linked Server is using to connect with? You don't need to know the
> previous password to change it. Obviously this may not be feasible in
> your environment but I don't know of how you can retrieve the password
> directly.
> ALI
>
Is it possible to know a password that was assign in the creation of a
linked server?
I have tha hash of the user password in Oracle and if i change user password
its possible to do the rollback. But in SQL Server if i need to rollback the
operation i dont know what was the old password.
Thanks and best regards.
Is it not possible for you to change the password of the account that
the Linked Server is using to connect with? You don't need to know the
previous password to change it. Obviously this may not be feasible in
your environment but I don't know of how you can retrieve the password
directly.
ALI
|||Hi Ali,
I need to know the password before change it because it might be possible
that i need to rollback this operation. So to change the password i need to
know what is the older password.
Thanks and best regards.
"zashah@.gmail.com" wrote:
> Is it not possible for you to change the password of the account that
> the Linked Server is using to connect with? You don't need to know the
> previous password to change it. Obviously this may not be feasible in
> your environment but I don't know of how you can retrieve the password
> directly.
> ALI
>
Password assign on linked server.
Hello,
Is it possible to know a password that was assign in the creation of a
linked server?
I have tha hash of the user password in Oracle and if i change user password
its possible to do the rollback. But in SQL Server if i need to rollback the
operation i dont know what was the old password.
Thanks and best regards.Is it not possible for you to change the password of the account that
the Linked Server is using to connect with? You don't need to know the
previous password to change it. Obviously this may not be feasible in
your environment but I don't know of how you can retrieve the password
directly.
ALI|||Hi Ali,
I need to know the password before change it because it might be possible
that i need to rollback this operation. So to change the password i need to
know what is the older password.
Thanks and best regards.
"zashah@.gmail.com" wrote:
> Is it not possible for you to change the password of the account that
> the Linked Server is using to connect with? You don't need to know the
> previous password to change it. Obviously this may not be feasible in
> your environment but I don't know of how you can retrieve the password
> directly.
> ALI
>
Is it possible to know a password that was assign in the creation of a
linked server?
I have tha hash of the user password in Oracle and if i change user password
its possible to do the rollback. But in SQL Server if i need to rollback the
operation i dont know what was the old password.
Thanks and best regards.Is it not possible for you to change the password of the account that
the Linked Server is using to connect with? You don't need to know the
previous password to change it. Obviously this may not be feasible in
your environment but I don't know of how you can retrieve the password
directly.
ALI|||Hi Ali,
I need to know the password before change it because it might be possible
that i need to rollback this operation. So to change the password i need to
know what is the older password.
Thanks and best regards.
"zashah@.gmail.com" wrote:
> Is it not possible for you to change the password of the account that
> the Linked Server is using to connect with? You don't need to know the
> previous password to change it. Obviously this may not be feasible in
> your environment but I don't know of how you can retrieve the password
> directly.
> ALI
>
Password assign on linked server.
Hello,
Is it possible to know a password that was assign in the creation of a
linked server?
I have tha hash of the user password in Oracle and if i change user password
its possible to do the rollback. But in SQL Server if i need to rollback the
operation i dont know what was the old password.
Thanks and best regards.Is it not possible for you to change the password of the account that
the Linked Server is using to connect with? You don't need to know the
previous password to change it. Obviously this may not be feasible in
your environment but I don't know of how you can retrieve the password
directly.
ALI|||Hi Ali,
I need to know the password before change it because it might be possible
that i need to rollback this operation. So to change the password i need to
know what is the older password.
Thanks and best regards.
"zashah@.gmail.com" wrote:
> Is it not possible for you to change the password of the account that
> the Linked Server is using to connect with? You don't need to know the
> previous password to change it. Obviously this may not be feasible in
> your environment but I don't know of how you can retrieve the password
> directly.
> ALI
>
Is it possible to know a password that was assign in the creation of a
linked server?
I have tha hash of the user password in Oracle and if i change user password
its possible to do the rollback. But in SQL Server if i need to rollback the
operation i dont know what was the old password.
Thanks and best regards.Is it not possible for you to change the password of the account that
the Linked Server is using to connect with? You don't need to know the
previous password to change it. Obviously this may not be feasible in
your environment but I don't know of how you can retrieve the password
directly.
ALI|||Hi Ali,
I need to know the password before change it because it might be possible
that i need to rollback this operation. So to change the password i need to
know what is the older password.
Thanks and best regards.
"zashah@.gmail.com" wrote:
> Is it not possible for you to change the password of the account that
> the Linked Server is using to connect with? You don't need to know the
> previous password to change it. Obviously this may not be feasible in
> your environment but I don't know of how you can retrieve the password
> directly.
> ALI
>
Subscribe to:
Posts (Atom)