I have a SQL 2000 (SP3) running on a Windows NT 4.0 (SP6) box used in our test environment. The SQL Server was configured to run under the local system account before I got here. In an effort to standardize things, I tried changing the SQL Service account to run under a designated domain user account purpose built for the job. We use this particular account for all of our new-build servers (which are W2K). This domain account is configured to be a "Power User" on the NT 4.0 Server in question.
Soon after changing things over to run under the new account, all the developers complained that they could no longer connect to the server. I could through QA and EM, but none of the developers could.
The developers are using WebLogic and JDBC drivers for the most part. I wasn't aware that the SQL Server service account affected client connectivity. Was I wrong or is there something else at work here?
Thanks,
hmscottDamn...I'm dealing with something similar right now...
The SSSA run things on behalf of the server...
My guess is that they all connect using sa blank (or whatever, connection pooling id and are still connectiong using sql server auth) and now that it's trusted, their connections are wrong...
How do they connect?
Like when you register a server in EM?
I don't think the service account has anything to do with it...
MOO|||Hi Brett,
They're connecting via various user accounts that are application-specific. Unfortunately, I am only beginning to make progress on convincing management to swing to all trusted connections. The developers insist that WebLogic doesn't support the concept of running under a service account.
Anyway, one guy was using sa, others were using different application accounts. I was able to connect successfully using a trusted connection (but then, I'm a Domain Admin, too, so there's no telling for sure.
It's far from an ideal setup; I'm just trying to correct things bit by bit.
Regards,
Hugh|||Hi Brett,
The developers insist that WebLogic doesn't support the concept of running under a service account.
That may be true...we use websphere and we set a connection pooling account that authenticates through sql server...but it's 1 id and many connections
Anyway, one guy was using sa
Hugh
There's always one...
Still no one is using the SSSA to connect...right?|||No, no one is using that account. I'm sure because the pasword is quite complex and other than being documented in a restricted folder for the DBAs, it's not known.
Thanks for your time...
Regards,
hmscott
Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts
Thursday, March 29, 2012
Sunday, March 25, 2012
Changing the language in the Report Builder interface
Hi @. all,
I work on a german Windows environment and use the Report Builder. For showing details in their it is necessary to switch the German interface in Report Builder into English.
I already tried to change my environment into English but it even after a restart it did not change the Report Builder interface....
I also tried to search all the XML-files for a language setting - with no success....
Does anyone know how to do this? Would be very helpful....!
Thanks in advance,
Jochen
Schliff, in your report click an empty area then go to the properties window and there is a language settings-this allows you to set your language preference.
|||
First: thanks for the answer :-)
Second: it does not work ;-(
Maybe my explanation wasn't precise enough: I'm talking about the Report Builder on the Report Server, which is controlled and used via Internet Explorer....
Are we talking about the same or did I misunderstood something?
Jochen
|||So let me get this..
you have a report, which is published in german but you want to view the published report in english...
if so cant you just go to Tools and Options and select English as the language in IE?
|||Well - that works excellent!
Sometimes solutions are that easy - hard to believe that one does not try these first
Thank you very much, great work....
Jochen
sqlTuesday, March 20, 2012
Changing Table Owner and user Owner
Hello there
I'm using Windows authentication, and i'm suddenly don't member of Dbo
owners.
What i need to change on the server in order so when i create new object
it's written as dbo and not as my name?
after i change that how can i change the owner of tables, views and store
procedures to be dbo owner?
' 03-5611606
' 050-7709399
: roy@.atidsm.co.ilRoy,shalom
Pls read this article from BOL
Database Owner (dbo)
The dbo is a user that has implied permissions to perform all activities in
the database. Any member of the sysadmin fixed server role who uses a
database is mapped to the special user inside each database called dbo.
Also, any object created by any member of the sysadmin fixed server role
belongs to dbo automatically.
For example, if user Andrew is a member of the sysadmin fixed server role
and creates a table T1, T1 belongs to dbo and is qualified as dbo.T1, not as
Andrew.T1. Conversely, if Andrew is not a member of the sysadmin fixed
server role but is a member only of the db_owner fixed database role and
creates a table T1, T1 belongs to Andrew and is qualified as Andrew.T1. The
table belongs to Andrew because he did not qualify the table as dbo.T1.
The dbo user cannot be deleted and is always present in every database.
Only objects created by members of the sysadmin fixed server role (or by the
dbo user) belong to dbo. Objects created by any other user who is not also a
member of the sysadmin fixed server role (including members of the db_owner
fixed database role):
a.. Belong to the user creating the object, not dbo.
b.. Are qualified with the name of the user who created the object.
"Roy Goldhammer" <roy@.hotmail.com> wrote in message
news:OWTo$T54FHA.3188@.TK2MSFTNGP15.phx.gbl...
> Hello there
> I'm using Windows authentication, and i'm suddenly don't member of Dbo
> owners.
> What i need to change on the server in order so when i create new object
> it's written as dbo and not as my name?
> after i change that how can i change the owner of tables, views and store
> procedures to be dbo owner?
> --
>
>
> ' 03-5611606
> ' 050-7709399
> : roy@.atidsm.co.il
>
I'm using Windows authentication, and i'm suddenly don't member of Dbo
owners.
What i need to change on the server in order so when i create new object
it's written as dbo and not as my name?
after i change that how can i change the owner of tables, views and store
procedures to be dbo owner?
' 03-5611606
' 050-7709399
: roy@.atidsm.co.ilRoy,shalom
Pls read this article from BOL
Database Owner (dbo)
The dbo is a user that has implied permissions to perform all activities in
the database. Any member of the sysadmin fixed server role who uses a
database is mapped to the special user inside each database called dbo.
Also, any object created by any member of the sysadmin fixed server role
belongs to dbo automatically.
For example, if user Andrew is a member of the sysadmin fixed server role
and creates a table T1, T1 belongs to dbo and is qualified as dbo.T1, not as
Andrew.T1. Conversely, if Andrew is not a member of the sysadmin fixed
server role but is a member only of the db_owner fixed database role and
creates a table T1, T1 belongs to Andrew and is qualified as Andrew.T1. The
table belongs to Andrew because he did not qualify the table as dbo.T1.
The dbo user cannot be deleted and is always present in every database.
Only objects created by members of the sysadmin fixed server role (or by the
dbo user) belong to dbo. Objects created by any other user who is not also a
member of the sysadmin fixed server role (including members of the db_owner
fixed database role):
a.. Belong to the user creating the object, not dbo.
b.. Are qualified with the name of the user who created the object.
"Roy Goldhammer" <roy@.hotmail.com> wrote in message
news:OWTo$T54FHA.3188@.TK2MSFTNGP15.phx.gbl...
> Hello there
> I'm using Windows authentication, and i'm suddenly don't member of Dbo
> owners.
> What i need to change on the server in order so when i create new object
> it's written as dbo and not as my name?
> after i change that how can i change the owner of tables, views and store
> procedures to be dbo owner?
> --
>
>
> ' 03-5611606
> ' 050-7709399
> : roy@.atidsm.co.il
>
Changing SQL2K port no. on Windows 2003
Hi,
I installed SQL2K SP3a on Windows 2003 server. During the install I changed
the SQL port number 1433 to 14330. Everything finished successfully.
But when the clients are trying to build the ODBC to connect to SQL server,
they cann't connect if they leave the Dynamically determine port check box
checked under the client configuration, but once we unchecked it and put the
port no. 14330 it will connect.
Shouldn't the Dynamically determine port no. option let the client get the
port no from the server? Or is there any security lockdown on Win2003
preventing the server to publish the port no.?
Thanks
AyadThey dynamically determine port only works for named instances. A default
instance will always default to 1433. You can change this but then the
client will always attempt to use port 1433o for every SQL Server it tries
to connect to.
If you choose to use a non-standard port for the default instance, you will
have to have each client change to connect using that port.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I installed SQL2K SP3a on Windows 2003 server. During the install I changed
the SQL port number 1433 to 14330. Everything finished successfully.
But when the clients are trying to build the ODBC to connect to SQL server,
they cann't connect if they leave the Dynamically determine port check box
checked under the client configuration, but once we unchecked it and put the
port no. 14330 it will connect.
Shouldn't the Dynamically determine port no. option let the client get the
port no from the server? Or is there any security lockdown on Win2003
preventing the server to publish the port no.?
Thanks
AyadThey dynamically determine port only works for named instances. A default
instance will always default to 1433. You can change this but then the
client will always attempt to use port 1433o for every SQL Server it tries
to connect to.
If you choose to use a non-standard port for the default instance, you will
have to have each client change to connect using that port.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Changing SQL2K port no. on Windows 2003
Hi,
I installed SQL2K SP3a on Windows 2003 server. During the install I changed
the SQL port number 1433 to 14330. Everything finished successfully.
But when the clients are trying to build the ODBC to connect to SQL server,
they cann't connect if they leave the Dynamically determine port check box
checked under the client configuration, but once we unchecked it and put the
port no. 14330 it will connect.
Shouldn't the Dynamically determine port no. option let the client get the
port no from the server? Or is there any security lockdown on Win2003
preventing the server to publish the port no.?
Thanks
Ayad
They dynamically determine port only works for named instances. A default
instance will always default to 1433. You can change this but then the
client will always attempt to use port 1433o for every SQL Server it tries
to connect to.
If you choose to use a non-standard port for the default instance, you will
have to have each client change to connect using that port.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I installed SQL2K SP3a on Windows 2003 server. During the install I changed
the SQL port number 1433 to 14330. Everything finished successfully.
But when the clients are trying to build the ODBC to connect to SQL server,
they cann't connect if they leave the Dynamically determine port check box
checked under the client configuration, but once we unchecked it and put the
port no. 14330 it will connect.
Shouldn't the Dynamically determine port no. option let the client get the
port no from the server? Or is there any security lockdown on Win2003
preventing the server to publish the port no.?
Thanks
Ayad
They dynamically determine port only works for named instances. A default
instance will always default to 1433. You can change this but then the
client will always attempt to use port 1433o for every SQL Server it tries
to connect to.
If you choose to use a non-standard port for the default instance, you will
have to have each client change to connect using that port.
Rand
This posting is provided "as is" with no warranties and confers no rights.
changing SQL server service account
Guys,
I have got WINDOWS 2000 Advanced Server and MS SQL SERVER 7.0 running on my live server. Now when we are planning for replication, we have found that SQL server will require to run under a domain account. At the moment there are so many ASP pages running on our server accesses different databases created using SQL server 7.0. Most of them are DSN connections to the database. Now if i create a domain account and restart the server and MS SQL services with the domain account, how is it going to effect the current web pages running on it?
Any help will be greatly appreciated.
ThanksA connection to a database has no bearing on what account starts the sql server service. However the account used does affect how the server interacts with other sql servers, or other machine resources, you found that out when you tried to implement replication using LocalSystem account. You can search msdn for "sql server service account" to get a better understanding of the purpose of accounts for sql server.|||Thanks very much Greg,
your reply helped me to have better understanding.
I would find out more from MSDN as you have suggested.
Cheers.
I have got WINDOWS 2000 Advanced Server and MS SQL SERVER 7.0 running on my live server. Now when we are planning for replication, we have found that SQL server will require to run under a domain account. At the moment there are so many ASP pages running on our server accesses different databases created using SQL server 7.0. Most of them are DSN connections to the database. Now if i create a domain account and restart the server and MS SQL services with the domain account, how is it going to effect the current web pages running on it?
Any help will be greatly appreciated.
ThanksA connection to a database has no bearing on what account starts the sql server service. However the account used does affect how the server interacts with other sql servers, or other machine resources, you found that out when you tried to implement replication using LocalSystem account. You can search msdn for "sql server service account" to get a better understanding of the purpose of accounts for sql server.|||Thanks very much Greg,
your reply helped me to have better understanding.
I would find out more from MSDN as you have suggested.
Cheers.
Monday, March 19, 2012
Changing SQL Server Logon Config.
Hello,
When I installed MS SQL Server 2000 on our client's computer I installed it under a local account using Windows Authentication as the server logon and am now accessing it using a network login (remoting into the same box). The result is that if I change the password for the local Windows account and reboot the server, SQL server cannot be restarted; I get an error:
A connection could not be established to (LOCAL)
Reason: SQL SERVER does not exist or access denied.
ConnectionOpen (Connect())..
Please verify SQL Server is running and check your SQL Server registration properties and try again.
I've changed the registration properties to use SQL Server Authenticaiton instead of Windows to no avail. Whichever connection option I use the server will not start unless I change the local account's password back to what it was when I installed. This works, but our client wants to have that local account's password changed for security/peace of mind. Any help or advice would be appreciated here :)
Thank youI always use a dedicated domain account for many reasons. exchange integration, access to file servers etc... and you should set that domain account to never have a password that never expires.|||... and you should set that domain account to never have a password that never expires.I suspect that you might have "over nevered" here. I would want the domain account to have a password that never expired (or I'd create a single application to change the service passwords and the AD password, all in one swell foop).
-PatP|||I'm afraid I don't quite get what you're saying here. The domain login is to stay the same in this case. It is the local account that the sql server installation is tied to that must have its password altered. The problem is that upon altering the password in Windows, SQL server will not start up the instance, giving that invalid logon message. Sorry to say that I'm still at a loss here. :confused:
When I installed MS SQL Server 2000 on our client's computer I installed it under a local account using Windows Authentication as the server logon and am now accessing it using a network login (remoting into the same box). The result is that if I change the password for the local Windows account and reboot the server, SQL server cannot be restarted; I get an error:
A connection could not be established to (LOCAL)
Reason: SQL SERVER does not exist or access denied.
ConnectionOpen (Connect())..
Please verify SQL Server is running and check your SQL Server registration properties and try again.
I've changed the registration properties to use SQL Server Authenticaiton instead of Windows to no avail. Whichever connection option I use the server will not start unless I change the local account's password back to what it was when I installed. This works, but our client wants to have that local account's password changed for security/peace of mind. Any help or advice would be appreciated here :)
Thank youI always use a dedicated domain account for many reasons. exchange integration, access to file servers etc... and you should set that domain account to never have a password that never expires.|||... and you should set that domain account to never have a password that never expires.I suspect that you might have "over nevered" here. I would want the domain account to have a password that never expired (or I'd create a single application to change the service passwords and the AD password, all in one swell foop).
-PatP|||I'm afraid I don't quite get what you're saying here. The domain login is to stay the same in this case. It is the local account that the sql server installation is tied to that must have its password altered. The problem is that upon altering the password in Windows, SQL server will not start up the instance, giving that invalid logon message. Sorry to say that I'm still at a loss here. :confused:
Changing SQL Server configuration in a cluster environment
I running SQL Server on a Windows active passive cluster and need to change
SQL Server configuration. If I change the configuration thru the virtual ser
ver the change is applied to the active node what happens to the passive nod
e? Is it necessary for me t
o failover and apply the change there too?Hi
Most configuration settings are stored in Master, which is shared.
If is recommended to fail over to the other nodes after you make a
configuration change as a test, you don't want to find out weeks down the
line that the failover failed because of a setting that was not identical on
all nodes.
There area a few settings in the registry under
" HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer", especially
" HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer" where
settings like LoginMode, AuditLevel and ListenOn are stored.
Cheers
--
Mike Epprecht, Microsoft SQL Server MVP
Epprecht Consulting (PTY) LTD
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.epprecht.net
Specialist SQL Server Solutions and Consulting
MVP Program: http://www.microsoft.com/mvp
"Jerrick D.H" <JerrickDH@.discussions.microsoft.com> wrote in message
news:301F2959-3BC0-4E96-8F55-838AC4813BA3@.microsoft.com...
> I running SQL Server on a Windows active passive cluster and need to
change SQL Server configuration. If I change the configuration thru the
virtual server the change is applied to the active node what happens to the
passive node? Is it necessary for me to failover and apply the change there
too?|||Your're so right about that.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Most configuration settings are stored in Master, which is shared.
> If is recommended to fail over to the other nodes after you make a
> configuration change as a test, you don't want to find out weeks down the
> line that the failover failed because of a setting that was not identical
on
> all nodes.
> There area a few settings in the registry under
> " HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer", especially
> " HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer" where
> settings like LoginMode, AuditLevel and ListenOn are stored.
> Cheers
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Epprecht Consulting (PTY) LTD
> Johannesburg, South Africa
> Mobile: +27-82-552-0268
> IM: mike@.epprecht.net
> Specialist SQL Server Solutions and Consulting
> MVP Program: http://www.microsoft.com/mvp
> "Jerrick D.H" <JerrickDH@.discussions.microsoft.com> wrote in message
> news:301F2959-3BC0-4E96-8F55-838AC4813BA3@.microsoft.com...
> change SQL Server configuration. If I change the configuration thru the
> virtual server the change is applied to the active node what happens to th
e
> passive node? Is it necessary for me to failover and apply the change ther
e
> too?
>
>
SQL Server configuration. If I change the configuration thru the virtual ser
ver the change is applied to the active node what happens to the passive nod
e? Is it necessary for me t
o failover and apply the change there too?Hi
Most configuration settings are stored in Master, which is shared.
If is recommended to fail over to the other nodes after you make a
configuration change as a test, you don't want to find out weeks down the
line that the failover failed because of a setting that was not identical on
all nodes.
There area a few settings in the registry under
" HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer", especially
" HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer" where
settings like LoginMode, AuditLevel and ListenOn are stored.
Cheers
--
Mike Epprecht, Microsoft SQL Server MVP
Epprecht Consulting (PTY) LTD
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.epprecht.net
Specialist SQL Server Solutions and Consulting
MVP Program: http://www.microsoft.com/mvp
"Jerrick D.H" <JerrickDH@.discussions.microsoft.com> wrote in message
news:301F2959-3BC0-4E96-8F55-838AC4813BA3@.microsoft.com...
> I running SQL Server on a Windows active passive cluster and need to
change SQL Server configuration. If I change the configuration thru the
virtual server the change is applied to the active node what happens to the
passive node? Is it necessary for me to failover and apply the change there
too?|||Your're so right about that.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Most configuration settings are stored in Master, which is shared.
> If is recommended to fail over to the other nodes after you make a
> configuration change as a test, you don't want to find out weeks down the
> line that the failover failed because of a setting that was not identical
on
> all nodes.
> There area a few settings in the registry under
> " HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer", especially
> " HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer" where
> settings like LoginMode, AuditLevel and ListenOn are stored.
> Cheers
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Epprecht Consulting (PTY) LTD
> Johannesburg, South Africa
> Mobile: +27-82-552-0268
> IM: mike@.epprecht.net
> Specialist SQL Server Solutions and Consulting
> MVP Program: http://www.microsoft.com/mvp
> "Jerrick D.H" <JerrickDH@.discussions.microsoft.com> wrote in message
> news:301F2959-3BC0-4E96-8F55-838AC4813BA3@.microsoft.com...
> change SQL Server configuration. If I change the configuration thru the
> virtual server the change is applied to the active node what happens to th
e
> passive node? Is it necessary for me to failover and apply the change ther
e
> too?
>
>
Changing SQL Server configuration in a cluster environment
I running SQL Server on a Windows active passive cluster and need to change SQL Server configuration. If I change the configuration thru the virtual server the change is applied to the active node what happens to the passive node? Is it necessary for me t
o failover and apply the change there too?
Hi
Most configuration settings are stored in Master, which is shared.
If is recommended to fail over to the other nodes after you make a
configuration change as a test, you don't want to find out weeks down the
line that the failover failed because of a setting that was not identical on
all nodes.
There area a few settings in the registry under
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer ", especially
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer \MSSQLServer" where
settings like LoginMode, AuditLevel and ListenOn are stored.
Cheers
--
Mike Epprecht, Microsoft SQL Server MVP
Epprecht Consulting (PTY) LTD
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.epprecht.net
Specialist SQL Server Solutions and Consulting
MVP Program: http://www.microsoft.com/mvp
"Jerrick D.H" <JerrickDH@.discussions.microsoft.com> wrote in message
news:301F2959-3BC0-4E96-8F55-838AC4813BA3@.microsoft.com...
> I running SQL Server on a Windows active passive cluster and need to
change SQL Server configuration. If I change the configuration thru the
virtual server the change is applied to the active node what happens to the
passive node? Is it necessary for me to failover and apply the change there
too?
|||Your're so right about that.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Most configuration settings are stored in Master, which is shared.
> If is recommended to fail over to the other nodes after you make a
> configuration change as a test, you don't want to find out weeks down the
> line that the failover failed because of a setting that was not identical on
> all nodes.
> There area a few settings in the registry under
> "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer ", especially
> "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer \MSSQLServer" where
> settings like LoginMode, AuditLevel and ListenOn are stored.
> Cheers
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Epprecht Consulting (PTY) LTD
> Johannesburg, South Africa
> Mobile: +27-82-552-0268
> IM: mike@.epprecht.net
> Specialist SQL Server Solutions and Consulting
> MVP Program: http://www.microsoft.com/mvp
> "Jerrick D.H" <JerrickDH@.discussions.microsoft.com> wrote in message
> news:301F2959-3BC0-4E96-8F55-838AC4813BA3@.microsoft.com...
> change SQL Server configuration. If I change the configuration thru the
> virtual server the change is applied to the active node what happens to the
> passive node? Is it necessary for me to failover and apply the change there
> too?
>
>
o failover and apply the change there too?
Hi
Most configuration settings are stored in Master, which is shared.
If is recommended to fail over to the other nodes after you make a
configuration change as a test, you don't want to find out weeks down the
line that the failover failed because of a setting that was not identical on
all nodes.
There area a few settings in the registry under
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer ", especially
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer \MSSQLServer" where
settings like LoginMode, AuditLevel and ListenOn are stored.
Cheers
--
Mike Epprecht, Microsoft SQL Server MVP
Epprecht Consulting (PTY) LTD
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.epprecht.net
Specialist SQL Server Solutions and Consulting
MVP Program: http://www.microsoft.com/mvp
"Jerrick D.H" <JerrickDH@.discussions.microsoft.com> wrote in message
news:301F2959-3BC0-4E96-8F55-838AC4813BA3@.microsoft.com...
> I running SQL Server on a Windows active passive cluster and need to
change SQL Server configuration. If I change the configuration thru the
virtual server the change is applied to the active node what happens to the
passive node? Is it necessary for me to failover and apply the change there
too?
|||Your're so right about that.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Most configuration settings are stored in Master, which is shared.
> If is recommended to fail over to the other nodes after you make a
> configuration change as a test, you don't want to find out weeks down the
> line that the failover failed because of a setting that was not identical on
> all nodes.
> There area a few settings in the registry under
> "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer ", especially
> "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer \MSSQLServer" where
> settings like LoginMode, AuditLevel and ListenOn are stored.
> Cheers
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Epprecht Consulting (PTY) LTD
> Johannesburg, South Africa
> Mobile: +27-82-552-0268
> IM: mike@.epprecht.net
> Specialist SQL Server Solutions and Consulting
> MVP Program: http://www.microsoft.com/mvp
> "Jerrick D.H" <JerrickDH@.discussions.microsoft.com> wrote in message
> news:301F2959-3BC0-4E96-8F55-838AC4813BA3@.microsoft.com...
> change SQL Server configuration. If I change the configuration thru the
> virtual server the change is applied to the active node what happens to the
> passive node? Is it necessary for me to failover and apply the change there
> too?
>
>
Changing SQL authentication method
Have a central SQL box (SQL server 2000 SP3a) which serves
requests from web servers. It is configured to use Windows
authentication. However I have a requirement for another
web server to use SQL authentication. Would I be able to
change the SQl Server's configuration to SQL and Windows
without breaking anything?
Many thanksOn Wed, 11 Aug 2004 01:45:08 -0700, Gary wrote:
>Have a central SQL box (SQL server 2000 SP3a) which serves
>requests from web servers. It is configured to use Windows
>authentication. However I have a requirement for another
>web server to use SQL authentication. Would I be able to
>change the SQl Server's configuration to SQL and Windows
>without breaking anything?
>Many thanks
Hi Gary,
Yes, this is possible. You can make this change through Enterprise
Manager: right-click the server, select Properties and on the Security
tab, set the required authentication mode.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||Hi,
There will not be any impact in changing the authentication. Only thing is,
you need to stop and start the MSSQL server service
to make the changes (Mixed authentication) active.
Thanks
Hari
MCDBA
"Gary" <anonymous@.discussions.microsoft.com> wrote in message
news:3be701c47f7f$817996e0$a301280a@.phx.gbl...
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Hi chaps
Thanks for the advice - thought as much, I'll give it a
whirl.
Gary|||Gary,
Make sure the sa password is strong before doing this, as people will be
able to attempt to login with it now, and possibly even attempt a brute
force crack. Apart from that, should be OK.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gary wrote:
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Hi Mark
Again thanks for the advice. The sa password has already
been set during service pack 3a installation and is strong.
Gary
requests from web servers. It is configured to use Windows
authentication. However I have a requirement for another
web server to use SQL authentication. Would I be able to
change the SQl Server's configuration to SQL and Windows
without breaking anything?
Many thanksOn Wed, 11 Aug 2004 01:45:08 -0700, Gary wrote:
>Have a central SQL box (SQL server 2000 SP3a) which serves
>requests from web servers. It is configured to use Windows
>authentication. However I have a requirement for another
>web server to use SQL authentication. Would I be able to
>change the SQl Server's configuration to SQL and Windows
>without breaking anything?
>Many thanks
Hi Gary,
Yes, this is possible. You can make this change through Enterprise
Manager: right-click the server, select Properties and on the Security
tab, set the required authentication mode.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||Hi,
There will not be any impact in changing the authentication. Only thing is,
you need to stop and start the MSSQL server service
to make the changes (Mixed authentication) active.
Thanks
Hari
MCDBA
"Gary" <anonymous@.discussions.microsoft.com> wrote in message
news:3be701c47f7f$817996e0$a301280a@.phx.gbl...
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Hi chaps
Thanks for the advice - thought as much, I'll give it a
whirl.
Gary|||Gary,
Make sure the sa password is strong before doing this, as people will be
able to attempt to login with it now, and possibly even attempt a brute
force crack. Apart from that, should be OK.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gary wrote:
> Have a central SQL box (SQL server 2000 SP3a) which serves
> requests from web servers. It is configured to use Windows
> authentication. However I have a requirement for another
> web server to use SQL authentication. Would I be able to
> change the SQl Server's configuration to SQL and Windows
> without breaking anything?
> Many thanks|||Hi Mark
Again thanks for the advice. The sa password has already
been set during service pack 3a installation and is strong.
Gary
Sunday, March 11, 2012
Changing Security to Windows Authentications from sql login
Hi
I have around 300+ DTS packages, with most of the have been created by users
with SQL Login information.
MY company is now moving to Windows Authentication.
There two places where we can put SQL Login information in DTS Packages.
1. When you create new connection in DTS for SQL Server.
2. When you save DTS packages...
I have posted the same in DTS group also.
It is lots of manual work to change all the dts packages to windows authenti
catiosn.
Is there any simple and automatic way to change all the connections to use w
indows authentications...'?
Appreciate your help.
Thanks
JPUsing SQL DMO you can do anything. Infact the whole SQL Enterprise Manager
uses DMO object to show you what you see.
If you can create a lil application, use SQL DMO, iterate thru DTS packages
and modify their properties.
Read more about SQL DMO !
"JP" <anonymous@.discussions.microsoft.com> wrote in message
news:B8F6BF05-533D-4C8B-8D83-3958B0D24165@.microsoft.com...
> Hi
> I have around 300+ DTS packages, with most of the have been created by
users with SQL Login information.
> MY company is now moving to Windows Authentication.
> There two places where we can put SQL Login information in DTS Packages.
> 1. When you create new connection in DTS for SQL Server.
> 2. When you save DTS packages...
> I have posted the same in DTS group also.
> It is lots of manual work to change all the dts packages to windows
authenticatiosn.
> Is there any simple and automatic way to change all the connections to use
windows authentications...'?
> Appreciate your help.
> Thanks
> JP
>
I have around 300+ DTS packages, with most of the have been created by users
with SQL Login information.
MY company is now moving to Windows Authentication.
There two places where we can put SQL Login information in DTS Packages.
1. When you create new connection in DTS for SQL Server.
2. When you save DTS packages...
I have posted the same in DTS group also.
It is lots of manual work to change all the dts packages to windows authenti
catiosn.
Is there any simple and automatic way to change all the connections to use w
indows authentications...'?
Appreciate your help.
Thanks
JPUsing SQL DMO you can do anything. Infact the whole SQL Enterprise Manager
uses DMO object to show you what you see.
If you can create a lil application, use SQL DMO, iterate thru DTS packages
and modify their properties.
Read more about SQL DMO !
"JP" <anonymous@.discussions.microsoft.com> wrote in message
news:B8F6BF05-533D-4C8B-8D83-3958B0D24165@.microsoft.com...
> Hi
> I have around 300+ DTS packages, with most of the have been created by
users with SQL Login information.
> MY company is now moving to Windows Authentication.
> There two places where we can put SQL Login information in DTS Packages.
> 1. When you create new connection in DTS for SQL Server.
> 2. When you save DTS packages...
> I have posted the same in DTS group also.
> It is lots of manual work to change all the dts packages to windows
authenticatiosn.
> Is there any simple and automatic way to change all the connections to use
windows authentications...'?
> Appreciate your help.
> Thanks
> JP
>
changing security model
how do i reconfigure an installed sql server to use standard security
(sql login/pwd) instead of only accepting trusted connections
(requiring windows login/pwd)
thanks,
jasonnever mind, i found it in the enterprise manager server properties
security tab.
(sql login/pwd) instead of only accepting trusted connections
(requiring windows login/pwd)
thanks,
jasonnever mind, i found it in the enterprise manager server properties
security tab.
Changing security authentication type.
Hi,
in an existing instance of SQL, will changing the security authentication
from SQL & Windows logins, to only windows logins cause any issues?
Also, if a database has been created with hardly any security already, are
there any issues with introducing security further down the line. For
example, a SQL server has been deployed already by my predecessor, with
authentication in SA & windows mode, and allowing pretty much anyone access
to SQL. If i was to create a DBA_Admin group and assign admin writes only to
that group, will it cause any problems in a already functioning database?
TIAInline...
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Stu" <stu@.blah.com> wrote in message
news:%23E25Hpb1GHA.1252@.TK2MSFTNGP04.phx.gbl...
> Hi,
> in an existing instance of SQL, will changing the security authentication
> from SQL & Windows logins, to only windows logins cause any issues?
>
It will block (lock out) any attempts to access the database using the sa
account (or any other SQL Login).
> Also, if a database has been created with hardly any security already, are
> there any issues with introducing security further down the line. For
There 'could' be substaintial disruption when you introduce security.
Consider a building where there were no keys necessary to enter the building
and the rooms, and suddenly keys were required to enter the building, and
also to enter rooms. Until everyone got all of the correct keys for their
needs, there would be major disruption. However, if this was a well planned
process, and appropraite keys were distributed before all the locks were
install, the disruption would be minimal if at all.
> example, a SQL server has been deployed already by my predecessor, with
> authentication in SA & windows mode, and allowing pretty much anyone
> access to SQL. If i was to create a DBA_Admin group and assign admin
> writes only to that group, will it cause any problems in a already
> functioning database?
Creating a domain/DBA_Admin group, providing that group login access to the
server, and also placing that group in the sysadmin server role, will not
cause any problems in a functioning database.
The problems will occur as you start locking down and removing permissions
from the sa account. And you 'should' do that. Applications should not be
using the sa account for database access since the sa account can do
'anything' with and to the server.
> TIA
>|||ok, many thanks for the reply.
So in short you're saying to keep the "mixed" authentication, but to secure
the server down, the best path to take is to create an AD DBA group, and
configure key users to be in that group?
furthermore, to leave the sa account's permissions well alone!
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:%23tasa7b1GHA.480@.TK2MSFTNGP06.phx.gbl...
> Inline...
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Stu" <stu@.blah.com> wrote in message
> news:%23E25Hpb1GHA.1252@.TK2MSFTNGP04.phx.gbl...
> It will block (lock out) any attempts to access the database using the sa
> account (or any other SQL Login).
>
>
> There 'could' be substaintial disruption when you introduce security.
> Consider a building where there were no keys necessary to enter the
> building and the rooms, and suddenly keys were required to enter the
> building, and also to enter rooms. Until everyone got all of the correct
> keys for their needs, there would be major disruption. However, if this
> was a well planned process, and appropraite keys were distributed before
> all the locks were install, the disruption would be minimal if at all.
>
> Creating a domain/DBA_Admin group, providing that group login access to
> the server, and also placing that group in the sysadmin server role, will
> not cause any problems in a functioning database.
> The problems will occur as you start locking down and removing permissions
> from the sa account. And you 'should' do that. Applications should not be
> using the sa account for database access since the sa account can do
> 'anything' with and to the server.
>
>|||Actually, I recommend that you take a deliberative approach to removing all
usage of the sa account, possibly with the eventual goal of switching to
Windows authentication.
Your first steps, however, are to determine the impact on the applications
of changing the connection strings. For some applications, that will be
relatively easy, for others, a re-deploy may be required and that will take
some time, effort and coordination.
Create one or more logins for the applications. Create one or more roles for
each database. Give those roles access to the appropriate databases. give
those roles permissions to the tables, views, stored procedures and
functions required by the applications. Place the logins in the new roles.
DO NOT put these logins in the sysadmin role.
Change the connections strings for the applications to use the new logins.
You want to eventually remove any application usage of the sa account.
This is a goal, it may take some time to eventually put it into place.
But for now, take no action to change the sa account -until you understand
the implications, and have a plan to addresses any issues.
However, as long as the sa account password is readily known by developers
(and whomever else may know it), you really have no security for your
database. (And if the application is hacked, the hackers will have admin
privileges in the database.)
There may be other regulatory reasons that you need to tighten up the
security, i.e., HIPPA, SarBox, etc. The usage of the sa account will most
likely be flagged as a security audit failure.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Stu" <stu@.blah.com> wrote in message
news:uSCBYwc1GHA.4648@.TK2MSFTNGP04.phx.gbl...
> ok, many thanks for the reply.
> So in short you're saying to keep the "mixed" authentication, but to
> secure the server down, the best path to take is to create an AD DBA
> group, and configure key users to be in that group?
> furthermore, to leave the sa account's permissions well alone!
>
> "Arnie Rowland" <arnie@.1568.com> wrote in message
> news:%23tasa7b1GHA.480@.TK2MSFTNGP06.phx.gbl...
>|||Many thanks for your advice to date Arnie. Could i just run some more
questions past the group.
After reading your reply, i'm thinking that yes in time the sa account will
be withdrawn from use.
I'm just trying to get my head around a plan of attack on how it will take
place.
The first step i want to take is to create a group for suitable DBA's to
administer the server.
I'm guessing that i'm also going to have to create a DBA Admin user, which
will effectively take the place of the SA account, which will not as you
mention be a member of the sysadmin group / role.
Is the switch over just as easy as selecting the windows authentication
radio button?
if so, if the changeover is made, if things go wrong, will the role back be
to retick mixed mode or would the initial changeover be not possible to
reverse?
also what changes will need to be done to the individual databases, just
changing the connection strings?
once again, thanks for any further advice.
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:%23LVeCAd1GHA.4116@.TK2MSFTNGP02.phx.gbl...
> Actually, I recommend that you take a deliberative approach to removing
> all usage of the sa account, possibly with the eventual goal of switching
> to Windows authentication.
> Your first steps, however, are to determine the impact on the applications
> of changing the connection strings. For some applications, that will be
> relatively easy, for others, a re-deploy may be required and that will
> take some time, effort and coordination.
> Create one or more logins for the applications. Create one or more roles
> for each database. Give those roles access to the appropriate databases.
> give those roles permissions to the tables, views, stored procedures and
> functions required by the applications. Place the logins in the new roles.
> DO NOT put these logins in the sysadmin role.
> Change the connections strings for the applications to use the new logins.
> You want to eventually remove any application usage of the sa account.
> This is a goal, it may take some time to eventually put it into place.
> But for now, take no action to change the sa account -until you understand
> the implications, and have a plan to addresses any issues.
> However, as long as the sa account password is readily known by developers
> (and whomever else may know it), you really have no security for your
> database. (And if the application is hacked, the hackers will have admin
> privileges in the database.)
> There may be other regulatory reasons that you need to tighten up the
> security, i.e., HIPPA, SarBox, etc. The usage of the sa account will most
> likely be flagged as a security audit failure.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Stu" <stu@.blah.com> wrote in message
> news:uSCBYwc1GHA.4648@.TK2MSFTNGP04.phx.gbl...
>|||Inline...
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Stu" <stu@.blah.com> wrote in message
news:uZXUeon1GHA.3908@.TK2MSFTNGP05.phx.gbl...
> Many thanks for your advice to date Arnie. Could i just run some more
> questions past the group.
> After reading your reply, i'm thinking that yes in time the sa account
> will be withdrawn from use.
> I'm just trying to get my head around a plan of attack on how it will take
> place.
> The first step i want to take is to create a group for suitable DBA's to
> administer the server.
> I'm guessing that i'm also going to have to create a DBA Admin user, which
> will effectively take the place of the SA account, which will not as you
> mention be a member of the sysadmin group / role.
>
A new DBA Admin User login would only be useful for SQL Login purposes.
You're moving away from SQL Logins.
It may be useful to create a domain group that contains those appointed to
be the SQL Administrators. You can then assign that domain group to the
[sysadmin] role in the server. Anyone that is a SQL Administrator must b
e in
the sysadmin role. (It has the same 'power' as [sa], but the security yo
u
are moving toward is that a user must have their own domain account/password
in order to get into the server, and then if they are in the sysadmin role
they are allowed administrator priviledges. If you cannot create (or have
created) a domain group, then you could add each prospective administrator's
domain/username to the sysadmin role.
Also, if appropriate you can add users to the db_owner role in a database.
That role allows complete control of a database, create tables, etc., BUT
does not allow similar control for other databases on the same server. This
can be good for developers when a database is in development, and then
removed from developers when the database goes into production.
> Is the switch over just as easy as selecting the windows authentication
> radio button?
> if so, if the changeover is made, if things go wrong, will the role back
> be to retick mixed mode or would the initial changeover be not possible to
> reverse?
Yes, you can check the button for Windows Authentication, and if things
break, click on SQL Authentication to return it back to mixed mode. -It will
take a few seconds as the server has to stop/restart.
> also what changes will need to be done to the individual databases, just
> changing the connection strings?
>
Each application will have to have it's connection strings changed to allow
for the new security model. BUT first, you will have created a database role
for the application users, and added the domain groups/accounts to that
role.
It will also be necessary to go through each database and provide
appropriate permissions to that role for Tables, Views, Stored Procedures,
Functions.
Different applications that have their own databases 'should' each have a
distinct database role, so that a user in permissions in one database cannot
inadvertently access data in another database.
> once again, thanks for any further advice.
No problem.
For a good introduction into SQL Server security, see if you can find a copy
of Morris Lewis' book, SQL Server Security Distilled, ISBN 1-9043-47-07-X
http://www.abebooks.com/servlet/Boo...isbn=190434707X
>
> "Arnie Rowland" <arnie@.1568.com> wrote in message
> news:%23LVeCAd1GHA.4116@.TK2MSFTNGP02.phx.gbl...
>
in an existing instance of SQL, will changing the security authentication
from SQL & Windows logins, to only windows logins cause any issues?
Also, if a database has been created with hardly any security already, are
there any issues with introducing security further down the line. For
example, a SQL server has been deployed already by my predecessor, with
authentication in SA & windows mode, and allowing pretty much anyone access
to SQL. If i was to create a DBA_Admin group and assign admin writes only to
that group, will it cause any problems in a already functioning database?
TIAInline...
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Stu" <stu@.blah.com> wrote in message
news:%23E25Hpb1GHA.1252@.TK2MSFTNGP04.phx.gbl...
> Hi,
> in an existing instance of SQL, will changing the security authentication
> from SQL & Windows logins, to only windows logins cause any issues?
>
It will block (lock out) any attempts to access the database using the sa
account (or any other SQL Login).
> Also, if a database has been created with hardly any security already, are
> there any issues with introducing security further down the line. For
There 'could' be substaintial disruption when you introduce security.
Consider a building where there were no keys necessary to enter the building
and the rooms, and suddenly keys were required to enter the building, and
also to enter rooms. Until everyone got all of the correct keys for their
needs, there would be major disruption. However, if this was a well planned
process, and appropraite keys were distributed before all the locks were
install, the disruption would be minimal if at all.
> example, a SQL server has been deployed already by my predecessor, with
> authentication in SA & windows mode, and allowing pretty much anyone
> access to SQL. If i was to create a DBA_Admin group and assign admin
> writes only to that group, will it cause any problems in a already
> functioning database?
Creating a domain/DBA_Admin group, providing that group login access to the
server, and also placing that group in the sysadmin server role, will not
cause any problems in a functioning database.
The problems will occur as you start locking down and removing permissions
from the sa account. And you 'should' do that. Applications should not be
using the sa account for database access since the sa account can do
'anything' with and to the server.
> TIA
>|||ok, many thanks for the reply.
So in short you're saying to keep the "mixed" authentication, but to secure
the server down, the best path to take is to create an AD DBA group, and
configure key users to be in that group?
furthermore, to leave the sa account's permissions well alone!
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:%23tasa7b1GHA.480@.TK2MSFTNGP06.phx.gbl...
> Inline...
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Stu" <stu@.blah.com> wrote in message
> news:%23E25Hpb1GHA.1252@.TK2MSFTNGP04.phx.gbl...
> It will block (lock out) any attempts to access the database using the sa
> account (or any other SQL Login).
>
>
> There 'could' be substaintial disruption when you introduce security.
> Consider a building where there were no keys necessary to enter the
> building and the rooms, and suddenly keys were required to enter the
> building, and also to enter rooms. Until everyone got all of the correct
> keys for their needs, there would be major disruption. However, if this
> was a well planned process, and appropraite keys were distributed before
> all the locks were install, the disruption would be minimal if at all.
>
> Creating a domain/DBA_Admin group, providing that group login access to
> the server, and also placing that group in the sysadmin server role, will
> not cause any problems in a functioning database.
> The problems will occur as you start locking down and removing permissions
> from the sa account. And you 'should' do that. Applications should not be
> using the sa account for database access since the sa account can do
> 'anything' with and to the server.
>
>|||Actually, I recommend that you take a deliberative approach to removing all
usage of the sa account, possibly with the eventual goal of switching to
Windows authentication.
Your first steps, however, are to determine the impact on the applications
of changing the connection strings. For some applications, that will be
relatively easy, for others, a re-deploy may be required and that will take
some time, effort and coordination.
Create one or more logins for the applications. Create one or more roles for
each database. Give those roles access to the appropriate databases. give
those roles permissions to the tables, views, stored procedures and
functions required by the applications. Place the logins in the new roles.
DO NOT put these logins in the sysadmin role.
Change the connections strings for the applications to use the new logins.
You want to eventually remove any application usage of the sa account.
This is a goal, it may take some time to eventually put it into place.
But for now, take no action to change the sa account -until you understand
the implications, and have a plan to addresses any issues.
However, as long as the sa account password is readily known by developers
(and whomever else may know it), you really have no security for your
database. (And if the application is hacked, the hackers will have admin
privileges in the database.)
There may be other regulatory reasons that you need to tighten up the
security, i.e., HIPPA, SarBox, etc. The usage of the sa account will most
likely be flagged as a security audit failure.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Stu" <stu@.blah.com> wrote in message
news:uSCBYwc1GHA.4648@.TK2MSFTNGP04.phx.gbl...
> ok, many thanks for the reply.
> So in short you're saying to keep the "mixed" authentication, but to
> secure the server down, the best path to take is to create an AD DBA
> group, and configure key users to be in that group?
> furthermore, to leave the sa account's permissions well alone!
>
> "Arnie Rowland" <arnie@.1568.com> wrote in message
> news:%23tasa7b1GHA.480@.TK2MSFTNGP06.phx.gbl...
>|||Many thanks for your advice to date Arnie. Could i just run some more
questions past the group.
After reading your reply, i'm thinking that yes in time the sa account will
be withdrawn from use.
I'm just trying to get my head around a plan of attack on how it will take
place.
The first step i want to take is to create a group for suitable DBA's to
administer the server.
I'm guessing that i'm also going to have to create a DBA Admin user, which
will effectively take the place of the SA account, which will not as you
mention be a member of the sysadmin group / role.
Is the switch over just as easy as selecting the windows authentication
radio button?
if so, if the changeover is made, if things go wrong, will the role back be
to retick mixed mode or would the initial changeover be not possible to
reverse?
also what changes will need to be done to the individual databases, just
changing the connection strings?
once again, thanks for any further advice.
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:%23LVeCAd1GHA.4116@.TK2MSFTNGP02.phx.gbl...
> Actually, I recommend that you take a deliberative approach to removing
> all usage of the sa account, possibly with the eventual goal of switching
> to Windows authentication.
> Your first steps, however, are to determine the impact on the applications
> of changing the connection strings. For some applications, that will be
> relatively easy, for others, a re-deploy may be required and that will
> take some time, effort and coordination.
> Create one or more logins for the applications. Create one or more roles
> for each database. Give those roles access to the appropriate databases.
> give those roles permissions to the tables, views, stored procedures and
> functions required by the applications. Place the logins in the new roles.
> DO NOT put these logins in the sysadmin role.
> Change the connections strings for the applications to use the new logins.
> You want to eventually remove any application usage of the sa account.
> This is a goal, it may take some time to eventually put it into place.
> But for now, take no action to change the sa account -until you understand
> the implications, and have a plan to addresses any issues.
> However, as long as the sa account password is readily known by developers
> (and whomever else may know it), you really have no security for your
> database. (And if the application is hacked, the hackers will have admin
> privileges in the database.)
> There may be other regulatory reasons that you need to tighten up the
> security, i.e., HIPPA, SarBox, etc. The usage of the sa account will most
> likely be flagged as a security audit failure.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Stu" <stu@.blah.com> wrote in message
> news:uSCBYwc1GHA.4648@.TK2MSFTNGP04.phx.gbl...
>|||Inline...
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Stu" <stu@.blah.com> wrote in message
news:uZXUeon1GHA.3908@.TK2MSFTNGP05.phx.gbl...
> Many thanks for your advice to date Arnie. Could i just run some more
> questions past the group.
> After reading your reply, i'm thinking that yes in time the sa account
> will be withdrawn from use.
> I'm just trying to get my head around a plan of attack on how it will take
> place.
> The first step i want to take is to create a group for suitable DBA's to
> administer the server.
> I'm guessing that i'm also going to have to create a DBA Admin user, which
> will effectively take the place of the SA account, which will not as you
> mention be a member of the sysadmin group / role.
>
A new DBA Admin User login would only be useful for SQL Login purposes.
You're moving away from SQL Logins.
It may be useful to create a domain group that contains those appointed to
be the SQL Administrators. You can then assign that domain group to the
[sysadmin] role in the server. Anyone that is a SQL Administrator must b
e in
the sysadmin role. (It has the same 'power' as [sa], but the security yo
u
are moving toward is that a user must have their own domain account/password
in order to get into the server, and then if they are in the sysadmin role
they are allowed administrator priviledges. If you cannot create (or have
created) a domain group, then you could add each prospective administrator's
domain/username to the sysadmin role.
Also, if appropriate you can add users to the db_owner role in a database.
That role allows complete control of a database, create tables, etc., BUT
does not allow similar control for other databases on the same server. This
can be good for developers when a database is in development, and then
removed from developers when the database goes into production.
> Is the switch over just as easy as selecting the windows authentication
> radio button?
> if so, if the changeover is made, if things go wrong, will the role back
> be to retick mixed mode or would the initial changeover be not possible to
> reverse?
Yes, you can check the button for Windows Authentication, and if things
break, click on SQL Authentication to return it back to mixed mode. -It will
take a few seconds as the server has to stop/restart.
> also what changes will need to be done to the individual databases, just
> changing the connection strings?
>
Each application will have to have it's connection strings changed to allow
for the new security model. BUT first, you will have created a database role
for the application users, and added the domain groups/accounts to that
role.
It will also be necessary to go through each database and provide
appropriate permissions to that role for Tables, Views, Stored Procedures,
Functions.
Different applications that have their own databases 'should' each have a
distinct database role, so that a user in permissions in one database cannot
inadvertently access data in another database.
> once again, thanks for any further advice.
No problem.
For a good introduction into SQL Server security, see if you can find a copy
of Morris Lewis' book, SQL Server Security Distilled, ISBN 1-9043-47-07-X
http://www.abebooks.com/servlet/Boo...isbn=190434707X
>
> "Arnie Rowland" <arnie@.1568.com> wrote in message
> news:%23LVeCAd1GHA.4116@.TK2MSFTNGP02.phx.gbl...
>
Thursday, March 8, 2012
Changing sa password
Hi All,
I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
data bases on this server & the authentication type is mixed. I would like to
know what are the implications if I change the sa password. Also would like
to know what all the precautions to be taken to do so.
With Regards,
Ovin
Have a look at sp_password?
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
6
> data bases on this server & the authentication type is mixed. I would like
to
> know what are the implications if I change the sa password. Also would
like
> to know what all the precautions to be taken to do so.
> With Regards,
>
|||Hi,
There is no implications in changing the SA password. THe only thing is
check in your application for any hard coded password for sa.
If it is not there then you could change the password for SA.
Note: It is not recommended to use SA password from application. If used
create a new login with DB_owner prev. and access the application.
Thanks
Hari
SQL Server MVP
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
> 6
> data bases on this server & the authentication type is mixed. I would like
> to
> know what are the implications if I change the sa password. Also would
> like
> to know what all the precautions to be taken to do so.
> With Regards,
>
|||In SQL Server 6.5 and earlier, many tasks could only be down as the actual sa
and Windows Network Authenticated system administrators were actually mapped,
aliased, as the sa.
However, since SQL Server 7.0, the creation of the system roles removed this
rectriction. Any login, SQL Server Autenticate or Windows Authenticated, who
is also a member of the system_administrators system role will have the EXACT
same permissions as the sa account itself. The security issue here is that
EVERYONE knows that the sa account exists; thus, this is a huge security hole.
It is not only a good idea to reset this password but to do it often and
make it as complex as possible.
As far as the impact to the system is concerned, it should not as long as no
applications are using them. If you are the application developer, you
should know whether or not you are using this account and switch the
application's login to something else if it is. If you are but a lowly DBA,
you may not know, not have access, or be supporting ill-coded vendor
applications. Regardless, you can use the SQL Server Profiler and audit for
the sa account login. You will have to filter out legitamate system
operations that typically will use the sa account also. How long you run
this audit depends on the nature of the applications support but one work day
to a business week should be enough to identify those systems that may be
using this account.
If all else fails, you can extract out the encrypted password if you do not
already know it, and be prepared to reset the account's password to its
original if issues arise.
Sincerely,
Anthony Thomas
"Ovin Crasta" wrote:
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
> data bases on this server & the authentication type is mixed. I would like to
> know what are the implications if I change the sa password. Also would like
> to know what all the precautions to be taken to do so.
> With Regards,
>
|||You could run a Profiler trace to catch who logs in using the "sa" login and based on that determine
what you need to do. No-one should need to login as sa, but some (badly written) apps do, though...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
> data bases on this server & the authentication type is mixed. I would like to
> know what are the implications if I change the sa password. Also would like
> to know what all the precautions to be taken to do so.
> With Regards,
>
I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
data bases on this server & the authentication type is mixed. I would like to
know what are the implications if I change the sa password. Also would like
to know what all the precautions to be taken to do so.
With Regards,
Ovin
Have a look at sp_password?
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
6
> data bases on this server & the authentication type is mixed. I would like
to
> know what are the implications if I change the sa password. Also would
like
> to know what all the precautions to be taken to do so.
> With Regards,
>
|||Hi,
There is no implications in changing the SA password. THe only thing is
check in your application for any hard coded password for sa.
If it is not there then you could change the password for SA.
Note: It is not recommended to use SA password from application. If used
create a new login with DB_owner prev. and access the application.
Thanks
Hari
SQL Server MVP
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
> 6
> data bases on this server & the authentication type is mixed. I would like
> to
> know what are the implications if I change the sa password. Also would
> like
> to know what all the precautions to be taken to do so.
> With Regards,
>
|||In SQL Server 6.5 and earlier, many tasks could only be down as the actual sa
and Windows Network Authenticated system administrators were actually mapped,
aliased, as the sa.
However, since SQL Server 7.0, the creation of the system roles removed this
rectriction. Any login, SQL Server Autenticate or Windows Authenticated, who
is also a member of the system_administrators system role will have the EXACT
same permissions as the sa account itself. The security issue here is that
EVERYONE knows that the sa account exists; thus, this is a huge security hole.
It is not only a good idea to reset this password but to do it often and
make it as complex as possible.
As far as the impact to the system is concerned, it should not as long as no
applications are using them. If you are the application developer, you
should know whether or not you are using this account and switch the
application's login to something else if it is. If you are but a lowly DBA,
you may not know, not have access, or be supporting ill-coded vendor
applications. Regardless, you can use the SQL Server Profiler and audit for
the sa account login. You will have to filter out legitamate system
operations that typically will use the sa account also. How long you run
this audit depends on the nature of the applications support but one work day
to a business week should be enough to identify those systems that may be
using this account.
If all else fails, you can extract out the encrypted password if you do not
already know it, and be prepared to reset the account's password to its
original if issues arise.
Sincerely,
Anthony Thomas
"Ovin Crasta" wrote:
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
> data bases on this server & the authentication type is mixed. I would like to
> know what are the implications if I change the sa password. Also would like
> to know what all the precautions to be taken to do so.
> With Regards,
>
|||You could run a Profiler trace to catch who logs in using the "sa" login and based on that determine
what you need to do. No-one should need to login as sa, but some (badly written) apps do, though...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
> data bases on this server & the authentication type is mixed. I would like to
> know what are the implications if I change the sa password. Also would like
> to know what all the precautions to be taken to do so.
> With Regards,
>
Changing sa password
Hi All,
I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
data bases on this server & the authentication type is mixed. I would like to
know what are the implications if I change the sa password. Also would like
to know what all the precautions to be taken to do so.
With Regards,Ovin
Have a look at sp_password?
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
6
> data bases on this server & the authentication type is mixed. I would like
to
> know what are the implications if I change the sa password. Also would
like
> to know what all the precautions to be taken to do so.
> With Regards,
>|||Hi,
There is no implications in changing the SA password. THe only thing is
check in your application for any hard coded password for sa.
If it is not there then you could change the password for SA.
Note: It is not recommended to use SA password from application. If used
create a new login with DB_owner prev. and access the application.
Thanks
Hari
SQL Server MVP
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
> 6
> data bases on this server & the authentication type is mixed. I would like
> to
> know what are the implications if I change the sa password. Also would
> like
> to know what all the precautions to be taken to do so.
> With Regards,
>|||In SQL Server 6.5 and earlier, many tasks could only be down as the actual sa
and Windows Network Authenticated system administrators were actually mapped,
aliased, as the sa.
However, since SQL Server 7.0, the creation of the system roles removed this
rectriction. Any login, SQL Server Autenticate or Windows Authenticated, who
is also a member of the system_administrators system role will have the EXACT
same permissions as the sa account itself. The security issue here is that
EVERYONE knows that the sa account exists; thus, this is a huge security hole.
It is not only a good idea to reset this password but to do it often and
make it as complex as possible.
As far as the impact to the system is concerned, it should not as long as no
applications are using them. If you are the application developer, you
should know whether or not you are using this account and switch the
application's login to something else if it is. If you are but a lowly DBA,
you may not know, not have access, or be supporting ill-coded vendor
applications. Regardless, you can use the SQL Server Profiler and audit for
the sa account login. You will have to filter out legitamate system
operations that typically will use the sa account also. How long you run
this audit depends on the nature of the applications support but one work day
to a business week should be enough to identify those systems that may be
using this account.
If all else fails, you can extract out the encrypted password if you do not
already know it, and be prepared to reset the account's password to its
original if issues arise.
Sincerely,
Anthony Thomas
"Ovin Crasta" wrote:
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
> data bases on this server & the authentication type is mixed. I would like to
> know what are the implications if I change the sa password. Also would like
> to know what all the precautions to be taken to do so.
> With Regards,
>|||You could run a Profiler trace to catch who logs in using the "sa" login and based on that determine
what you need to do. No-one should need to login as sa, but some (badly written) apps do, though...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
> data bases on this server & the authentication type is mixed. I would like to
> know what are the implications if I change the sa password. Also would like
> to know what all the precautions to be taken to do so.
> With Regards,
>
I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
data bases on this server & the authentication type is mixed. I would like to
know what are the implications if I change the sa password. Also would like
to know what all the precautions to be taken to do so.
With Regards,Ovin
Have a look at sp_password?
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
6
> data bases on this server & the authentication type is mixed. I would like
to
> know what are the implications if I change the sa password. Also would
like
> to know what all the precautions to be taken to do so.
> With Regards,
>|||Hi,
There is no implications in changing the SA password. THe only thing is
check in your application for any hard coded password for sa.
If it is not there then you could change the password for SA.
Note: It is not recommended to use SA password from application. If used
create a new login with DB_owner prev. and access the application.
Thanks
Hari
SQL Server MVP
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
> 6
> data bases on this server & the authentication type is mixed. I would like
> to
> know what are the implications if I change the sa password. Also would
> like
> to know what all the precautions to be taken to do so.
> With Regards,
>|||In SQL Server 6.5 and earlier, many tasks could only be down as the actual sa
and Windows Network Authenticated system administrators were actually mapped,
aliased, as the sa.
However, since SQL Server 7.0, the creation of the system roles removed this
rectriction. Any login, SQL Server Autenticate or Windows Authenticated, who
is also a member of the system_administrators system role will have the EXACT
same permissions as the sa account itself. The security issue here is that
EVERYONE knows that the sa account exists; thus, this is a huge security hole.
It is not only a good idea to reset this password but to do it often and
make it as complex as possible.
As far as the impact to the system is concerned, it should not as long as no
applications are using them. If you are the application developer, you
should know whether or not you are using this account and switch the
application's login to something else if it is. If you are but a lowly DBA,
you may not know, not have access, or be supporting ill-coded vendor
applications. Regardless, you can use the SQL Server Profiler and audit for
the sa account login. You will have to filter out legitamate system
operations that typically will use the sa account also. How long you run
this audit depends on the nature of the applications support but one work day
to a business week should be enough to identify those systems that may be
using this account.
If all else fails, you can extract out the encrypted password if you do not
already know it, and be prepared to reset the account's password to its
original if issues arise.
Sincerely,
Anthony Thomas
"Ovin Crasta" wrote:
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
> data bases on this server & the authentication type is mixed. I would like to
> know what are the implications if I change the sa password. Also would like
> to know what all the precautions to be taken to do so.
> With Regards,
>|||You could run a Profiler trace to catch who logs in using the "sa" login and based on that determine
what you need to do. No-one should need to login as sa, but some (badly written) apps do, though...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
> data bases on this server & the authentication type is mixed. I would like to
> know what are the implications if I change the sa password. Also would like
> to know what all the precautions to be taken to do so.
> With Regards,
>
Changing sa password
Hi All,
I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
data bases on this server & the authentication type is mixed. I would like t
o
know what are the implications if I change the sa password. Also would like
to know what all the precautions to be taken to do so.
With Regards,Ovin
Have a look at sp_password?
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
6
> data bases on this server & the authentication type is mixed. I would like
to
> know what are the implications if I change the sa password. Also would
like
> to know what all the precautions to be taken to do so.
> With Regards,
>|||Hi,
There is no implications in changing the SA password. THe only thing is
check in your application for any hard coded password for sa.
If it is not there then you could change the password for SA.
Note: It is not recommended to use SA password from application. If used
create a new login with DB_owner prev. and access the application.
Thanks
Hari
SQL Server MVP
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
> 6
> data bases on this server & the authentication type is mixed. I would like
> to
> know what are the implications if I change the sa password. Also would
> like
> to know what all the precautions to be taken to do so.
> With Regards,
>|||In SQL Server 6.5 and earlier, many tasks could only be down as the actual s
a
and Windows Network Authenticated system administrators were actually mapped
,
aliased, as the sa.
However, since SQL Server 7.0, the creation of the system roles removed this
rectriction. Any login, SQL Server Autenticate or Windows Authenticated, wh
o
is also a member of the system_administrators system role will have the EXAC
T
same permissions as the sa account itself. The security issue here is that
EVERYONE knows that the sa account exists; thus, this is a huge security hol
e.
It is not only a good idea to reset this password but to do it often and
make it as complex as possible.
As far as the impact to the system is concerned, it should not as long as no
applications are using them. If you are the application developer, you
should know whether or not you are using this account and switch the
application's login to something else if it is. If you are but a lowly DBA,
you may not know, not have access, or be supporting ill-coded vendor
applications. Regardless, you can use the SQL Server Profiler and audit for
the sa account login. You will have to filter out legitamate system
operations that typically will use the sa account also. How long you run
this audit depends on the nature of the applications support but one work da
y
to a business week should be enough to identify those systems that may be
using this account.
If all else fails, you can extract out the encrypted password if you do not
already know it, and be prepared to reset the account's password to its
original if issues arise.
Sincerely,
Anthony Thomas
"Ovin Crasta" wrote:
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
6
> data bases on this server & the authentication type is mixed. I would like
to
> know what are the implications if I change the sa password. Also would lik
e
> to know what all the precautions to be taken to do so.
> With Regards,
>|||You could run a Profiler trace to catch who logs in using the "sa" login and
based on that determine
what you need to do. No-one should need to login as sa, but some (badly writ
ten) apps do, though...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
6
> data bases on this server & the authentication type is mixed. I would like
to
> know what are the implications if I change the sa password. Also would lik
e
> to know what all the precautions to be taken to do so.
> With Regards,
>
I am running SQL server 2000 with sp3a on Windows Server 2003,I am running 6
data bases on this server & the authentication type is mixed. I would like t
o
know what are the implications if I change the sa password. Also would like
to know what all the precautions to be taken to do so.
With Regards,Ovin
Have a look at sp_password?
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
6
> data bases on this server & the authentication type is mixed. I would like
to
> know what are the implications if I change the sa password. Also would
like
> to know what all the precautions to be taken to do so.
> With Regards,
>|||Hi,
There is no implications in changing the SA password. THe only thing is
check in your application for any hard coded password for sa.
If it is not there then you could change the password for SA.
Note: It is not recommended to use SA password from application. If used
create a new login with DB_owner prev. and access the application.
Thanks
Hari
SQL Server MVP
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
> 6
> data bases on this server & the authentication type is mixed. I would like
> to
> know what are the implications if I change the sa password. Also would
> like
> to know what all the precautions to be taken to do so.
> With Regards,
>|||In SQL Server 6.5 and earlier, many tasks could only be down as the actual s
a
and Windows Network Authenticated system administrators were actually mapped
,
aliased, as the sa.
However, since SQL Server 7.0, the creation of the system roles removed this
rectriction. Any login, SQL Server Autenticate or Windows Authenticated, wh
o
is also a member of the system_administrators system role will have the EXAC
T
same permissions as the sa account itself. The security issue here is that
EVERYONE knows that the sa account exists; thus, this is a huge security hol
e.
It is not only a good idea to reset this password but to do it often and
make it as complex as possible.
As far as the impact to the system is concerned, it should not as long as no
applications are using them. If you are the application developer, you
should know whether or not you are using this account and switch the
application's login to something else if it is. If you are but a lowly DBA,
you may not know, not have access, or be supporting ill-coded vendor
applications. Regardless, you can use the SQL Server Profiler and audit for
the sa account login. You will have to filter out legitamate system
operations that typically will use the sa account also. How long you run
this audit depends on the nature of the applications support but one work da
y
to a business week should be enough to identify those systems that may be
using this account.
If all else fails, you can extract out the encrypted password if you do not
already know it, and be prepared to reset the account's password to its
original if issues arise.
Sincerely,
Anthony Thomas
"Ovin Crasta" wrote:
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
6
> data bases on this server & the authentication type is mixed. I would like
to
> know what are the implications if I change the sa password. Also would lik
e
> to know what all the precautions to be taken to do so.
> With Regards,
>|||You could run a Profiler trace to catch who logs in using the "sa" login and
based on that determine
what you need to do. No-one should need to login as sa, but some (badly writ
ten) apps do, though...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ovin Crasta" <OvinCrasta@.discussions.microsoft.com> wrote in message
news:C5EBB60D-6421-4C34-943C-46C767389402@.microsoft.com...
> Hi All,
> I am running SQL server 2000 with sp3a on Windows Server 2003,I am running
6
> data bases on this server & the authentication type is mixed. I would like
to
> know what are the implications if I change the sa password. Also would lik
e
> to know what all the precautions to be taken to do so.
> With Regards,
>
changing report from VB
I'm trying to learn how to control a report from within a VB 2005 program.
My program has a windows form with a ReportViewer on it referencing a report
(.rdlc). The report has features in it which I would like to change per my
VB program. For example, I'd like to add a checkbox to the windows form that
would change the visibility of a column on the report (i.e. when checked, the
Visibility.Hidden property of the report column would be set to False, and
vica-versa). I assume this can be done, but I can't figure out how to obtain
a reference to the items on the report from within VB. Is this possible, and
if so, how do I do this?
--
EdHello Ed,
The only way you could do this is that you add a parameter in the local
report to control the visibility of the report item and then in the windows
application, you could set the parameter value and refresh the report to
get the result.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||While I haven't tried it yet, I suppose you could load in the XML in the
.rdlc file, change the XML for the visibility of the column, and save it back
to the file, and then refresh the Report...the only problem might be that it
may produce an error message that the file is in use. This would not be an
elegant solution, particularly since if I wanted to modify the layout of the
report, I'd probably have to re-write the XML change code. I must say, it
would be very handy to be able to just click a button or checkbox to hide or
view certain parts of the reports.
Another thing I'm interested in is being able to easily show or hide group
detail on the report easily--similar to a TreeView control in Windows forms,
but with the '+' signs opening or closing levels of details. Is that
available in the Reporting Services?
--
Ed
"Wei Lu [MSFT]" wrote:
> Hello Ed,
> The only way you could do this is that you add a parameter in the local
> report to control the visibility of the report item and then in the windows
> application, you could set the parameter value and refresh the report to
> get the result.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello ED,
You could do it.
It called drilldown report.
How to: Add a Visibility Toggle to an Item (Report Designer)
http://msdn2.microsoft.com/en-us/library/ms156456.aspx
Hope this helps.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.
My program has a windows form with a ReportViewer on it referencing a report
(.rdlc). The report has features in it which I would like to change per my
VB program. For example, I'd like to add a checkbox to the windows form that
would change the visibility of a column on the report (i.e. when checked, the
Visibility.Hidden property of the report column would be set to False, and
vica-versa). I assume this can be done, but I can't figure out how to obtain
a reference to the items on the report from within VB. Is this possible, and
if so, how do I do this?
--
EdHello Ed,
The only way you could do this is that you add a parameter in the local
report to control the visibility of the report item and then in the windows
application, you could set the parameter value and refresh the report to
get the result.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||While I haven't tried it yet, I suppose you could load in the XML in the
.rdlc file, change the XML for the visibility of the column, and save it back
to the file, and then refresh the Report...the only problem might be that it
may produce an error message that the file is in use. This would not be an
elegant solution, particularly since if I wanted to modify the layout of the
report, I'd probably have to re-write the XML change code. I must say, it
would be very handy to be able to just click a button or checkbox to hide or
view certain parts of the reports.
Another thing I'm interested in is being able to easily show or hide group
detail on the report easily--similar to a TreeView control in Windows forms,
but with the '+' signs opening or closing levels of details. Is that
available in the Reporting Services?
--
Ed
"Wei Lu [MSFT]" wrote:
> Hello Ed,
> The only way you could do this is that you add a parameter in the local
> report to control the visibility of the report item and then in the windows
> application, you could set the parameter value and refresh the report to
> get the result.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello ED,
You could do it.
It called drilldown report.
How to: Add a Visibility Toggle to an Item (Report Designer)
http://msdn2.microsoft.com/en-us/library/ms156456.aspx
Hope this helps.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.
Wednesday, March 7, 2012
Changing Password for SA
We are running SQL 2000 Enterprise Edition on Windows 2003 Standard Edition
Server. How do you change the password for SA? Do we need to do anything
before and after changing the password?
Thank you.
Diane> How do you change the password for SA?
Read about sp_password.
> Do we need to do anything before and after changing the password?
Hopefully you don't have any applications or users connecting using this log
in name. If you do, you
need to handle them.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Diane Walker" <ett9300@.yahoo.com> wrote in message news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gb
l...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard Editio
n Server. How do you
> change the password for SA? Do we need to do anything before and after ch
anging the password?
> Thank you.
> Diane
>|||Hi,
sp_password stored procedure
but read this page as well
http://support.microsoft.com/kb/322336
if any of your application using sa user/password to connect to db then ,
you need to change that application as well
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
> Edition Server. How do you change the password for SA? Do we need to do
> anything before and after changing the password?
> Thank you.
> Diane
>|||ALTER LOGIN?
TheSQLGuru
President
Indicium Resources, Inc.
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
> Edition Server. How do you change the password for SA? Do we need to do
> anything before and after changing the password?
> Thank you.
> Diane
>|||Thank you very much for your prompt response. I guess that I need to change
the password off office hours. How do you find out what application is
using SA account? Thanks.
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:OopWgAWmHHA.1532@.TK2MSFTNGP03.phx.gbl...
> ALTER LOGIN?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
>|||You can set up a profiler run and have it trace login/out events and include
the Application Name as one of the columns. Note that profiler will have a
small impact on system performance.
TheSQLGuru
President
Indicium Resources, Inc.
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:eVgKfRWmHHA.596@.TK2MSFTNGP06.phx.gbl...
> Thank you very much for your prompt response. I guess that I need to
> change the password off office hours. How do you find out what
> application is using SA account? Thanks.
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:OopWgAWmHHA.1532@.TK2MSFTNGP03.phx.gbl...
>
Server. How do you change the password for SA? Do we need to do anything
before and after changing the password?
Thank you.
Diane> How do you change the password for SA?
Read about sp_password.
> Do we need to do anything before and after changing the password?
Hopefully you don't have any applications or users connecting using this log
in name. If you do, you
need to handle them.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Diane Walker" <ett9300@.yahoo.com> wrote in message news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gb
l...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard Editio
n Server. How do you
> change the password for SA? Do we need to do anything before and after ch
anging the password?
> Thank you.
> Diane
>|||Hi,
sp_password stored procedure
but read this page as well
http://support.microsoft.com/kb/322336
if any of your application using sa user/password to connect to db then ,
you need to change that application as well
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
> Edition Server. How do you change the password for SA? Do we need to do
> anything before and after changing the password?
> Thank you.
> Diane
>|||ALTER LOGIN?
TheSQLGuru
President
Indicium Resources, Inc.
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
> Edition Server. How do you change the password for SA? Do we need to do
> anything before and after changing the password?
> Thank you.
> Diane
>|||Thank you very much for your prompt response. I guess that I need to change
the password off office hours. How do you find out what application is
using SA account? Thanks.
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:OopWgAWmHHA.1532@.TK2MSFTNGP03.phx.gbl...
> ALTER LOGIN?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
>|||You can set up a profiler run and have it trace login/out events and include
the Application Name as one of the columns. Note that profiler will have a
small impact on system performance.
TheSQLGuru
President
Indicium Resources, Inc.
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:eVgKfRWmHHA.596@.TK2MSFTNGP06.phx.gbl...
> Thank you very much for your prompt response. I guess that I need to
> change the password off office hours. How do you find out what
> application is using SA account? Thanks.
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:OopWgAWmHHA.1532@.TK2MSFTNGP03.phx.gbl...
>
Changing Password for SA
We are running SQL 2000 Enterprise Edition on Windows 2003 Standard Edition
Server. How do you change the password for SA? Do we need to do anything
before and after changing the password?
Thank you.
Diane
> How do you change the password for SA?
Read about sp_password.
> Do we need to do anything before and after changing the password?
Hopefully you don't have any applications or users connecting using this login name. If you do, you
need to handle them.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Diane Walker" <ett9300@.yahoo.com> wrote in message news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard Edition Server. How do you
> change the password for SA? Do we need to do anything before and after changing the password?
> Thank you.
> Diane
>
|||ALTER LOGIN?
TheSQLGuru
President
Indicium Resources, Inc.
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
> Edition Server. How do you change the password for SA? Do we need to do
> anything before and after changing the password?
> Thank you.
> Diane
>
|||Thank you very much for your prompt response. I guess that I need to change
the password off office hours. How do you find out what application is
using SA account? Thanks.
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:OopWgAWmHHA.1532@.TK2MSFTNGP03.phx.gbl...
> ALTER LOGIN?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
>
|||You can set up a profiler run and have it trace login/out events and include
the Application Name as one of the columns. Note that profiler will have a
small impact on system performance.
TheSQLGuru
President
Indicium Resources, Inc.
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:eVgKfRWmHHA.596@.TK2MSFTNGP06.phx.gbl...
> Thank you very much for your prompt response. I guess that I need to
> change the password off office hours. How do you find out what
> application is using SA account? Thanks.
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:OopWgAWmHHA.1532@.TK2MSFTNGP03.phx.gbl...
>
Server. How do you change the password for SA? Do we need to do anything
before and after changing the password?
Thank you.
Diane
> How do you change the password for SA?
Read about sp_password.
> Do we need to do anything before and after changing the password?
Hopefully you don't have any applications or users connecting using this login name. If you do, you
need to handle them.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Diane Walker" <ett9300@.yahoo.com> wrote in message news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard Edition Server. How do you
> change the password for SA? Do we need to do anything before and after changing the password?
> Thank you.
> Diane
>
|||ALTER LOGIN?
TheSQLGuru
President
Indicium Resources, Inc.
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
> Edition Server. How do you change the password for SA? Do we need to do
> anything before and after changing the password?
> Thank you.
> Diane
>
|||Thank you very much for your prompt response. I guess that I need to change
the password off office hours. How do you find out what application is
using SA account? Thanks.
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:OopWgAWmHHA.1532@.TK2MSFTNGP03.phx.gbl...
> ALTER LOGIN?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
>
|||You can set up a profiler run and have it trace login/out events and include
the Application Name as one of the columns. Note that profiler will have a
small impact on system performance.
TheSQLGuru
President
Indicium Resources, Inc.
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:eVgKfRWmHHA.596@.TK2MSFTNGP06.phx.gbl...
> Thank you very much for your prompt response. I guess that I need to
> change the password off office hours. How do you find out what
> application is using SA account? Thanks.
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:OopWgAWmHHA.1532@.TK2MSFTNGP03.phx.gbl...
>
Changing Password for SA
We are running SQL 2000 Enterprise Edition on Windows 2003 Standard Edition
Server. How do you change the password for SA? Do we need to do anything
before and after changing the password?
Thank you.
Diane> How do you change the password for SA?
Read about sp_password.
> Do we need to do anything before and after changing the password?
Hopefully you don't have any applications or users connecting using this login name. If you do, you
need to handle them.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Diane Walker" <ett9300@.yahoo.com> wrote in message news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard Edition Server. How do you
> change the password for SA? Do we need to do anything before and after changing the password?
> Thank you.
> Diane
>|||Hi,
sp_password stored procedure
but read this page as well
http://support.microsoft.com/kb/322336
if any of your application using sa user/password to connect to db then ,
you need to change that application as well
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
> Edition Server. How do you change the password for SA? Do we need to do
> anything before and after changing the password?
> Thank you.
> Diane
>|||ALTER LOGIN?
--
TheSQLGuru
President
Indicium Resources, Inc.
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
> Edition Server. How do you change the password for SA? Do we need to do
> anything before and after changing the password?
> Thank you.
> Diane
>|||Thank you very much for your prompt response. I guess that I need to change
the password off office hours. How do you find out what application is
using SA account? Thanks.
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:OopWgAWmHHA.1532@.TK2MSFTNGP03.phx.gbl...
> ALTER LOGIN?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
>> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
>> Edition Server. How do you change the password for SA? Do we need to do
>> anything before and after changing the password?
>> Thank you.
>> Diane
>|||You can set up a profiler run and have it trace login/out events and include
the Application Name as one of the columns. Note that profiler will have a
small impact on system performance.
--
TheSQLGuru
President
Indicium Resources, Inc.
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:eVgKfRWmHHA.596@.TK2MSFTNGP06.phx.gbl...
> Thank you very much for your prompt response. I guess that I need to
> change the password off office hours. How do you find out what
> application is using SA account? Thanks.
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:OopWgAWmHHA.1532@.TK2MSFTNGP03.phx.gbl...
>> ALTER LOGIN?
>> --
>> TheSQLGuru
>> President
>> Indicium Resources, Inc.
>> "Diane Walker" <ett9300@.yahoo.com> wrote in message
>> news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
>> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
>> Edition Server. How do you change the password for SA? Do we need to
>> do anything before and after changing the password?
>> Thank you.
>> Diane
>>
>
Server. How do you change the password for SA? Do we need to do anything
before and after changing the password?
Thank you.
Diane> How do you change the password for SA?
Read about sp_password.
> Do we need to do anything before and after changing the password?
Hopefully you don't have any applications or users connecting using this login name. If you do, you
need to handle them.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Diane Walker" <ett9300@.yahoo.com> wrote in message news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard Edition Server. How do you
> change the password for SA? Do we need to do anything before and after changing the password?
> Thank you.
> Diane
>|||Hi,
sp_password stored procedure
but read this page as well
http://support.microsoft.com/kb/322336
if any of your application using sa user/password to connect to db then ,
you need to change that application as well
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
> Edition Server. How do you change the password for SA? Do we need to do
> anything before and after changing the password?
> Thank you.
> Diane
>|||ALTER LOGIN?
--
TheSQLGuru
President
Indicium Resources, Inc.
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
> Edition Server. How do you change the password for SA? Do we need to do
> anything before and after changing the password?
> Thank you.
> Diane
>|||Thank you very much for your prompt response. I guess that I need to change
the password off office hours. How do you find out what application is
using SA account? Thanks.
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:OopWgAWmHHA.1532@.TK2MSFTNGP03.phx.gbl...
> ALTER LOGIN?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
>> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
>> Edition Server. How do you change the password for SA? Do we need to do
>> anything before and after changing the password?
>> Thank you.
>> Diane
>|||You can set up a profiler run and have it trace login/out events and include
the Application Name as one of the columns. Note that profiler will have a
small impact on system performance.
--
TheSQLGuru
President
Indicium Resources, Inc.
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:eVgKfRWmHHA.596@.TK2MSFTNGP06.phx.gbl...
> Thank you very much for your prompt response. I guess that I need to
> change the password off office hours. How do you find out what
> application is using SA account? Thanks.
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:OopWgAWmHHA.1532@.TK2MSFTNGP03.phx.gbl...
>> ALTER LOGIN?
>> --
>> TheSQLGuru
>> President
>> Indicium Resources, Inc.
>> "Diane Walker" <ett9300@.yahoo.com> wrote in message
>> news:OJ0wZrVmHHA.596@.TK2MSFTNGP06.phx.gbl...
>> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
>> Edition Server. How do you change the password for SA? Do we need to
>> do anything before and after changing the password?
>> Thank you.
>> Diane
>>
>
Subscribe to:
Posts (Atom)