Hi NG,
i received the following mail today:
<snipp>
May be the reason is that I didn't read
this file with the Acroreader version 7.0 which is the latest available
for Windows. Please take into account that not everybody lives in a
Microsoft world: The latest available Acroreader under Linux is version
5! So I kindly request a readable version of my personal pdf-statement
P.S.: A closer analysis of the pdf file shows this error message:
**** This file has a corrupted %%EOF marker, or garbage after the %%EOF.
**** The file was produced by Microsoft Rptg Srvcs PDF Rendering
Extension 8. 0:
**** please notify the author of this software
**** that the file does not conform to Adobe's published PDF
</snipp>
My question:
Does the hotfix from
http://support.microsoft.com/kb/885444/en-us
fix my problems?
I got the beta SP2 already here, but the production environment is german so
i couldn't install the sp2 there.
Brian?
regards
FrankDear "Frank",
are you running SP1 now?
dlr
"Frank Matthiesen" <fm@.xax.de> wrote in message
news:3bcph6F6ggsklU1@.individual.net...
> Hi NG,
> i received the following mail today:
> <snipp>
> May be the reason is that I didn't read
> this file with the Acroreader version 7.0 which is the latest available
> for Windows. Please take into account that not everybody lives in a
> Microsoft world: The latest available Acroreader under Linux is version
> 5! So I kindly request a readable version of my personal pdf-statement
> P.S.: A closer analysis of the pdf file shows this error message:
> **** This file has a corrupted %%EOF marker, or garbage after the
%%EOF.
> **** The file was produced by Microsoft Rptg Srvcs PDF Rendering
> Extension 8. 0:
> **** please notify the author of this software
> **** that the file does not conform to Adobe's published PDF
> </snipp>
>
> My question:
> Does the hotfix from
> http://support.microsoft.com/kb/885444/en-us
> fix my problems?
> I got the beta SP2 already here, but the production environment is german
so
> i couldn't install the sp2 there.
> Brian?
> regards
> Frank
>
>|||Dennis Redfield wrote:
> are you running SP1 now?
Yes i do.
Franksql
Showing posts with label users. Show all posts
Showing posts with label users. Show all posts
Friday, March 30, 2012
Wednesday, March 28, 2012
pdf instead of html as default output format
Hi all,
I would like to output all reports in pdf format instead of html.
I dont want to allow users to choose an export format.
So, if they access an URL and fill some textboxes with appropriated
parameters I can send them a ready-to-print PDF file in Internet Explorer.
Is it possible?
(I´m assuming all clients uses IE browser and Acrobat Reader plugin).
thanks a lot!One way you can do it is in the url of the report. You can add at the end of
your report url:
&rs:Command=Render&rs:format=pdf
Since it is in the url you have to be careful how you open it. I just open
the report in a new windows and it will actually render the report in the
adobe acrobat reader progam so there is no url the user can change. You
could embed it in an iframe on a page to display to a user as well.
"Ricardo" wrote:
> Hi all,
> I would like to output all reports in pdf format instead of html.
> I dont want to allow users to choose an export format.
> So, if they access an URL and fill some textboxes with appropriated
> parameters I can send them a ready-to-print PDF file in Internet Explorer.
> Is it possible?
> (I´m assuming all clients uses IE browser and Acrobat Reader plugin).
> thanks a lot!
>
>
I would like to output all reports in pdf format instead of html.
I dont want to allow users to choose an export format.
So, if they access an URL and fill some textboxes with appropriated
parameters I can send them a ready-to-print PDF file in Internet Explorer.
Is it possible?
(I´m assuming all clients uses IE browser and Acrobat Reader plugin).
thanks a lot!One way you can do it is in the url of the report. You can add at the end of
your report url:
&rs:Command=Render&rs:format=pdf
Since it is in the url you have to be careful how you open it. I just open
the report in a new windows and it will actually render the report in the
adobe acrobat reader progam so there is no url the user can change. You
could embed it in an iframe on a page to display to a user as well.
"Ricardo" wrote:
> Hi all,
> I would like to output all reports in pdf format instead of html.
> I dont want to allow users to choose an export format.
> So, if they access an URL and fill some textboxes with appropriated
> parameters I can send them a ready-to-print PDF file in Internet Explorer.
> Is it possible?
> (I´m assuming all clients uses IE browser and Acrobat Reader plugin).
> thanks a lot!
>
>
Friday, March 23, 2012
PDF always prompts
I'm publishing reports in PDF, providing users with URLs like
http://<server>/reportserver?/<reportname>&rs:Format=PDF&rs:Command=Render
In some circumstances, I'd like the PDF to open directly in the browser
without a prompt, but these always ask if I want to Open or Save the file,
directly in Acrobat Reader 8. How can I make this happen?
Static PDF files on my server open directly in the browser as expected.I had some fun trying to track that down too. I eventually found this, which
worked for me. I'm no expert so I'm not sure just what the critical bit is.
I'm using the Render method to get the report as a byte[] from Reporting
Services. Good luck:
private void DoOutput(byte[] result)
{
Response.ContentType = "Application/pdf";
Response.Cache.SetCacheability(HttpCacheability.Public);
Response.BufferOutput = false;
int count = result.Length;
if (count > 0)
{
Response.OutputStream.Write(result, 0, count);
}
Response.End();
}
"Rocks" wrote:
> I'm publishing reports in PDF, providing users with URLs like
> http://<server>/reportserver?/<reportname>&rs:Format=PDF&rs:Command=Render
> In some circumstances, I'd like the PDF to open directly in the browser
> without a prompt, but these always ask if I want to Open or Save the file,
> directly in Acrobat Reader 8. How can I make this happen?
> Static PDF files on my server open directly in the browser as expected.|||So, I have to use ASP.NET? I'm still running classic ASP.
"jgwilliams" wrote:
> I had some fun trying to track that down too. I eventually found this, which
> worked for me. I'm no expert so I'm not sure just what the critical bit is.
> I'm using the Render method to get the report as a byte[] from Reporting
> Services. Good luck:
> private void DoOutput(byte[] result)
> {
> Response.ContentType = "Application/pdf";
> Response.Cache.SetCacheability(HttpCacheability.Public);
> Response.BufferOutput = false;
> int count = result.Length;
> if (count > 0)
> {
> Response.OutputStream.Write(result, 0, count);
> }
> Response.End();
> }
> "Rocks" wrote:
> > I'm publishing reports in PDF, providing users with URLs like
> > http://<server>/reportserver?/<reportname>&rs:Format=PDF&rs:Command=Render
> >
> > In some circumstances, I'd like the PDF to open directly in the browser
> > without a prompt, but these always ask if I want to Open or Save the file,
> > directly in Acrobat Reader 8. How can I make this happen?
> >
> > Static PDF files on my server open directly in the browser as expected.|||Aah, right. Sorry, I can't help you there - I never really used classic ASP
in earnest.
"Rocks" wrote:
> So, I have to use ASP.NET? I'm still running classic ASP.
> "jgwilliams" wrote:
> > I had some fun trying to track that down too. I eventually found this, which
> > worked for me. I'm no expert so I'm not sure just what the critical bit is.
> > I'm using the Render method to get the report as a byte[] from Reporting
> > Services. Good luck:
> >
> > private void DoOutput(byte[] result)
> > {
> > Response.ContentType = "Application/pdf";
> > Response.Cache.SetCacheability(HttpCacheability.Public);
> > Response.BufferOutput = false;
> > int count = result.Length;
> > if (count > 0)
> > {
> > Response.OutputStream.Write(result, 0, count);
> > }
> > Response.End();
> > }
> >
> > "Rocks" wrote:
> >
> > > I'm publishing reports in PDF, providing users with URLs like
> > > http://<server>/reportserver?/<reportname>&rs:Format=PDF&rs:Command=Render
> > >
> > > In some circumstances, I'd like the PDF to open directly in the browser
> > > without a prompt, but these always ask if I want to Open or Save the file,
> > > directly in Acrobat Reader 8. How can I make this happen?
> > >
> > > Static PDF files on my server open directly in the browser as expected.|||I found a solution that works for my situation, and even works in classic
ASP: just setup a server proxy:
Response.ContentType = "application/pdf"
reportSource = "reportserver?reportname&rs:Format=PDF"
set objReport = Server.CreateObject("MSXML2.ServerXMLHTTP")
objReport.open "GET", reportSource, false
objReport.send
Response.BinaryWrite(objReport.ResponseBody)
set objReport = nothing
"jgwilliams" wrote:
> Aah, right. Sorry, I can't help you there - I never really used classic ASP
> in earnest.
> "Rocks" wrote:
> > So, I have to use ASP.NET? I'm still running classic ASP.
> >
> > "jgwilliams" wrote:
> >
> > > I had some fun trying to track that down too. I eventually found this, which
> > > worked for me. I'm no expert so I'm not sure just what the critical bit is.
> > > I'm using the Render method to get the report as a byte[] from Reporting
> > > Services. Good luck:
> > >
> > > private void DoOutput(byte[] result)
> > > {
> > > Response.ContentType = "Application/pdf";
> > > Response.Cache.SetCacheability(HttpCacheability.Public);
> > > Response.BufferOutput = false;
> > > int count = result.Length;
> > > if (count > 0)
> > > {
> > > Response.OutputStream.Write(result, 0, count);
> > > }
> > > Response.End();
> > > }
> > >
> > > "Rocks" wrote:
> > >
> > > > I'm publishing reports in PDF, providing users with URLs like
> > > > http://<server>/reportserver?/<reportname>&rs:Format=PDF&rs:Command=Render
> > > >
> > > > In some circumstances, I'd like the PDF to open directly in the browser
> > > > without a prompt, but these always ask if I want to Open or Save the file,
> > > > directly in Acrobat Reader 8. How can I make this happen?
> > > >
> > > > Static PDF files on my server open directly in the browser as expected.|||I'm facing the same iissue, and would like to know how to use this method
"private void DoOutput(byte[] result)" the param result where i'm going to
fill it ?
thnx a lot
"jgwilliams" wrote:
> I had some fun trying to track that down too. I eventually found this, which
> worked for me. I'm no expert so I'm not sure just what the critical bit is.
> I'm using the Render method to get the report as a byte[] from Reporting
> Services. Good luck:
> private void DoOutput(byte[] result)
> {
> Response.ContentType = "Application/pdf";
> Response.Cache.SetCacheability(HttpCacheability.Public);
> Response.BufferOutput = false;
> int count = result.Length;
> if (count > 0)
> {
> Response.OutputStream.Write(result, 0, count);
> }
> Response.End();
> }
> "Rocks" wrote:
> > I'm publishing reports in PDF, providing users with URLs like
> > http://<server>/reportserver?/<reportname>&rs:Format=PDF&rs:Command=Render
> >
> > In some circumstances, I'd like the PDF to open directly in the browser
> > without a prompt, but these always ask if I want to Open or Save the file,
> > directly in Acrobat Reader 8. How can I make this happen?
> >
> > Static PDF files on my server open directly in the browser as expected.
http://<server>/reportserver?/<reportname>&rs:Format=PDF&rs:Command=Render
In some circumstances, I'd like the PDF to open directly in the browser
without a prompt, but these always ask if I want to Open or Save the file,
directly in Acrobat Reader 8. How can I make this happen?
Static PDF files on my server open directly in the browser as expected.I had some fun trying to track that down too. I eventually found this, which
worked for me. I'm no expert so I'm not sure just what the critical bit is.
I'm using the Render method to get the report as a byte[] from Reporting
Services. Good luck:
private void DoOutput(byte[] result)
{
Response.ContentType = "Application/pdf";
Response.Cache.SetCacheability(HttpCacheability.Public);
Response.BufferOutput = false;
int count = result.Length;
if (count > 0)
{
Response.OutputStream.Write(result, 0, count);
}
Response.End();
}
"Rocks" wrote:
> I'm publishing reports in PDF, providing users with URLs like
> http://<server>/reportserver?/<reportname>&rs:Format=PDF&rs:Command=Render
> In some circumstances, I'd like the PDF to open directly in the browser
> without a prompt, but these always ask if I want to Open or Save the file,
> directly in Acrobat Reader 8. How can I make this happen?
> Static PDF files on my server open directly in the browser as expected.|||So, I have to use ASP.NET? I'm still running classic ASP.
"jgwilliams" wrote:
> I had some fun trying to track that down too. I eventually found this, which
> worked for me. I'm no expert so I'm not sure just what the critical bit is.
> I'm using the Render method to get the report as a byte[] from Reporting
> Services. Good luck:
> private void DoOutput(byte[] result)
> {
> Response.ContentType = "Application/pdf";
> Response.Cache.SetCacheability(HttpCacheability.Public);
> Response.BufferOutput = false;
> int count = result.Length;
> if (count > 0)
> {
> Response.OutputStream.Write(result, 0, count);
> }
> Response.End();
> }
> "Rocks" wrote:
> > I'm publishing reports in PDF, providing users with URLs like
> > http://<server>/reportserver?/<reportname>&rs:Format=PDF&rs:Command=Render
> >
> > In some circumstances, I'd like the PDF to open directly in the browser
> > without a prompt, but these always ask if I want to Open or Save the file,
> > directly in Acrobat Reader 8. How can I make this happen?
> >
> > Static PDF files on my server open directly in the browser as expected.|||Aah, right. Sorry, I can't help you there - I never really used classic ASP
in earnest.
"Rocks" wrote:
> So, I have to use ASP.NET? I'm still running classic ASP.
> "jgwilliams" wrote:
> > I had some fun trying to track that down too. I eventually found this, which
> > worked for me. I'm no expert so I'm not sure just what the critical bit is.
> > I'm using the Render method to get the report as a byte[] from Reporting
> > Services. Good luck:
> >
> > private void DoOutput(byte[] result)
> > {
> > Response.ContentType = "Application/pdf";
> > Response.Cache.SetCacheability(HttpCacheability.Public);
> > Response.BufferOutput = false;
> > int count = result.Length;
> > if (count > 0)
> > {
> > Response.OutputStream.Write(result, 0, count);
> > }
> > Response.End();
> > }
> >
> > "Rocks" wrote:
> >
> > > I'm publishing reports in PDF, providing users with URLs like
> > > http://<server>/reportserver?/<reportname>&rs:Format=PDF&rs:Command=Render
> > >
> > > In some circumstances, I'd like the PDF to open directly in the browser
> > > without a prompt, but these always ask if I want to Open or Save the file,
> > > directly in Acrobat Reader 8. How can I make this happen?
> > >
> > > Static PDF files on my server open directly in the browser as expected.|||I found a solution that works for my situation, and even works in classic
ASP: just setup a server proxy:
Response.ContentType = "application/pdf"
reportSource = "reportserver?reportname&rs:Format=PDF"
set objReport = Server.CreateObject("MSXML2.ServerXMLHTTP")
objReport.open "GET", reportSource, false
objReport.send
Response.BinaryWrite(objReport.ResponseBody)
set objReport = nothing
"jgwilliams" wrote:
> Aah, right. Sorry, I can't help you there - I never really used classic ASP
> in earnest.
> "Rocks" wrote:
> > So, I have to use ASP.NET? I'm still running classic ASP.
> >
> > "jgwilliams" wrote:
> >
> > > I had some fun trying to track that down too. I eventually found this, which
> > > worked for me. I'm no expert so I'm not sure just what the critical bit is.
> > > I'm using the Render method to get the report as a byte[] from Reporting
> > > Services. Good luck:
> > >
> > > private void DoOutput(byte[] result)
> > > {
> > > Response.ContentType = "Application/pdf";
> > > Response.Cache.SetCacheability(HttpCacheability.Public);
> > > Response.BufferOutput = false;
> > > int count = result.Length;
> > > if (count > 0)
> > > {
> > > Response.OutputStream.Write(result, 0, count);
> > > }
> > > Response.End();
> > > }
> > >
> > > "Rocks" wrote:
> > >
> > > > I'm publishing reports in PDF, providing users with URLs like
> > > > http://<server>/reportserver?/<reportname>&rs:Format=PDF&rs:Command=Render
> > > >
> > > > In some circumstances, I'd like the PDF to open directly in the browser
> > > > without a prompt, but these always ask if I want to Open or Save the file,
> > > > directly in Acrobat Reader 8. How can I make this happen?
> > > >
> > > > Static PDF files on my server open directly in the browser as expected.|||I'm facing the same iissue, and would like to know how to use this method
"private void DoOutput(byte[] result)" the param result where i'm going to
fill it ?
thnx a lot
"jgwilliams" wrote:
> I had some fun trying to track that down too. I eventually found this, which
> worked for me. I'm no expert so I'm not sure just what the critical bit is.
> I'm using the Render method to get the report as a byte[] from Reporting
> Services. Good luck:
> private void DoOutput(byte[] result)
> {
> Response.ContentType = "Application/pdf";
> Response.Cache.SetCacheability(HttpCacheability.Public);
> Response.BufferOutput = false;
> int count = result.Length;
> if (count > 0)
> {
> Response.OutputStream.Write(result, 0, count);
> }
> Response.End();
> }
> "Rocks" wrote:
> > I'm publishing reports in PDF, providing users with URLs like
> > http://<server>/reportserver?/<reportname>&rs:Format=PDF&rs:Command=Render
> >
> > In some circumstances, I'd like the PDF to open directly in the browser
> > without a prompt, but these always ask if I want to Open or Save the file,
> > directly in Acrobat Reader 8. How can I make this happen?
> >
> > Static PDF files on my server open directly in the browser as expected.
Wednesday, March 21, 2012
Pausing SQL Server from transact SQL
We have a database that automatically restores at night from another server.
We use a kill all users job and place the database in single user mode.
Unfortunately there is an app on the network that will automatically
reconnect if it's spid is killed.
I'd like to be able to Pause the server from within transact SQL.
The only way I can see to do this is:
exec master..xp_cmdshell "net pause mssqlserver", No_OUTPUT
Kill the spids >= 50
exec sp_dboption 'Database Name', 'dbo use only', true
exec master..xp_cmdshell "net continue mssqlserver", No_OUTPUT
Is there a way of pausing without using xp_cmdshell?
PaulThis might work...
ALTER DATABASE yourdb SET SINGLE_USER WITH ROLLBACK IMMEDIATE
GO
USE yourdb
GO
RESTORE ...
That way you should be the single_user before the application can reconnect.
--
HTH
Ryan Waight, MCDBA, MCSE
"Paul Cahill" <NOTpaul.cahillNOT@.blueyonder.co.uk> wrote in message
news:%23QjaYGZjDHA.1456@.tk2msftngp13.phx.gbl...
> We have a database that automatically restores at night from another
server.
> We use a kill all users job and place the database in single user mode.
> Unfortunately there is an app on the network that will automatically
> reconnect if it's spid is killed.
> I'd like to be able to Pause the server from within transact SQL.
> The only way I can see to do this is:
> exec master..xp_cmdshell "net pause mssqlserver", No_OUTPUT
> Kill the spids >= 50
> exec sp_dboption 'Database Name', 'dbo use only', true
> exec master..xp_cmdshell "net continue mssqlserver", No_OUTPUT
> Is there a way of pausing without using xp_cmdshell?
> Paul
>|||Or set the db in restricted user mode, assuming that that nasty app doesn't
use a login that is a member of the db_owner, db_creator or sysadmin roles.
ALTER DATABASE yourdb SET RESTRICTED_USER WITH ROLLBACK IMMEDIATE
Ryan, your code will not work. _no one_ can be in the database when you want
to restore it, not even the connection that is doing the restore, that
should be connected to a different database. You can do ALTER DATABASE...
and then RESTORE when you are connected to the master database and hope the
application won't be able to log back in between the statements, but that
won't always work.
--
Jacco Schalkwijk
SQL Server MVP
"Ryan Waight" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:eZhceRZjDHA.1004@.tk2msftngp13.phx.gbl...
> This might work...
> ALTER DATABASE yourdb SET SINGLE_USER WITH ROLLBACK IMMEDIATE
> GO
> USE yourdb
> GO
> RESTORE ...
> That way you should be the single_user before the application can
reconnect.
> --
> HTH
> Ryan Waight, MCDBA, MCSE
> "Paul Cahill" <NOTpaul.cahillNOT@.blueyonder.co.uk> wrote in message
> news:%23QjaYGZjDHA.1456@.tk2msftngp13.phx.gbl...
> > We have a database that automatically restores at night from another
> server.
> > We use a kill all users job and place the database in single user mode.
> > Unfortunately there is an app on the network that will automatically
> > reconnect if it's spid is killed.
> >
> > I'd like to be able to Pause the server from within transact SQL.
> > The only way I can see to do this is:
> >
> > exec master..xp_cmdshell "net pause mssqlserver", No_OUTPUT
> > Kill the spids >= 50
> > exec sp_dboption 'Database Name', 'dbo use only', true
> > exec master..xp_cmdshell "net continue mssqlserver", No_OUTPUT
> >
> > Is there a way of pausing without using xp_cmdshell?
> >
> > Paul
> >
> >
>|||> ALTER DATABASE yourdb SET SINGLE_USER WITH ROLLBACK IMMEDIATE
> GO
> USE yourdb
> GO
> RESTORE ...
>
Since a database can't be restored while it's in use, the database
context needs to be changed to some other database:
USE master
GO
RESTORE ...
Hope this helps.
Dan Guzman
SQL Server MVP
--
SQL FAQ links (courtesy Neil Pike):
http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
--
"Ryan Waight" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:eZhceRZjDHA.1004@.tk2msftngp13.phx.gbl...
> This might work...
> ALTER DATABASE yourdb SET SINGLE_USER WITH ROLLBACK IMMEDIATE
> GO
> USE yourdb
> GO
> RESTORE ...
> That way you should be the single_user before the application can
reconnect.
> --
> HTH
> Ryan Waight, MCDBA, MCSE
> "Paul Cahill" <NOTpaul.cahillNOT@.blueyonder.co.uk> wrote in message
> news:%23QjaYGZjDHA.1456@.tk2msftngp13.phx.gbl...
> > We have a database that automatically restores at night from another
> server.
> > We use a kill all users job and place the database in single user
mode.
> > Unfortunately there is an app on the network that will automatically
> > reconnect if it's spid is killed.
> >
> > I'd like to be able to Pause the server from within transact SQL.
> > The only way I can see to do this is:
> >
> > exec master..xp_cmdshell "net pause mssqlserver", No_OUTPUT
> > Kill the spids >= 50
> > exec sp_dboption 'Database Name', 'dbo use only', true
> > exec master..xp_cmdshell "net continue mssqlserver", No_OUTPUT
> >
> > Is there a way of pausing without using xp_cmdshell?
> >
> > Paul
> >
> >
>|||Apologies all. USE yourdb will of course use up the SINGLE_USER.
Should have read :-
ALTER DATABASE yourdb SET SINGLE_USER WITH ROLLBACK IMMEDIATE
GO
USE master
GO
RESTORE ...
--
HTH
Ryan Waight, MCDBA, MCSE
"Jacco Schalkwijk" <NOSPAMjaccos@.eurostop.co.uk> wrote in message
news:uamRLnZjDHA.1948@.TK2MSFTNGP12.phx.gbl...
> Or set the db in restricted user mode, assuming that that nasty app
doesn't
> use a login that is a member of the db_owner, db_creator or sysadmin
roles.
> ALTER DATABASE yourdb SET RESTRICTED_USER WITH ROLLBACK IMMEDIATE
> Ryan, your code will not work. _no one_ can be in the database when you
want
> to restore it, not even the connection that is doing the restore, that
> should be connected to a different database. You can do ALTER DATABASE...
> and then RESTORE when you are connected to the master database and hope
the
> application won't be able to log back in between the statements, but that
> won't always work.
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Ryan Waight" <Ryan_Waight@.nospam.hotmail.com> wrote in message
> news:eZhceRZjDHA.1004@.tk2msftngp13.phx.gbl...
> > This might work...
> >
> > ALTER DATABASE yourdb SET SINGLE_USER WITH ROLLBACK IMMEDIATE
> > GO
> > USE yourdb
> > GO
> > RESTORE ...
> >
> > That way you should be the single_user before the application can
> reconnect.
> >
> > --
> > HTH
> > Ryan Waight, MCDBA, MCSE
> >
> > "Paul Cahill" <NOTpaul.cahillNOT@.blueyonder.co.uk> wrote in message
> > news:%23QjaYGZjDHA.1456@.tk2msftngp13.phx.gbl...
> > > We have a database that automatically restores at night from another
> > server.
> > > We use a kill all users job and place the database in single user
mode.
> > > Unfortunately there is an app on the network that will automatically
> > > reconnect if it's spid is killed.
> > >
> > > I'd like to be able to Pause the server from within transact SQL.
> > > The only way I can see to do this is:
> > >
> > > exec master..xp_cmdshell "net pause mssqlserver", No_OUTPUT
> > > Kill the spids >= 50
> > > exec sp_dboption 'Database Name', 'dbo use only', true
> > > exec master..xp_cmdshell "net continue mssqlserver", No_OUTPUT
> > >
> > > Is there a way of pausing without using xp_cmdshell?
> > >
> > > Paul
> > >
> > >
> >
> >
>|||Thanks guys. Too busy looking at set dboption to remember alter database.
Paul
"Jacco Schalkwijk" <NOSPAMjaccos@.eurostop.co.uk> wrote in message
news:uamRLnZjDHA.1948@.TK2MSFTNGP12.phx.gbl...
> Or set the db in restricted user mode, assuming that that nasty app
doesn't
> use a login that is a member of the db_owner, db_creator or sysadmin
roles.
> ALTER DATABASE yourdb SET RESTRICTED_USER WITH ROLLBACK IMMEDIATE
> Ryan, your code will not work. _no one_ can be in the database when you
want
> to restore it, not even the connection that is doing the restore, that
> should be connected to a different database. You can do ALTER DATABASE...
> and then RESTORE when you are connected to the master database and hope
the
> application won't be able to log back in between the statements, but that
> won't always work.
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Ryan Waight" <Ryan_Waight@.nospam.hotmail.com> wrote in message
> news:eZhceRZjDHA.1004@.tk2msftngp13.phx.gbl...
> > This might work...
> >
> > ALTER DATABASE yourdb SET SINGLE_USER WITH ROLLBACK IMMEDIATE
> > GO
> > USE yourdb
> > GO
> > RESTORE ...
> >
> > That way you should be the single_user before the application can
> reconnect.
> >
> > --
> > HTH
> > Ryan Waight, MCDBA, MCSE
> >
> > "Paul Cahill" <NOTpaul.cahillNOT@.blueyonder.co.uk> wrote in message
> > news:%23QjaYGZjDHA.1456@.tk2msftngp13.phx.gbl...
> > > We have a database that automatically restores at night from another
> > server.
> > > We use a kill all users job and place the database in single user
mode.
> > > Unfortunately there is an app on the network that will automatically
> > > reconnect if it's spid is killed.
> > >
> > > I'd like to be able to Pause the server from within transact SQL.
> > > The only way I can see to do this is:
> > >
> > > exec master..xp_cmdshell "net pause mssqlserver", No_OUTPUT
> > > Kill the spids >= 50
> > > exec sp_dboption 'Database Name', 'dbo use only', true
> > > exec master..xp_cmdshell "net continue mssqlserver", No_OUTPUT
> > >
> > > Is there a way of pausing without using xp_cmdshell?
> > >
> > > Paul
> > >
> > >
> >
> >
>
We use a kill all users job and place the database in single user mode.
Unfortunately there is an app on the network that will automatically
reconnect if it's spid is killed.
I'd like to be able to Pause the server from within transact SQL.
The only way I can see to do this is:
exec master..xp_cmdshell "net pause mssqlserver", No_OUTPUT
Kill the spids >= 50
exec sp_dboption 'Database Name', 'dbo use only', true
exec master..xp_cmdshell "net continue mssqlserver", No_OUTPUT
Is there a way of pausing without using xp_cmdshell?
PaulThis might work...
ALTER DATABASE yourdb SET SINGLE_USER WITH ROLLBACK IMMEDIATE
GO
USE yourdb
GO
RESTORE ...
That way you should be the single_user before the application can reconnect.
--
HTH
Ryan Waight, MCDBA, MCSE
"Paul Cahill" <NOTpaul.cahillNOT@.blueyonder.co.uk> wrote in message
news:%23QjaYGZjDHA.1456@.tk2msftngp13.phx.gbl...
> We have a database that automatically restores at night from another
server.
> We use a kill all users job and place the database in single user mode.
> Unfortunately there is an app on the network that will automatically
> reconnect if it's spid is killed.
> I'd like to be able to Pause the server from within transact SQL.
> The only way I can see to do this is:
> exec master..xp_cmdshell "net pause mssqlserver", No_OUTPUT
> Kill the spids >= 50
> exec sp_dboption 'Database Name', 'dbo use only', true
> exec master..xp_cmdshell "net continue mssqlserver", No_OUTPUT
> Is there a way of pausing without using xp_cmdshell?
> Paul
>|||Or set the db in restricted user mode, assuming that that nasty app doesn't
use a login that is a member of the db_owner, db_creator or sysadmin roles.
ALTER DATABASE yourdb SET RESTRICTED_USER WITH ROLLBACK IMMEDIATE
Ryan, your code will not work. _no one_ can be in the database when you want
to restore it, not even the connection that is doing the restore, that
should be connected to a different database. You can do ALTER DATABASE...
and then RESTORE when you are connected to the master database and hope the
application won't be able to log back in between the statements, but that
won't always work.
--
Jacco Schalkwijk
SQL Server MVP
"Ryan Waight" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:eZhceRZjDHA.1004@.tk2msftngp13.phx.gbl...
> This might work...
> ALTER DATABASE yourdb SET SINGLE_USER WITH ROLLBACK IMMEDIATE
> GO
> USE yourdb
> GO
> RESTORE ...
> That way you should be the single_user before the application can
reconnect.
> --
> HTH
> Ryan Waight, MCDBA, MCSE
> "Paul Cahill" <NOTpaul.cahillNOT@.blueyonder.co.uk> wrote in message
> news:%23QjaYGZjDHA.1456@.tk2msftngp13.phx.gbl...
> > We have a database that automatically restores at night from another
> server.
> > We use a kill all users job and place the database in single user mode.
> > Unfortunately there is an app on the network that will automatically
> > reconnect if it's spid is killed.
> >
> > I'd like to be able to Pause the server from within transact SQL.
> > The only way I can see to do this is:
> >
> > exec master..xp_cmdshell "net pause mssqlserver", No_OUTPUT
> > Kill the spids >= 50
> > exec sp_dboption 'Database Name', 'dbo use only', true
> > exec master..xp_cmdshell "net continue mssqlserver", No_OUTPUT
> >
> > Is there a way of pausing without using xp_cmdshell?
> >
> > Paul
> >
> >
>|||> ALTER DATABASE yourdb SET SINGLE_USER WITH ROLLBACK IMMEDIATE
> GO
> USE yourdb
> GO
> RESTORE ...
>
Since a database can't be restored while it's in use, the database
context needs to be changed to some other database:
USE master
GO
RESTORE ...
Hope this helps.
Dan Guzman
SQL Server MVP
--
SQL FAQ links (courtesy Neil Pike):
http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
--
"Ryan Waight" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:eZhceRZjDHA.1004@.tk2msftngp13.phx.gbl...
> This might work...
> ALTER DATABASE yourdb SET SINGLE_USER WITH ROLLBACK IMMEDIATE
> GO
> USE yourdb
> GO
> RESTORE ...
> That way you should be the single_user before the application can
reconnect.
> --
> HTH
> Ryan Waight, MCDBA, MCSE
> "Paul Cahill" <NOTpaul.cahillNOT@.blueyonder.co.uk> wrote in message
> news:%23QjaYGZjDHA.1456@.tk2msftngp13.phx.gbl...
> > We have a database that automatically restores at night from another
> server.
> > We use a kill all users job and place the database in single user
mode.
> > Unfortunately there is an app on the network that will automatically
> > reconnect if it's spid is killed.
> >
> > I'd like to be able to Pause the server from within transact SQL.
> > The only way I can see to do this is:
> >
> > exec master..xp_cmdshell "net pause mssqlserver", No_OUTPUT
> > Kill the spids >= 50
> > exec sp_dboption 'Database Name', 'dbo use only', true
> > exec master..xp_cmdshell "net continue mssqlserver", No_OUTPUT
> >
> > Is there a way of pausing without using xp_cmdshell?
> >
> > Paul
> >
> >
>|||Apologies all. USE yourdb will of course use up the SINGLE_USER.
Should have read :-
ALTER DATABASE yourdb SET SINGLE_USER WITH ROLLBACK IMMEDIATE
GO
USE master
GO
RESTORE ...
--
HTH
Ryan Waight, MCDBA, MCSE
"Jacco Schalkwijk" <NOSPAMjaccos@.eurostop.co.uk> wrote in message
news:uamRLnZjDHA.1948@.TK2MSFTNGP12.phx.gbl...
> Or set the db in restricted user mode, assuming that that nasty app
doesn't
> use a login that is a member of the db_owner, db_creator or sysadmin
roles.
> ALTER DATABASE yourdb SET RESTRICTED_USER WITH ROLLBACK IMMEDIATE
> Ryan, your code will not work. _no one_ can be in the database when you
want
> to restore it, not even the connection that is doing the restore, that
> should be connected to a different database. You can do ALTER DATABASE...
> and then RESTORE when you are connected to the master database and hope
the
> application won't be able to log back in between the statements, but that
> won't always work.
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Ryan Waight" <Ryan_Waight@.nospam.hotmail.com> wrote in message
> news:eZhceRZjDHA.1004@.tk2msftngp13.phx.gbl...
> > This might work...
> >
> > ALTER DATABASE yourdb SET SINGLE_USER WITH ROLLBACK IMMEDIATE
> > GO
> > USE yourdb
> > GO
> > RESTORE ...
> >
> > That way you should be the single_user before the application can
> reconnect.
> >
> > --
> > HTH
> > Ryan Waight, MCDBA, MCSE
> >
> > "Paul Cahill" <NOTpaul.cahillNOT@.blueyonder.co.uk> wrote in message
> > news:%23QjaYGZjDHA.1456@.tk2msftngp13.phx.gbl...
> > > We have a database that automatically restores at night from another
> > server.
> > > We use a kill all users job and place the database in single user
mode.
> > > Unfortunately there is an app on the network that will automatically
> > > reconnect if it's spid is killed.
> > >
> > > I'd like to be able to Pause the server from within transact SQL.
> > > The only way I can see to do this is:
> > >
> > > exec master..xp_cmdshell "net pause mssqlserver", No_OUTPUT
> > > Kill the spids >= 50
> > > exec sp_dboption 'Database Name', 'dbo use only', true
> > > exec master..xp_cmdshell "net continue mssqlserver", No_OUTPUT
> > >
> > > Is there a way of pausing without using xp_cmdshell?
> > >
> > > Paul
> > >
> > >
> >
> >
>|||Thanks guys. Too busy looking at set dboption to remember alter database.
Paul
"Jacco Schalkwijk" <NOSPAMjaccos@.eurostop.co.uk> wrote in message
news:uamRLnZjDHA.1948@.TK2MSFTNGP12.phx.gbl...
> Or set the db in restricted user mode, assuming that that nasty app
doesn't
> use a login that is a member of the db_owner, db_creator or sysadmin
roles.
> ALTER DATABASE yourdb SET RESTRICTED_USER WITH ROLLBACK IMMEDIATE
> Ryan, your code will not work. _no one_ can be in the database when you
want
> to restore it, not even the connection that is doing the restore, that
> should be connected to a different database. You can do ALTER DATABASE...
> and then RESTORE when you are connected to the master database and hope
the
> application won't be able to log back in between the statements, but that
> won't always work.
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Ryan Waight" <Ryan_Waight@.nospam.hotmail.com> wrote in message
> news:eZhceRZjDHA.1004@.tk2msftngp13.phx.gbl...
> > This might work...
> >
> > ALTER DATABASE yourdb SET SINGLE_USER WITH ROLLBACK IMMEDIATE
> > GO
> > USE yourdb
> > GO
> > RESTORE ...
> >
> > That way you should be the single_user before the application can
> reconnect.
> >
> > --
> > HTH
> > Ryan Waight, MCDBA, MCSE
> >
> > "Paul Cahill" <NOTpaul.cahillNOT@.blueyonder.co.uk> wrote in message
> > news:%23QjaYGZjDHA.1456@.tk2msftngp13.phx.gbl...
> > > We have a database that automatically restores at night from another
> > server.
> > > We use a kill all users job and place the database in single user
mode.
> > > Unfortunately there is an app on the network that will automatically
> > > reconnect if it's spid is killed.
> > >
> > > I'd like to be able to Pause the server from within transact SQL.
> > > The only way I can see to do this is:
> > >
> > > exec master..xp_cmdshell "net pause mssqlserver", No_OUTPUT
> > > Kill the spids >= 50
> > > exec sp_dboption 'Database Name', 'dbo use only', true
> > > exec master..xp_cmdshell "net continue mssqlserver", No_OUTPUT
> > >
> > > Is there a way of pausing without using xp_cmdshell?
> > >
> > > Paul
> > >
> > >
> >
> >
>
Tuesday, March 20, 2012
Patching SQLServer/MSDE
Patching SQLServer/MSDE
We are developing a desktop application that will use an MSDE database. The
data in the DB we deploy cannot be read by users, or administrators of the b
ox or other SQL Server admins. To accomplish this, we have learned we would
have to install a separate
instance of SQLServer/MSDE on the user's PC (or, alternately, encrypt the da
tabase).
The downside to a separate instance is we would be responsible to apply any
SQL Server patches to our instance. Our software is given to our customers,
and we have no control over their machines, so we will have to issue servic
e patches for our software
that contain the SQL Server patches as they come out.
My question is this: Obviously, it will be difficult for us to get patches o
f our software out there immediately after each SQL Server patch is released
my Microsoft. Are there threats that SQL Server remedy that can possibly ha
ve an adverse effect on sof
tware/hardware outside of the our database that is using the SQL Server inst
ance? I'm wondering about our liability if say, we release our version of a
patch 1-2 months after Microsoft releases their patch. I know our database
may be threatened, but is
there the possibility the user's machines/network would also be threatened i
f certain patches are not installed in a timely matter? I understand how th
is would be a major issue if we were talking about patches to IIS, but not
so sure about SQL Server.
Any thoughts on this are greatly appreciated.
Thanks!MSDE can be configured to listen only on Shared Memory. This will limit
your exposure from
external machines. So, other machines won't be able to connect to your
instance of MSDE, since
it's not listening on TCP or Named Pipes. Only local connections would
succeed.
MBSA 1.2 can be used to scan the local machine to see if it needs any SQL
related security fixes.
This could be documented in your application notes.
http://www.microsoft.com/technet/se...s/mbsahome.mspx
You can also find out Best Practices on the web ;
http://www.microsoft.com/technet/pr...n/sp3sec00.mspx
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
We are developing a desktop application that will use an MSDE database. The
data in the DB we deploy cannot be read by users, or administrators of the b
ox or other SQL Server admins. To accomplish this, we have learned we would
have to install a separate
instance of SQLServer/MSDE on the user's PC (or, alternately, encrypt the da
tabase).
The downside to a separate instance is we would be responsible to apply any
SQL Server patches to our instance. Our software is given to our customers,
and we have no control over their machines, so we will have to issue servic
e patches for our software
that contain the SQL Server patches as they come out.
My question is this: Obviously, it will be difficult for us to get patches o
f our software out there immediately after each SQL Server patch is released
my Microsoft. Are there threats that SQL Server remedy that can possibly ha
ve an adverse effect on sof
tware/hardware outside of the our database that is using the SQL Server inst
ance? I'm wondering about our liability if say, we release our version of a
patch 1-2 months after Microsoft releases their patch. I know our database
may be threatened, but is
there the possibility the user's machines/network would also be threatened i
f certain patches are not installed in a timely matter? I understand how th
is would be a major issue if we were talking about patches to IIS, but not
so sure about SQL Server.
Any thoughts on this are greatly appreciated.
Thanks!MSDE can be configured to listen only on Shared Memory. This will limit
your exposure from
external machines. So, other machines won't be able to connect to your
instance of MSDE, since
it's not listening on TCP or Named Pipes. Only local connections would
succeed.
MBSA 1.2 can be used to scan the local machine to see if it needs any SQL
related security fixes.
This could be documented in your application notes.
http://www.microsoft.com/technet/se...s/mbsahome.mspx
You can also find out Best Practices on the web ;
http://www.microsoft.com/technet/pr...n/sp3sec00.mspx
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Monday, March 12, 2012
password storage
Hi everybody
I am working on a school project where I am writing a software for course registration. I have different users Students, Faculty, and Administrator. They are allowed to log in using their ID and password. I was wondering how could i store password and userID securly. Should I store it in the individual table or separately?
Any suggestion is appreciated. Also, if somebody has worked on this kind of project, please let me know.
Thanks a lot[I am using SQL 2000.|||You need to use what is known as "one-way" encryption. The good news is that this is simpler than "two-way" encryption where it is must be possible to both encypt and decrypt a text string. In one-way encryption you apply a function to encrypt the string, and then store the encrypted result in your table. When someone submits their password to log in, you apply the same encryption function to their password and then compare it to the encrypted version stored with their personal record. If the two match, you let the dude in.
There are some built-in encryption functions within SQL Server which are simple to use. I think they are called dbencrypt and dbcompare, or something similiar. The disadvantage with these is that they are undocumented functions, and if you upgrade your database to a new version of sql server Microsoft does not guarantee that it will use the same encryption algorythm in future versions. The result (and this has happened in past upgrades...) is that the passwords your users submit no longer match the versions stored in your database. They must all be reset and new ones must be entered.
You can write your own one-way encryption algorythm, or I have one that you can use that is more secure than the one supplied with SQL Server. (The built-in function has been cracked and the solution is available on the internet.)
blindman
I am working on a school project where I am writing a software for course registration. I have different users Students, Faculty, and Administrator. They are allowed to log in using their ID and password. I was wondering how could i store password and userID securly. Should I store it in the individual table or separately?
Any suggestion is appreciated. Also, if somebody has worked on this kind of project, please let me know.
Thanks a lot[I am using SQL 2000.|||You need to use what is known as "one-way" encryption. The good news is that this is simpler than "two-way" encryption where it is must be possible to both encypt and decrypt a text string. In one-way encryption you apply a function to encrypt the string, and then store the encrypted result in your table. When someone submits their password to log in, you apply the same encryption function to their password and then compare it to the encrypted version stored with their personal record. If the two match, you let the dude in.
There are some built-in encryption functions within SQL Server which are simple to use. I think they are called dbencrypt and dbcompare, or something similiar. The disadvantage with these is that they are undocumented functions, and if you upgrade your database to a new version of sql server Microsoft does not guarantee that it will use the same encryption algorythm in future versions. The result (and this has happened in past upgrades...) is that the passwords your users submit no longer match the versions stored in your database. They must all be reset and new ones must be entered.
You can write your own one-way encryption algorythm, or I have one that you can use that is more secure than the one supplied with SQL Server. (The built-in function has been cracked and the solution is available on the internet.)
blindman
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,
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
>
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
>
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...
>
Password Protect SQL SERVER
We have a database that we distribute for our application
to customers. We add users to a user table to allow
access to the web application only. How can I protect the
database with a secret password that only we know and the
customer can only access the data and use the database
but cannot get to the database using EM or Query Analyser
unless he knwos the password.
Help is appreciated.
I am new to all this so if some one could please guide me
to the right direction.
Thansk a lot.If they own the server and are sa then you can't. sa can see or do
everything on the server.
Andrew J. Kelly
SQL Server MVP
"HP" <anonymous@.discussions.microsoft.com> wrote in message
news:a26901c3eb2c$e9d5d7e0$a601280a@.phx.gbl...
user in the user table which will let them get to the
application if a valid user.
If they plan on buying sql server on thir own and putting
in our database is their a way we can stop them from
reading the database and egtting to its structure by
password protecting the database on the msde or by
encrypting the database.
can see or do
message
on to their box as the local admin they are essentially sa. You can remove
that account but that won't really stop someone from getting at it if they
want and have rights to the physical machine. The real answer here has
always been to make sure you have a good copywrite, NDA etc to cover this
area. There are some 3rd party tools to encrypt the db but it can be a real
hassle and in the long run I am not sure how effective it is. Take a look
on google for past posts regarding encryption and sql server for more
details.
Andrew J. Kelly
SQL Server MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:a63401c3eb5b$e253f450$a601280a@.phx.gbl...[QUOTE]
> We are the sa. We give to the customer MSDE with an added
> user in the user table which will let them get to the
> application if a valid user.
> If they plan on buying sql server on thir own and putting
> in our database is their a way we can stop them from
> reading the database and egtting to its structure by
> password protecting the database on the msde or by
> encrypting the database.
>
> can see or do
> message
> application
> the
> the
> Analyser
> me|||It is a serious weakness in MSSQL. There is no answer as far as we know.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:u25zg#16DHA.2472@.TK2MSFTNGP10.phx.gbl...
> By default there is a local NT admin account that is also sa. If they log
> on to their box as the local admin they are essentially sa. You can
remove
> that account but that won't really stop someone from getting at it if they
> want and have rights to the physical machine. The real answer here has
> always been to make sure you have a good copywrite, NDA etc to cover this
> area. There are some 3rd party tools to encrypt the db but it can be a
real
> hassle and in the long run I am not sure how effective it is. Take a look
> on google for past posts regarding encryption and sql server for more
> details.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> <anonymous@.discussions.microsoft.com> wrote in message
> news:a63401c3eb5b$e253f450$a601280a@.phx.gbl...
>
to customers. We add users to a user table to allow
access to the web application only. How can I protect the
database with a secret password that only we know and the
customer can only access the data and use the database
but cannot get to the database using EM or Query Analyser
unless he knwos the password.
Help is appreciated.
I am new to all this so if some one could please guide me
to the right direction.
Thansk a lot.If they own the server and are sa then you can't. sa can see or do
everything on the server.
Andrew J. Kelly
SQL Server MVP
"HP" <anonymous@.discussions.microsoft.com> wrote in message
news:a26901c3eb2c$e9d5d7e0$a601280a@.phx.gbl...
quote:|||We are the sa. We give to the customer MSDE with an added
> We have a database that we distribute for our application
> to customers. We add users to a user table to allow
> access to the web application only. How can I protect the
> database with a secret password that only we know and the
> customer can only access the data and use the database
> but cannot get to the database using EM or Query Analyser
> unless he knwos the password.
> Help is appreciated.
> I am new to all this so if some one could please guide me
> to the right direction.
> Thansk a lot.
user in the user table which will let them get to the
application if a valid user.
If they plan on buying sql server on thir own and putting
in our database is their a way we can stop them from
reading the database and egtting to its structure by
password protecting the database on the msde or by
encrypting the database.
quote:
>--Original Message--
>If they own the server and are sa then you can't. sa
can see or do
quote:
>everything on the server.
>--
>Andrew J. Kelly
>SQL Server MVP
>
>"HP" <anonymous@.discussions.microsoft.com> wrote in
message
quote:|||By default there is a local NT admin account that is also sa. If they log
>news:a26901c3eb2c$e9d5d7e0$a601280a@.phx.gbl...
application[QUOTE]
the[QUOTE]
the[QUOTE]
Analyser[QUOTE]
me[QUOTE]
>
>.
>
on to their box as the local admin they are essentially sa. You can remove
that account but that won't really stop someone from getting at it if they
want and have rights to the physical machine. The real answer here has
always been to make sure you have a good copywrite, NDA etc to cover this
area. There are some 3rd party tools to encrypt the db but it can be a real
hassle and in the long run I am not sure how effective it is. Take a look
on google for past posts regarding encryption and sql server for more
details.
Andrew J. Kelly
SQL Server MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:a63401c3eb5b$e253f450$a601280a@.phx.gbl...[QUOTE]
> We are the sa. We give to the customer MSDE with an added
> user in the user table which will let them get to the
> application if a valid user.
> If they plan on buying sql server on thir own and putting
> in our database is their a way we can stop them from
> reading the database and egtting to its structure by
> password protecting the database on the msde or by
> encrypting the database.
>
> can see or do
> message
> application
> the
> the
> Analyser
> me|||It is a serious weakness in MSSQL. There is no answer as far as we know.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:u25zg#16DHA.2472@.TK2MSFTNGP10.phx.gbl...
> By default there is a local NT admin account that is also sa. If they log
> on to their box as the local admin they are essentially sa. You can
remove
> that account but that won't really stop someone from getting at it if they
> want and have rights to the physical machine. The real answer here has
> always been to make sure you have a good copywrite, NDA etc to cover this
> area. There are some 3rd party tools to encrypt the db but it can be a
real
> hassle and in the long run I am not sure how effective it is. Take a look
> on google for past posts regarding encryption and sql server for more
> details.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> <anonymous@.discussions.microsoft.com> wrote in message
> news:a63401c3eb5b$e253f450$a601280a@.phx.gbl...
>
Wednesday, March 7, 2012
Password expired
Hello!
My users SQL passwords expires after 90 days and that's what I want.
The problem is that I want the user to be able to change their password when
this happends.
I developed a small application for this purpose, but I can't get it to
work.
There are an asp.net page with five textboxes: server, loginname,
oldpassword, newpassword, and confirmnewpassword.
First I'm trying to establish a sqlconnection with the server, loginname and
the oldpassword, but the row conn.open(); raises an error with: Reason: The
password of the account has expired
Well, I can understand why, but I don't understand how to solve this
solution.
The next row where ment to be ALTER LOGIN thename WITH PASSWORD = 'blabla2'
OLD_PASSWORD = 'blabla1', and this works when able to login, but in this
case I can't establish the connection.
How to solve this
Best Regards /MagnusMagnus,
To achieve this you should be using windows integrated authentication rather
than SQL, this would be the simplest way.
You could do this in SQL authentication as well but bit complicated, what
you should do is, your password changing application should use a dedicated
sql use account, that login should have all db_admin right. Use that login
to logon to sql server to change the password
Regards
VT
Knowledge is power, share it
http://oneplace4sql.blogspot.com/
"Magnus" <magnus.blomberg@.skanska.se> wrote in message
news:uNBOhw4lHHA.588@.TK2MSFTNGP06.phx.gbl...
> Hello!
> My users SQL passwords expires after 90 days and that's what I want.
> The problem is that I want the user to be able to change their password
> when this happends.
> I developed a small application for this purpose, but I can't get it to
> work.
> There are an asp.net page with five textboxes: server, loginname,
> oldpassword, newpassword, and confirmnewpassword.
> First I'm trying to establish a sqlconnection with the server, loginname
> and the oldpassword, but the row conn.open(); raises an error with:
> Reason: The password of the account has expired
> Well, I can understand why, but I don't understand how to solve this
> solution.
> The next row where ment to be ALTER LOGIN thename WITH PASSWORD =
> 'blabla2' OLD_PASSWORD = 'blabla1', and this works when able to login, but
> in this case I can't establish the connection.
> How to solve this
> Best Regards /Magnus
>
>|||Hi!
Thanks. Well, I know Windows Authentication is the prefered way, but in this
case, not!
Okay, so I setup an account that has access to change the password then. So
it's not possible to use the existing login to change the password? That
mean that password expired has the same impact as account locked out or
account disabled in this case?
Should I use sa or a dedicated?
Regards Magnus
"vt" <vinu.t.1976@.gmail.com> wrote in message
news:OqDR2S5lHHA.1216@.TK2MSFTNGP03.phx.gbl...
> Magnus,
> To achieve this you should be using windows integrated authentication
> rather than SQL, this would be the simplest way.
> You could do this in SQL authentication as well but bit complicated, what
> you should do is, your password changing application should use a
> dedicated sql use account, that login should have all db_admin right. Use
> that login to logon to sql server to change the password
>
> Regards
> VT
> Knowledge is power, share it
> http://oneplace4sql.blogspot.com/
>
>
>
>
> "Magnus" <magnus.blomberg@.skanska.se> wrote in message
> news:uNBOhw4lHHA.588@.TK2MSFTNGP06.phx.gbl...
>|||Personally I will not use sa, I would rather create a login that's only for
this purpose
Regards
VT
Knowledge is power, share it
http://oneplace4sql.blogspot.com/
"Magnus" <magnus.blomberg@.skanska.se> wrote in message
news:%23$hIvg5lHHA.4592@.TK2MSFTNGP05.phx.gbl...
> Hi!
> Thanks. Well, I know Windows Authentication is the prefered way, but in
> this case, not!
> Okay, so I setup an account that has access to change the password then.
> So it's not possible to use the existing login to change the password?
> That mean that password expired has the same impact as account locked out
> or account disabled in this case?
> Should I use sa or a dedicated?
> Regards Magnus
>
> "vt" <vinu.t.1976@.gmail.com> wrote in message
> news:OqDR2S5lHHA.1216@.TK2MSFTNGP03.phx.gbl...
>|||A user can change their own password as long as they change it before it
expires. If you let them change it after it expires, there would be no
point in having it expire would there? Once it expires, the dba will have
to change it for them. I suggest telling them to put a reminder in their
calendar to change the password a week or so before it expires.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Magnus" <magnus.blomberg@.skanska.se> wrote in message
news:uNBOhw4lHHA.588@.TK2MSFTNGP06.phx.gbl...
> Hello!
> My users SQL passwords expires after 90 days and that's what I want.
> The problem is that I want the user to be able to change their password
> when this happends.
> I developed a small application for this purpose, but I can't get it to
> work.
> There are an asp.net page with five textboxes: server, loginname,
> oldpassword, newpassword, and confirmnewpassword.
> First I'm trying to establish a sqlconnection with the server, loginname
> and the oldpassword, but the row conn.open(); raises an error with:
> Reason: The password of the account has expired
> Well, I can understand why, but I don't understand how to solve this
> solution.
> The next row where ment to be ALTER LOGIN thename WITH PASSWORD =
> 'blabla2' OLD_PASSWORD = 'blabla1', and this works when able to login, but
> in this case I can't establish the connection.
> How to solve this
> Best Regards /Magnus
>
>|||[posted and mailed]
Magnus (magnus.blomberg@.skanska.se) writes:
> My users SQL passwords expires after 90 days and that's what I want. The
> problem is that I want the user to be able to change their password when
> this happends.
> I developed a small application for this purpose, but I can't get it to
> work.
> There are an asp.net page with five textboxes: server, loginname,
> oldpassword, newpassword, and confirmnewpassword.
Despite what Roger and vt says, this is indeed possible. You simply connect
to SQL Server and in the connect string you pass the new password in the
Password property. The old password you pass in the Old Password property.
For instance:
PROVIDER=SQLNCLI;Server=ThatServer;Datab
ase=ThatDatabase;UID=ThisUser;
Password=SprillansNytt;Old Password=Frrarets
Note that you must use the SQLNCLI provider, as SQLOLEDB does not support
the Old Password property.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||So passwords never really expire? Cool!
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns99339BA797939Yazorman@.127.0.0.1...
> [posted and mailed]
> Magnus (magnus.blomberg@.skanska.se) writes:
> Despite what Roger and vt says, this is indeed possible. You simply
> connect
> to SQL Server and in the connect string you pass the new password in the
> Password property. The old password you pass in the Old Password property.
> For instance:
> PROVIDER=SQLNCLI;Server=ThatServer;Datab
ase=ThatDatabase;UID=ThisUser;
> Password=SprillansNytt;Old Password=Frrarets
> Note that you must use the SQLNCLI provider, as SQLOLEDB does not support
> the Old Password property.
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx|||Thanks Erland!
I thougth it should be a way, since this is the same behavior as for the AD
accounts. When it has expired, you have to change the password, but you can
still do it!
Regarding to the fact that SQLOLEDB provider doesn't support this, how to
change the code below to work?
String strconn = "PROVIDER=SQLNCLI;Server=" + TextBox1.Text +
";Database=master;UID=" + TextBox2.Text +
";Password=" + TextBox4.Text + ";Old Password=" + TextBox3.Text;
System.Data.SqlClient.SqlConnection conn = new
System.Data.SqlClient.SqlConnection(strconn);
Is it OK to use this kind of code? Injection must be impossible/useless to
use within the connection string. Isn't it?
Best regards
/Magnus
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns99339BA797939Yazorman@.127.0.0.1...
> [posted and mailed]
> Magnus (magnus.blomberg@.skanska.se) writes:
> Despite what Roger and vt says, this is indeed possible. You simply
> connect
> to SQL Server and in the connect string you pass the new password in the
> Password property. The old password you pass in the Old Password property.
> For instance:
> PROVIDER=SQLNCLI;Server=ThatServer;Datab
ase=ThatDatabase;UID=ThisUser;
> Password=SprillansNytt;Old Password=Frrarets
> Note that you must use the SQLNCLI provider, as SQLOLEDB does not support
> the Old Password property.
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx|||At the ...conn = new... row I get the error message Keyword not supported:
'provider'.
/Magnus
"Magnus" <magnus.blomberg@.skanska.se> wrote in message
news:uLGHYm5mHHA.1220@.TK2MSFTNGP03.phx.gbl...
> Thanks Erland!
> I thougth it should be a way, since this is the same behavior as for the
> AD accounts. When it has expired, you have to change the password, but you
> can still do it!
> Regarding to the fact that SQLOLEDB provider doesn't support this, how to
> change the code below to work?
> String strconn = "PROVIDER=SQLNCLI;Server=" + TextBox1.Text +
> ";Database=master;UID=" + TextBox2.Text +
> ";Password=" + TextBox4.Text + ";Old Password=" +
> TextBox3.Text;
> System.Data.SqlClient.SqlConnection conn = new
> System.Data.SqlClient.SqlConnection(strconn);
> Is it OK to use this kind of code? Injection must be impossible/useless to
> use within the connection string. Isn't it?
> Best regards
> /Magnus
>
> "Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
> news:Xns99339BA797939Yazorman@.127.0.0.1...
>|||Magnus (magnus.blomberg@.skanska.se) writes:
> I thougth it should be a way, since this is the same behavior as for the
> AD accounts. When it has expired, you have to change the password, but
> you can still do it!
> Regarding to the fact that SQLOLEDB provider doesn't support this, how to
> change the code below to work?
> String strconn = "PROVIDER=SQLNCLI;Server=" + TextBox1.Text +
> ";Database=master;UID=" + TextBox2.Text +
> ";Password=" + TextBox4.Text + ";Old Password=" + TextBox3.Text;
> System.Data.SqlClient.SqlConnection conn = new
> System.Data.SqlClient.SqlConnection(strconn);
> Is it OK to use this kind of code? Injection must be impossible/useless to
> use within the connection string. Isn't it?
Impossible it is not. I mean if the user think you should run with
MARS enabled, he can arrange it. More importantly, the user may want to
use a semicolon in his password.
> At the ...conn = new... row I get the error message Keyword not supported:
> 'provider'.
I XXX that you use ASP .Net, so I guess that you are using SqlClient as
your API. (Well, you should.) I looked at SQL Native Client, since this
is where I've played with this feature. Just remove the Provider part.
Not that I know, but I guess the connection-string properties are the
same with SqlClient.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx
My users SQL passwords expires after 90 days and that's what I want.
The problem is that I want the user to be able to change their password when
this happends.
I developed a small application for this purpose, but I can't get it to
work.
There are an asp.net page with five textboxes: server, loginname,
oldpassword, newpassword, and confirmnewpassword.
First I'm trying to establish a sqlconnection with the server, loginname and
the oldpassword, but the row conn.open(); raises an error with: Reason: The
password of the account has expired
Well, I can understand why, but I don't understand how to solve this
solution.
The next row where ment to be ALTER LOGIN thename WITH PASSWORD = 'blabla2'
OLD_PASSWORD = 'blabla1', and this works when able to login, but in this
case I can't establish the connection.
How to solve this
Best Regards /MagnusMagnus,
To achieve this you should be using windows integrated authentication rather
than SQL, this would be the simplest way.
You could do this in SQL authentication as well but bit complicated, what
you should do is, your password changing application should use a dedicated
sql use account, that login should have all db_admin right. Use that login
to logon to sql server to change the password
Regards
VT
Knowledge is power, share it
http://oneplace4sql.blogspot.com/
"Magnus" <magnus.blomberg@.skanska.se> wrote in message
news:uNBOhw4lHHA.588@.TK2MSFTNGP06.phx.gbl...
> Hello!
> My users SQL passwords expires after 90 days and that's what I want.
> The problem is that I want the user to be able to change their password
> when this happends.
> I developed a small application for this purpose, but I can't get it to
> work.
> There are an asp.net page with five textboxes: server, loginname,
> oldpassword, newpassword, and confirmnewpassword.
> First I'm trying to establish a sqlconnection with the server, loginname
> and the oldpassword, but the row conn.open(); raises an error with:
> Reason: The password of the account has expired
> Well, I can understand why, but I don't understand how to solve this
> solution.
> The next row where ment to be ALTER LOGIN thename WITH PASSWORD =
> 'blabla2' OLD_PASSWORD = 'blabla1', and this works when able to login, but
> in this case I can't establish the connection.
> How to solve this
> Best Regards /Magnus
>
>|||Hi!
Thanks. Well, I know Windows Authentication is the prefered way, but in this
case, not!
Okay, so I setup an account that has access to change the password then. So
it's not possible to use the existing login to change the password? That
mean that password expired has the same impact as account locked out or
account disabled in this case?
Should I use sa or a dedicated?
Regards Magnus
"vt" <vinu.t.1976@.gmail.com> wrote in message
news:OqDR2S5lHHA.1216@.TK2MSFTNGP03.phx.gbl...
> Magnus,
> To achieve this you should be using windows integrated authentication
> rather than SQL, this would be the simplest way.
> You could do this in SQL authentication as well but bit complicated, what
> you should do is, your password changing application should use a
> dedicated sql use account, that login should have all db_admin right. Use
> that login to logon to sql server to change the password
>
> Regards
> VT
> Knowledge is power, share it
> http://oneplace4sql.blogspot.com/
>
>
>
>
> "Magnus" <magnus.blomberg@.skanska.se> wrote in message
> news:uNBOhw4lHHA.588@.TK2MSFTNGP06.phx.gbl...
>|||Personally I will not use sa, I would rather create a login that's only for
this purpose
Regards
VT
Knowledge is power, share it
http://oneplace4sql.blogspot.com/
"Magnus" <magnus.blomberg@.skanska.se> wrote in message
news:%23$hIvg5lHHA.4592@.TK2MSFTNGP05.phx.gbl...
> Hi!
> Thanks. Well, I know Windows Authentication is the prefered way, but in
> this case, not!
> Okay, so I setup an account that has access to change the password then.
> So it's not possible to use the existing login to change the password?
> That mean that password expired has the same impact as account locked out
> or account disabled in this case?
> Should I use sa or a dedicated?
> Regards Magnus
>
> "vt" <vinu.t.1976@.gmail.com> wrote in message
> news:OqDR2S5lHHA.1216@.TK2MSFTNGP03.phx.gbl...
>|||A user can change their own password as long as they change it before it
expires. If you let them change it after it expires, there would be no
point in having it expire would there? Once it expires, the dba will have
to change it for them. I suggest telling them to put a reminder in their
calendar to change the password a week or so before it expires.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Magnus" <magnus.blomberg@.skanska.se> wrote in message
news:uNBOhw4lHHA.588@.TK2MSFTNGP06.phx.gbl...
> Hello!
> My users SQL passwords expires after 90 days and that's what I want.
> The problem is that I want the user to be able to change their password
> when this happends.
> I developed a small application for this purpose, but I can't get it to
> work.
> There are an asp.net page with five textboxes: server, loginname,
> oldpassword, newpassword, and confirmnewpassword.
> First I'm trying to establish a sqlconnection with the server, loginname
> and the oldpassword, but the row conn.open(); raises an error with:
> Reason: The password of the account has expired
> Well, I can understand why, but I don't understand how to solve this
> solution.
> The next row where ment to be ALTER LOGIN thename WITH PASSWORD =
> 'blabla2' OLD_PASSWORD = 'blabla1', and this works when able to login, but
> in this case I can't establish the connection.
> How to solve this
> Best Regards /Magnus
>
>|||[posted and mailed]
Magnus (magnus.blomberg@.skanska.se) writes:
> My users SQL passwords expires after 90 days and that's what I want. The
> problem is that I want the user to be able to change their password when
> this happends.
> I developed a small application for this purpose, but I can't get it to
> work.
> There are an asp.net page with five textboxes: server, loginname,
> oldpassword, newpassword, and confirmnewpassword.
Despite what Roger and vt says, this is indeed possible. You simply connect
to SQL Server and in the connect string you pass the new password in the
Password property. The old password you pass in the Old Password property.
For instance:
PROVIDER=SQLNCLI;Server=ThatServer;Datab
ase=ThatDatabase;UID=ThisUser;
Password=SprillansNytt;Old Password=Frrarets
Note that you must use the SQLNCLI provider, as SQLOLEDB does not support
the Old Password property.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||So passwords never really expire? Cool!
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns99339BA797939Yazorman@.127.0.0.1...
> [posted and mailed]
> Magnus (magnus.blomberg@.skanska.se) writes:
> Despite what Roger and vt says, this is indeed possible. You simply
> connect
> to SQL Server and in the connect string you pass the new password in the
> Password property. The old password you pass in the Old Password property.
> For instance:
> PROVIDER=SQLNCLI;Server=ThatServer;Datab
ase=ThatDatabase;UID=ThisUser;
> Password=SprillansNytt;Old Password=Frrarets
> Note that you must use the SQLNCLI provider, as SQLOLEDB does not support
> the Old Password property.
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx|||Thanks Erland!
I thougth it should be a way, since this is the same behavior as for the AD
accounts. When it has expired, you have to change the password, but you can
still do it!
Regarding to the fact that SQLOLEDB provider doesn't support this, how to
change the code below to work?
String strconn = "PROVIDER=SQLNCLI;Server=" + TextBox1.Text +
";Database=master;UID=" + TextBox2.Text +
";Password=" + TextBox4.Text + ";Old Password=" + TextBox3.Text;
System.Data.SqlClient.SqlConnection conn = new
System.Data.SqlClient.SqlConnection(strconn);
Is it OK to use this kind of code? Injection must be impossible/useless to
use within the connection string. Isn't it?
Best regards
/Magnus
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns99339BA797939Yazorman@.127.0.0.1...
> [posted and mailed]
> Magnus (magnus.blomberg@.skanska.se) writes:
> Despite what Roger and vt says, this is indeed possible. You simply
> connect
> to SQL Server and in the connect string you pass the new password in the
> Password property. The old password you pass in the Old Password property.
> For instance:
> PROVIDER=SQLNCLI;Server=ThatServer;Datab
ase=ThatDatabase;UID=ThisUser;
> Password=SprillansNytt;Old Password=Frrarets
> Note that you must use the SQLNCLI provider, as SQLOLEDB does not support
> the Old Password property.
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx|||At the ...conn = new... row I get the error message Keyword not supported:
'provider'.
/Magnus
"Magnus" <magnus.blomberg@.skanska.se> wrote in message
news:uLGHYm5mHHA.1220@.TK2MSFTNGP03.phx.gbl...
> Thanks Erland!
> I thougth it should be a way, since this is the same behavior as for the
> AD accounts. When it has expired, you have to change the password, but you
> can still do it!
> Regarding to the fact that SQLOLEDB provider doesn't support this, how to
> change the code below to work?
> String strconn = "PROVIDER=SQLNCLI;Server=" + TextBox1.Text +
> ";Database=master;UID=" + TextBox2.Text +
> ";Password=" + TextBox4.Text + ";Old Password=" +
> TextBox3.Text;
> System.Data.SqlClient.SqlConnection conn = new
> System.Data.SqlClient.SqlConnection(strconn);
> Is it OK to use this kind of code? Injection must be impossible/useless to
> use within the connection string. Isn't it?
> Best regards
> /Magnus
>
> "Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
> news:Xns99339BA797939Yazorman@.127.0.0.1...
>|||Magnus (magnus.blomberg@.skanska.se) writes:
> I thougth it should be a way, since this is the same behavior as for the
> AD accounts. When it has expired, you have to change the password, but
> you can still do it!
> Regarding to the fact that SQLOLEDB provider doesn't support this, how to
> change the code below to work?
> String strconn = "PROVIDER=SQLNCLI;Server=" + TextBox1.Text +
> ";Database=master;UID=" + TextBox2.Text +
> ";Password=" + TextBox4.Text + ";Old Password=" + TextBox3.Text;
> System.Data.SqlClient.SqlConnection conn = new
> System.Data.SqlClient.SqlConnection(strconn);
> Is it OK to use this kind of code? Injection must be impossible/useless to
> use within the connection string. Isn't it?
Impossible it is not. I mean if the user think you should run with
MARS enabled, he can arrange it. More importantly, the user may want to
use a semicolon in his password.
> At the ...conn = new... row I get the error message Keyword not supported:
> 'provider'.
I XXX that you use ASP .Net, so I guess that you are using SqlClient as
your API. (Well, you should.) I looked at SQL Native Client, since this
is where I've played with this feature. Just remove the Provider part.
Not that I know, but I guess the connection-string properties are the
same with SqlClient.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx
Password encryption and decryption
Hi there,
Currently I working on a project that requires users to enter a username and
password before they can use one of our internal administration system.
The system is built using VB6.0 and SQL server 200o on Windows 2000.
Can someone please suggest a way of encrypting and decrypting the password
so that the passwords can be stored in the databaseCall the Windows Crypto API in the VB6 application.
Lots of information on MSDN.
Pity you are not using .NET as there, it is 100's of times easier to
implement.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Padmini" <Padmini@.discussions.microsoft.com> wrote in message
news:3DB5CD8B-17E8-459E-9CD8-331952A8FD90@.microsoft.com...
> Hi there,
> Currently I working on a project that requires users to enter a username
> and
> password before they can use one of our internal administration system.
> The system is built using VB6.0 and SQL server 200o on Windows 2000.
> Can someone please suggest a way of encrypting and decrypting the password
> so that the passwords can be stored in the database|||Don't store the password in the database. Password recovery mechanisms are
inherently insecure. Instead store a secure hash, including salt. The MS
crypto API provides the tools you need.
David Portas
SQL Server MVP
--|||are there any code examples of doing this anywhere?
"David Portas" wrote:
> Don't store the password in the database. Password recovery mechanisms are
> inherently insecure. Instead store a secure hash, including salt. The MS
> crypto API provides the tools you need.
> --
> David Portas
> SQL Server MVP
> --
Currently I working on a project that requires users to enter a username and
password before they can use one of our internal administration system.
The system is built using VB6.0 and SQL server 200o on Windows 2000.
Can someone please suggest a way of encrypting and decrypting the password
so that the passwords can be stored in the databaseCall the Windows Crypto API in the VB6 application.
Lots of information on MSDN.
Pity you are not using .NET as there, it is 100's of times easier to
implement.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Padmini" <Padmini@.discussions.microsoft.com> wrote in message
news:3DB5CD8B-17E8-459E-9CD8-331952A8FD90@.microsoft.com...
> Hi there,
> Currently I working on a project that requires users to enter a username
> and
> password before they can use one of our internal administration system.
> The system is built using VB6.0 and SQL server 200o on Windows 2000.
> Can someone please suggest a way of encrypting and decrypting the password
> so that the passwords can be stored in the database|||Don't store the password in the database. Password recovery mechanisms are
inherently insecure. Instead store a secure hash, including salt. The MS
crypto API provides the tools you need.
David Portas
SQL Server MVP
--|||are there any code examples of doing this anywhere?
"David Portas" wrote:
> Don't store the password in the database. Password recovery mechanisms are
> inherently insecure. Instead store a secure hash, including salt. The MS
> crypto API provides the tools you need.
> --
> David Portas
> SQL Server MVP
> --
Password Complexity problem
I need to restore a v2000 database to a v2005 database including all users.
How can I disable password complexity so that I can achieve this ? I'm sure others have run into this prblem.
Thanks in advance,
Nancy
You can do this. Password complexity is a feature of the underlying OS (Windows 2003 and greater). the policy is a local policy which can be overwritten by a domain policy. Open the MMC add the Group Policy Editor (for local computer) and navigate to the security settings. if you are domain controlled, you will see the setting evtl. greyed out. You will have to ask your administrator then to temporary disable it for this server.
Jens K. Suessmeyer
http://www.sqlserver2005.de
Password complexity in SQL
We have a SQL 2000 server and a client app that accesses it. We utilize SQL
authentication for the users who have already logged into the Windows domain
with a separate userid and password.
We are currently going through a certification and accredidation test and
one of the things we are getting dinged on is that we do not require complex
passwords with the SQL password. I see nowhere in SQL server to setup
mandatory password complexities, ie: minimum 8 characters, at least 1
number, 1 capital letter, etc.
Is there somewhere in SQL 2000 that a password policy for the SQL password
can be setup?Not for SQL Server 2000 not I'm aware of, unless you build and enfore this
functionality yourself. In SQL Server 2005, SQL passwords will abide by the
Windows OS machine/domain password policy with Windows Server 2003 and
above. In either version, its preferred to use only Windows logins which
have had password complexity policies for some time. Do you really need to
support SQL logins?
Cheers,
Bob Beauchemin
http://www.SQLskills.com/blogs/bobb
"Rockitman" <Rockitman@.discussions.microsoft.com> wrote in message
news:8F93457A-538A-4FD5-8551-79A9404AB777@.microsoft.com...
> We have a SQL 2000 server and a client app that accesses it. We utilize
> SQL
> authentication for the users who have already logged into the Windows
> domain
> with a separate userid and password.
> We are currently going through a certification and accredidation test and
> one of the things we are getting dinged on is that we do not require
> complex
> passwords with the SQL password. I see nowhere in SQL server to setup
> mandatory password complexities, ie: minimum 8 characters, at least 1
> number, 1 capital letter, etc.
> Is there somewhere in SQL 2000 that a password policy for the SQL password
> can be setup?|||Well that's what I'm trying to tell these guys. We already meet the
password requirements as a user cannot even get access to the client app
without first logging into the domain with a required complex password. If
I
change all the users to Windows authentication, when they access the client
app, will it just automatically open or will they have to reenter their
Domain id and password?
"Bob Beauchemin" wrote:
> Not for SQL Server 2000 not I'm aware of, unless you build and enfore this
> functionality yourself. In SQL Server 2005, SQL passwords will abide by th
e
> Windows OS machine/domain password policy with Windows Server 2003 and
> above. In either version, its preferred to use only Windows logins which
> have had password complexity policies for some time. Do you really need to
> support SQL logins?
> Cheers,
> Bob Beauchemin
> http://www.SQLskills.com/blogs/bobb|||If you use Windows authentication, their existing credentials are used, they
don't need to reenter. You'd need to change the connection strings in the
client apps to make this happen. There are some issues with delegation of
credentials (NTLM credentials are good for 1 inter-machine "hop", Kerberos
credentials can do multi-machine only if you have delegation enabled on a
server level) so you'd want to ensure that your application architecture can
accomdate this, especially if you have an intranet application. There's a
section in the SQL Server Books Online with details.
Cheers,
Bob Beauchemin
http://www.SQLskills.com/blogs/bobb
"Rockitman" <Rockitman@.discussions.microsoft.com> wrote in message
news:3A6FD24F-14C1-4C15-B559-CD1489849867@.microsoft.com...
> Well that's what I'm trying to tell these guys. We already meet the
> password requirements as a user cannot even get access to the client app
> without first logging into the domain with a required complex password.
> If I
> change all the users to Windows authentication, when they access the
> client
> app, will it just automatically open or will they have to reenter their
> Domain id and password?
> "Bob Beauchemin" wrote:
>
>
authentication for the users who have already logged into the Windows domain
with a separate userid and password.
We are currently going through a certification and accredidation test and
one of the things we are getting dinged on is that we do not require complex
passwords with the SQL password. I see nowhere in SQL server to setup
mandatory password complexities, ie: minimum 8 characters, at least 1
number, 1 capital letter, etc.
Is there somewhere in SQL 2000 that a password policy for the SQL password
can be setup?Not for SQL Server 2000 not I'm aware of, unless you build and enfore this
functionality yourself. In SQL Server 2005, SQL passwords will abide by the
Windows OS machine/domain password policy with Windows Server 2003 and
above. In either version, its preferred to use only Windows logins which
have had password complexity policies for some time. Do you really need to
support SQL logins?
Cheers,
Bob Beauchemin
http://www.SQLskills.com/blogs/bobb
"Rockitman" <Rockitman@.discussions.microsoft.com> wrote in message
news:8F93457A-538A-4FD5-8551-79A9404AB777@.microsoft.com...
> We have a SQL 2000 server and a client app that accesses it. We utilize
> SQL
> authentication for the users who have already logged into the Windows
> domain
> with a separate userid and password.
> We are currently going through a certification and accredidation test and
> one of the things we are getting dinged on is that we do not require
> complex
> passwords with the SQL password. I see nowhere in SQL server to setup
> mandatory password complexities, ie: minimum 8 characters, at least 1
> number, 1 capital letter, etc.
> Is there somewhere in SQL 2000 that a password policy for the SQL password
> can be setup?|||Well that's what I'm trying to tell these guys. We already meet the
password requirements as a user cannot even get access to the client app
without first logging into the domain with a required complex password. If
I
change all the users to Windows authentication, when they access the client
app, will it just automatically open or will they have to reenter their
Domain id and password?
"Bob Beauchemin" wrote:
> Not for SQL Server 2000 not I'm aware of, unless you build and enfore this
> functionality yourself. In SQL Server 2005, SQL passwords will abide by th
e
> Windows OS machine/domain password policy with Windows Server 2003 and
> above. In either version, its preferred to use only Windows logins which
> have had password complexity policies for some time. Do you really need to
> support SQL logins?
> Cheers,
> Bob Beauchemin
> http://www.SQLskills.com/blogs/bobb|||If you use Windows authentication, their existing credentials are used, they
don't need to reenter. You'd need to change the connection strings in the
client apps to make this happen. There are some issues with delegation of
credentials (NTLM credentials are good for 1 inter-machine "hop", Kerberos
credentials can do multi-machine only if you have delegation enabled on a
server level) so you'd want to ensure that your application architecture can
accomdate this, especially if you have an intranet application. There's a
section in the SQL Server Books Online with details.
Cheers,
Bob Beauchemin
http://www.SQLskills.com/blogs/bobb
"Rockitman" <Rockitman@.discussions.microsoft.com> wrote in message
news:3A6FD24F-14C1-4C15-B559-CD1489849867@.microsoft.com...
> Well that's what I'm trying to tell these guys. We already meet the
> password requirements as a user cannot even get access to the client app
> without first logging into the domain with a required complex password.
> If I
> change all the users to Windows authentication, when they access the
> client
> app, will it just automatically open or will they have to reenter their
> Domain id and password?
> "Bob Beauchemin" wrote:
>
>
Password change
Hi,
How do I set up sercurity enforcement to have users change their sql
passwords every 30 days?
Thanks
mecn,
SQL Server adopts its policies from the Windows local policies. So, I
believe that you would have to change those.
(But, if your servers are having their policies synchronized with the domain
policies, I don't know if your changes will stick locally.)
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
> Hi,
> How do I set up sercurity enforcement to have users change their sql
> passwords every 30 days?
> Thanks
>
|||In 2005 you do it in the CREATE LOGIN 8or change with ALTER LOGIN) command. In 2000, you can't do
that.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"mecn" <mecn2002@.yahoo.com> wrote in message news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
> Hi,
> How do I set up sercurity enforcement to have users change their sql
> passwords every 30 days?
> Thanks
>
|||My sql2005 is sql authentication. so the users are not windows based users
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:%234wTN0IyHHA.4392@.TK2MSFTNGP04.phx.gbl...
> mecn,
> SQL Server adopts its policies from the Windows local policies. So, I
> believe that you would have to change those.
> (But, if your servers are having their policies synchronized with the
> domain policies, I don't know if your changes will stick locally.)
> RLF
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
>
|||Thanks all
let me say it clearly, I need to enforce sql 2005 sql (authentication) users
to change their passwords every 30 days.
Is there a setting or check box that i could fill?
I don't know how.
Thanks
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:F6BD45B2-27C2-4E6A-924E-FF9DDA37B970@.microsoft.com...
> In 2005 you do it in the CREATE LOGIN 8or change with ALTER LOGIN)
> command. In 2000, you can't do that.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
>
|||Yes, I know. For SQL Server logins, SQL Server adopts the policies from the
Windows local server that is running the SQL Server. (Windows does its own
managing of Windows login policies.)
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:uvKX38IyHHA.1208@.TK2MSFTNGP03.phx.gbl...
> My sql2005 is sql authentication. so the users are not windows based users
>
> "Russell Fields" <russellfields@.nomail.com> wrote in message
> news:%234wTN0IyHHA.4392@.TK2MSFTNGP04.phx.gbl...
>
|||Did you read about the CREATE LOGIN command in Books Online? If you do, you will find a parameter
which specifies that the Windows policy password expiration policy should apply to this SQL Server
login.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"mecn" <mecn2002@.yahoo.com> wrote in message news:u978YDJyHHA.4928@.TK2MSFTNGP03.phx.gbl...
> Thanks all
> let me say it clearly, I need to enforce sql 2005 sql (authentication) users to change their
> passwords every 30 days.
> Is there a setting or check box that i could fill?
> I don't know how.
> Thanks
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:F6BD45B2-27C2-4E6A-924E-FF9DDA37B970@.microsoft.com...
>
How do I set up sercurity enforcement to have users change their sql
passwords every 30 days?
Thanks
mecn,
SQL Server adopts its policies from the Windows local policies. So, I
believe that you would have to change those.
(But, if your servers are having their policies synchronized with the domain
policies, I don't know if your changes will stick locally.)
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
> Hi,
> How do I set up sercurity enforcement to have users change their sql
> passwords every 30 days?
> Thanks
>
|||In 2005 you do it in the CREATE LOGIN 8or change with ALTER LOGIN) command. In 2000, you can't do
that.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"mecn" <mecn2002@.yahoo.com> wrote in message news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
> Hi,
> How do I set up sercurity enforcement to have users change their sql
> passwords every 30 days?
> Thanks
>
|||My sql2005 is sql authentication. so the users are not windows based users
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:%234wTN0IyHHA.4392@.TK2MSFTNGP04.phx.gbl...
> mecn,
> SQL Server adopts its policies from the Windows local policies. So, I
> believe that you would have to change those.
> (But, if your servers are having their policies synchronized with the
> domain policies, I don't know if your changes will stick locally.)
> RLF
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
>
|||Thanks all
let me say it clearly, I need to enforce sql 2005 sql (authentication) users
to change their passwords every 30 days.
Is there a setting or check box that i could fill?
I don't know how.
Thanks
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:F6BD45B2-27C2-4E6A-924E-FF9DDA37B970@.microsoft.com...
> In 2005 you do it in the CREATE LOGIN 8or change with ALTER LOGIN)
> command. In 2000, you can't do that.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
>
|||Yes, I know. For SQL Server logins, SQL Server adopts the policies from the
Windows local server that is running the SQL Server. (Windows does its own
managing of Windows login policies.)
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:uvKX38IyHHA.1208@.TK2MSFTNGP03.phx.gbl...
> My sql2005 is sql authentication. so the users are not windows based users
>
> "Russell Fields" <russellfields@.nomail.com> wrote in message
> news:%234wTN0IyHHA.4392@.TK2MSFTNGP04.phx.gbl...
>
|||Did you read about the CREATE LOGIN command in Books Online? If you do, you will find a parameter
which specifies that the Windows policy password expiration policy should apply to this SQL Server
login.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"mecn" <mecn2002@.yahoo.com> wrote in message news:u978YDJyHHA.4928@.TK2MSFTNGP03.phx.gbl...
> Thanks all
> let me say it clearly, I need to enforce sql 2005 sql (authentication) users to change their
> passwords every 30 days.
> Is there a setting or check box that i could fill?
> I don't know how.
> Thanks
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:F6BD45B2-27C2-4E6A-924E-FF9DDA37B970@.microsoft.com...
>
Saturday, February 25, 2012
Password change
Hi,
How do I set up sercurity enforcement to have users change their sql
passwords every 30 days?
Thanksmecn,
SQL Server adopts its policies from the Windows local policies. So, I
believe that you would have to change those.
(But, if your servers are having their policies synchronized with the domain
policies, I don't know if your changes will stick locally.)
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
> Hi,
> How do I set up sercurity enforcement to have users change their sql
> passwords every 30 days?
> Thanks
>|||In 2005 you do it in the CREATE LOGIN 8or change with ALTER LOGIN) command.
In 2000, you can't do
that.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"mecn" <mecn2002@.yahoo.com> wrote in message news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...[v
bcol=seagreen]
> Hi,
> How do I set up sercurity enforcement to have users change their sql
> passwords every 30 days?
> Thanks
>[/vbcol]|||My sql2005 is sql authentication. so the users are not windows based users
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:%234wTN0IyHHA.4392@.TK2MSFTNGP04.phx.gbl...
> mecn,
> SQL Server adopts its policies from the Windows local policies. So, I
> believe that you would have to change those.
> (But, if your servers are having their policies synchronized with the
> domain policies, I don't know if your changes will stick locally.)
> RLF
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
>|||Thanks all
let me say it clearly, I need to enforce sql 2005 sql (authentication) users
to change their passwords every 30 days.
Is there a setting or check box that i could fill?
I don't know how.
Thanks
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:F6BD45B2-27C2-4E6A-924E-FF9DDA37B970@.microsoft.com...
> In 2005 you do it in the CREATE LOGIN 8or change with ALTER LOGIN)
> command. In 2000, you can't do that.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
>|||Yes, I know. For SQL Server logins, SQL Server adopts the policies from the
Windows local server that is running the SQL Server. (Windows does its own
managing of Windows login policies.)
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:uvKX38IyHHA.1208@.TK2MSFTNGP03.phx.gbl...
> My sql2005 is sql authentication. so the users are not windows based users
>
> "Russell Fields" <russellfields@.nomail.com> wrote in message
> news:%234wTN0IyHHA.4392@.TK2MSFTNGP04.phx.gbl...
>|||Did you read about the CREATE LOGIN command in Books Online? If you do, you
will find a parameter
which specifies that the Windows policy password expiration policy should ap
ply to this SQL Server
login.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"mecn" <mecn2002@.yahoo.com> wrote in message news:u978YDJyHHA.4928@.TK2MSFTNGP03.phx.gbl...[v
bcol=seagreen]
> Thanks all
> let me say it clearly, I need to enforce sql 2005 sql (authentication) use
rs to change their
> passwords every 30 days.
> Is there a setting or check box that i could fill?
> I don't know how.
> Thanks
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n message
> news:F6BD45B2-27C2-4E6A-924E-FF9DDA37B970@.microsoft.com...
>[/vbcol]
How do I set up sercurity enforcement to have users change their sql
passwords every 30 days?
Thanksmecn,
SQL Server adopts its policies from the Windows local policies. So, I
believe that you would have to change those.
(But, if your servers are having their policies synchronized with the domain
policies, I don't know if your changes will stick locally.)
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
> Hi,
> How do I set up sercurity enforcement to have users change their sql
> passwords every 30 days?
> Thanks
>|||In 2005 you do it in the CREATE LOGIN 8or change with ALTER LOGIN) command.
In 2000, you can't do
that.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"mecn" <mecn2002@.yahoo.com> wrote in message news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...[v
bcol=seagreen]
> Hi,
> How do I set up sercurity enforcement to have users change their sql
> passwords every 30 days?
> Thanks
>[/vbcol]|||My sql2005 is sql authentication. so the users are not windows based users
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:%234wTN0IyHHA.4392@.TK2MSFTNGP04.phx.gbl...
> mecn,
> SQL Server adopts its policies from the Windows local policies. So, I
> believe that you would have to change those.
> (But, if your servers are having their policies synchronized with the
> domain policies, I don't know if your changes will stick locally.)
> RLF
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
>|||Thanks all
let me say it clearly, I need to enforce sql 2005 sql (authentication) users
to change their passwords every 30 days.
Is there a setting or check box that i could fill?
I don't know how.
Thanks
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:F6BD45B2-27C2-4E6A-924E-FF9DDA37B970@.microsoft.com...
> In 2005 you do it in the CREATE LOGIN 8or change with ALTER LOGIN)
> command. In 2000, you can't do that.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
>|||Yes, I know. For SQL Server logins, SQL Server adopts the policies from the
Windows local server that is running the SQL Server. (Windows does its own
managing of Windows login policies.)
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:uvKX38IyHHA.1208@.TK2MSFTNGP03.phx.gbl...
> My sql2005 is sql authentication. so the users are not windows based users
>
> "Russell Fields" <russellfields@.nomail.com> wrote in message
> news:%234wTN0IyHHA.4392@.TK2MSFTNGP04.phx.gbl...
>|||Did you read about the CREATE LOGIN command in Books Online? If you do, you
will find a parameter
which specifies that the Windows policy password expiration policy should ap
ply to this SQL Server
login.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"mecn" <mecn2002@.yahoo.com> wrote in message news:u978YDJyHHA.4928@.TK2MSFTNGP03.phx.gbl...[v
bcol=seagreen]
> Thanks all
> let me say it clearly, I need to enforce sql 2005 sql (authentication) use
rs to change their
> passwords every 30 days.
> Is there a setting or check box that i could fill?
> I don't know how.
> Thanks
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n message
> news:F6BD45B2-27C2-4E6A-924E-FF9DDA37B970@.microsoft.com...
>[/vbcol]
Password change
Hi,
How do I set up sercurity enforcement to have users change their sql
passwords every 30 days?
Thanksmecn,
SQL Server adopts its policies from the Windows local policies. So, I
believe that you would have to change those.
(But, if your servers are having their policies synchronized with the domain
policies, I don't know if your changes will stick locally.)
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
> Hi,
> How do I set up sercurity enforcement to have users change their sql
> passwords every 30 days?
> Thanks
>|||In 2005 you do it in the CREATE LOGIN 8or change with ALTER LOGIN) command. In 2000, you can't do
that.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"mecn" <mecn2002@.yahoo.com> wrote in message news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
> Hi,
> How do I set up sercurity enforcement to have users change their sql
> passwords every 30 days?
> Thanks
>|||My sql2005 is sql authentication. so the users are not windows based users
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:%234wTN0IyHHA.4392@.TK2MSFTNGP04.phx.gbl...
> mecn,
> SQL Server adopts its policies from the Windows local policies. So, I
> believe that you would have to change those.
> (But, if your servers are having their policies synchronized with the
> domain policies, I don't know if your changes will stick locally.)
> RLF
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
>> Hi,
>> How do I set up sercurity enforcement to have users change their sql
>> passwords every 30 days?
>> Thanks
>>
>|||Thanks all
let me say it clearly, I need to enforce sql 2005 sql (authentication) users
to change their passwords every 30 days.
Is there a setting or check box that i could fill?
I don't know how.
Thanks
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:F6BD45B2-27C2-4E6A-924E-FF9DDA37B970@.microsoft.com...
> In 2005 you do it in the CREATE LOGIN 8or change with ALTER LOGIN)
> command. In 2000, you can't do that.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
>> Hi,
>> How do I set up sercurity enforcement to have users change their sql
>> passwords every 30 days?
>> Thanks
>>
>|||Yes, I know. For SQL Server logins, SQL Server adopts the policies from the
Windows local server that is running the SQL Server. (Windows does its own
managing of Windows login policies.)
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:uvKX38IyHHA.1208@.TK2MSFTNGP03.phx.gbl...
> My sql2005 is sql authentication. so the users are not windows based users
>
> "Russell Fields" <russellfields@.nomail.com> wrote in message
> news:%234wTN0IyHHA.4392@.TK2MSFTNGP04.phx.gbl...
>> mecn,
>> SQL Server adopts its policies from the Windows local policies. So, I
>> believe that you would have to change those.
>> (But, if your servers are having their policies synchronized with the
>> domain policies, I don't know if your changes will stick locally.)
>> RLF
>> "mecn" <mecn2002@.yahoo.com> wrote in message
>> news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
>> Hi,
>> How do I set up sercurity enforcement to have users change their sql
>> passwords every 30 days?
>> Thanks
>>
>>
>|||Did you read about the CREATE LOGIN command in Books Online? If you do, you will find a parameter
which specifies that the Windows policy password expiration policy should apply to this SQL Server
login.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"mecn" <mecn2002@.yahoo.com> wrote in message news:u978YDJyHHA.4928@.TK2MSFTNGP03.phx.gbl...
> Thanks all
> let me say it clearly, I need to enforce sql 2005 sql (authentication) users to change their
> passwords every 30 days.
> Is there a setting or check box that i could fill?
> I don't know how.
> Thanks
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:F6BD45B2-27C2-4E6A-924E-FF9DDA37B970@.microsoft.com...
>> In 2005 you do it in the CREATE LOGIN 8or change with ALTER LOGIN) command. In 2000, you can't do
>> that.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "mecn" <mecn2002@.yahoo.com> wrote in message news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
>> Hi,
>> How do I set up sercurity enforcement to have users change their sql
>> passwords every 30 days?
>> Thanks
>>
>
How do I set up sercurity enforcement to have users change their sql
passwords every 30 days?
Thanksmecn,
SQL Server adopts its policies from the Windows local policies. So, I
believe that you would have to change those.
(But, if your servers are having their policies synchronized with the domain
policies, I don't know if your changes will stick locally.)
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
> Hi,
> How do I set up sercurity enforcement to have users change their sql
> passwords every 30 days?
> Thanks
>|||In 2005 you do it in the CREATE LOGIN 8or change with ALTER LOGIN) command. In 2000, you can't do
that.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"mecn" <mecn2002@.yahoo.com> wrote in message news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
> Hi,
> How do I set up sercurity enforcement to have users change their sql
> passwords every 30 days?
> Thanks
>|||My sql2005 is sql authentication. so the users are not windows based users
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:%234wTN0IyHHA.4392@.TK2MSFTNGP04.phx.gbl...
> mecn,
> SQL Server adopts its policies from the Windows local policies. So, I
> believe that you would have to change those.
> (But, if your servers are having their policies synchronized with the
> domain policies, I don't know if your changes will stick locally.)
> RLF
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
>> Hi,
>> How do I set up sercurity enforcement to have users change their sql
>> passwords every 30 days?
>> Thanks
>>
>|||Thanks all
let me say it clearly, I need to enforce sql 2005 sql (authentication) users
to change their passwords every 30 days.
Is there a setting or check box that i could fill?
I don't know how.
Thanks
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:F6BD45B2-27C2-4E6A-924E-FF9DDA37B970@.microsoft.com...
> In 2005 you do it in the CREATE LOGIN 8or change with ALTER LOGIN)
> command. In 2000, you can't do that.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
>> Hi,
>> How do I set up sercurity enforcement to have users change their sql
>> passwords every 30 days?
>> Thanks
>>
>|||Yes, I know. For SQL Server logins, SQL Server adopts the policies from the
Windows local server that is running the SQL Server. (Windows does its own
managing of Windows login policies.)
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:uvKX38IyHHA.1208@.TK2MSFTNGP03.phx.gbl...
> My sql2005 is sql authentication. so the users are not windows based users
>
> "Russell Fields" <russellfields@.nomail.com> wrote in message
> news:%234wTN0IyHHA.4392@.TK2MSFTNGP04.phx.gbl...
>> mecn,
>> SQL Server adopts its policies from the Windows local policies. So, I
>> believe that you would have to change those.
>> (But, if your servers are having their policies synchronized with the
>> domain policies, I don't know if your changes will stick locally.)
>> RLF
>> "mecn" <mecn2002@.yahoo.com> wrote in message
>> news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
>> Hi,
>> How do I set up sercurity enforcement to have users change their sql
>> passwords every 30 days?
>> Thanks
>>
>>
>|||Did you read about the CREATE LOGIN command in Books Online? If you do, you will find a parameter
which specifies that the Windows policy password expiration policy should apply to this SQL Server
login.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"mecn" <mecn2002@.yahoo.com> wrote in message news:u978YDJyHHA.4928@.TK2MSFTNGP03.phx.gbl...
> Thanks all
> let me say it clearly, I need to enforce sql 2005 sql (authentication) users to change their
> passwords every 30 days.
> Is there a setting or check box that i could fill?
> I don't know how.
> Thanks
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:F6BD45B2-27C2-4E6A-924E-FF9DDA37B970@.microsoft.com...
>> In 2005 you do it in the CREATE LOGIN 8or change with ALTER LOGIN) command. In 2000, you can't do
>> that.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "mecn" <mecn2002@.yahoo.com> wrote in message news:OdDICuIyHHA.5888@.TK2MSFTNGP02.phx.gbl...
>> Hi,
>> How do I set up sercurity enforcement to have users change their sql
>> passwords every 30 days?
>> Thanks
>>
>
Passphrase lost after moving users
I know something like this was addressed before on this forum but I am unable to locate it at all...
Anyone know the solution ?
Problem :
After you move databases to a new server, users may not be able to log in to the new server:
Used DTS ...
Thanks..checkout sp_change_users_login in BOL
sp_change_users_login [ @.Action = ] 'action'
[ , [ @.UserNamePattern = ] 'user' ]
[ , [ @.LoginName = ] 'login' ]
[ , [ @.Password = ] 'password' ]
Anyone know the solution ?
Problem :
After you move databases to a new server, users may not be able to log in to the new server:
Used DTS ...
Thanks..checkout sp_change_users_login in BOL
sp_change_users_login [ @.Action = ] 'action'
[ , [ @.UserNamePattern = ] 'user' ]
[ , [ @.LoginName = ] 'login' ]
[ , [ @.Password = ] 'password' ]
Passing the User ID and AD group as Parameter
Hi...
I have a requirement where I need to pass the Users Windows userID and the AD group through which he is associated to the database so that I can get appropiate data.
Is there a way I can pass the Windows user ID and the AD group(through which he is authenticated in Reporting Serivces) through the Reporting Serivces as a parameter so that it can be used in the Reporting Query.
Thanks,
siaj
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||
As Jens says, UserID is just available using the internal object. For the AD group you should consider writing a custom assembly that performs the operation according to your business rules to decide which is THE group among the ones the user may pertain. I've not checked how difficult it will be to write such code in .Net but sounds not much complicated.
Best regards,Jordi Rambla
MVP SQL Server
SolidQualityLearning|||Hi Siaj,
Were you able to figure this out? I am in need of the same functionality. I undertand .Net has a 'IsInGroup()' function that can check if a user is in a group but I am not sure how it goes...
Thanks,
Ben|||test|||Have you figured this out? I am in the same situation...
Thanks,
Ben
Passing the User ID and AD group as Parameter
Hi...
I have a requirement where I need to pass the Users Windows userID and the AD group through which he is associated to the database so that I can get appropiate data.
Is there a way I can pass the Windows user ID and the AD group(through which he is authenticated in Reporting Serivces) through the Reporting Serivces as a parameter so that it can be used in the Reporting Query.
Thanks,
siaj
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de|||
As Jens says, UserID is just available using the internal object. For the AD group you should consider writing a custom assembly that performs the operation according to your business rules to decide which is THE group among the ones the user may pertain. I've not checked how difficult it will be to write such code in .Net but sounds not much complicated.
Best regards,Jordi Rambla
MVP SQL Server
SolidQualityLearning|||Hi Siaj,
Were you able to figure this out? I am in need of the same functionality. I undertand .Net has a 'IsInGroup()' function that can check if a user is in a group but I am not sure how it goes...
Thanks,
Ben|||test|||Have you figured this out? I am in the same situation...
Thanks,
Ben
Subscribe to:
Posts (Atom)