SQL Adding a User account: password

Showing posts with label password. Show all posts

Thursday, March 29, 2012

Advice on sa password change

I am taking over a server that doesn't seem to have been managed very well a
nd am planning on changing the sa password (for security).
However I know that various bits and bobs (on this server) seem to rely on i
t.
So I'm writing a document to outline the steps I have to take. What I need
to know is as full a list as possible of all the places I should check to se
e if the sa password has been used.
So apart from Security - Login - sa - properties, what else should I be chec
king?
Thanks in advance
DerekHi,
For 'SA' login , It is recommended to have mixed case passwords with a few
numbers along with special characters so that a hacker can not guess
the password.
Have a look into the below site from Vyas to get the best practices to be
followed in secuity.
http://vyaskn.tripod.com/sql_server...t_practices.htm
Thanks
Hari
MCDBA
"Derek" <anonymous@.discussions.microsoft.com> wrote in message
news:CAF7226E-6A3B-4210-810F-732A23E70A97@.microsoft.com...
> I am taking over a server that doesn't seem to have been managed very well
and am planning on changing the sa password (for security).
> However I know that various bits and bobs (on this server) seem to rely on
it.
> So I'm writing a document to outline the steps I have to take. What I
need to know is as full a list as possible of all the places I should check
to see if the sa password has been used.
> So apart from Security - Login - sa - properties, what else should I be
checking?
> Thanks in advance
> Derek|||If you are wondering about things that might break when you change the
password:
Look at all DTS packages - Connection properties to this SQL Server. Also
any scheduled DTS package that was scheduled in Enterprise Manager while
logged in as the sa account will have to be resecheduled.
Look at all replication agents to make sure they are not using the sa
account to connect to this server.
Look at all other jobs as well.
Any client application that uses the sa account to connect to this server
will need to be modified to account for the new password.
There are probably some things that I have missed but these have been the
ones that have caused the most problems when the sa password is changed.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Linked servers may break, but you will have to update the remote server
itself to fix the problem. Besides, you shouldn't be linking servers with
the SA login anyway.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:U%23$JPkfLEHA.3364@.cpmsftngxa10.phx.gbl...
> If you are wondering about things that might break when you change the
> password:
> Look at all DTS packages - Connection properties to this SQL Server. Also
> any scheduled DTS package that was scheduled in Enterprise Manager while
> logged in as the sa account will have to be resecheduled.
> Look at all replication agents to make sure they are not using the sa
> account to connect to this server.
> Look at all other jobs as well.
> Any client application that uses the sa account to connect to this server
> will need to be modified to account for the new password.
> There are probably some things that I have missed but these have been the
> ones that have caused the most problems when the sa password is changed.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

Sunday, March 25, 2012

advice in encryption

Hello everyone,

i need an advice in encryption in sql server 2000

which is better, to encrypt the password in asp.net and send it to the sql server already encrypt it, or to encrypt the password in the sqlserver ?

and also does anybody know if there is a tutorial about security in sql server i can use to secure my application.

Kind Regards

Mahmoud ManasrahYou should really check outMicrosoft's Patterns & Practices. This is a great series of in-depth articles with specific recommendations on how to design, build, deploy, and operate sound solutions.

In particular,Improving Web Application Security: Threats and Countermeasures,Building Secure ASP.NET Applications.

I know that you should never send password data in plain text from ASP.NET to SQL Server. I believe that you can use https to transmit the password to your processing page. But this is not an area in which I am particularly knowledgeable.

Terri

Thursday, March 8, 2012

ADP connection to SQL

I would like any advice on connecting an Access Project to SQL Server 2000. Authentication is in mixed mode and user enter a name and password. When he click cancel twice, it will appear error - he enter without check a name and password. How I can prevent that?Any chance of changing the authentication to Windows only?|||

I don't understand what is happening in your scenario - can you explain with more details how you set up your project to connect to SQL Server?

Thanks
Laurentiu

ADP connection to SQL

I don't understand what is happening in your scenario - can you explain with more details how you set up your project to connect to SQL Server?

Thanks
Laurentiu

Saturday, February 25, 2012

ADODB - Cube connection error: Provider could not set DATASOURCE, USERID, or PASSWORD property

When attempting to connect to my cube from the same server, I receive this error:
"Provider could not set DATASOURCE, USERID, or PASSWORD property"

The connection works just fine from my machine, but when going from the server to the server, I profile it, and no connection attempts are made. The server is w2k3 SE sp1, and the successful client is win xp pro sp2.

The method I'm using is an adodb ConnectionClass in C# vs.net 2003. The adodb is using v2.8, and I used the component checker to make sure the server has 2.8 - it does.
I have the user name and password in the connection string,
"Provider=MSOLAP.3;Cache Authentication=True;Persist Security Info=False;Initial Catalog=thecatalog;Data Source=theServerName;"
calling the open like: cn.Open(ConnectionString, "theuser", "thepass", 0);
and if it successfully opens, then I make use of an adomd.cellset.

I'm currently checking component differences between the 2 machines, but does anyone have any specific things to try or specific components to check?

First I would make sure you can establish OLED connection from one machine to another.

You can find here some clues on how to troubleshoot connection problems: http://www.sqljunkies.com/WebLog/edwardm/archive/2006/05/26/21447.aspx

Second, as you already suggested, I would check configuration of components.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

ADODB - Cube connection error: Provider could not set DATASOURCE, USERID, or PASSWORD proper

When attempting to connect to my cube from the same server, I receive this error:
"Provider could not set DATASOURCE, USERID, or PASSWORD property"

I'm currently checking component differences between the 2 machines, but does anyone have any specific things to try or specific components to check?

First I would make sure you can establish OLED connection from one machine to another.

You can find here some clues on how to troubleshoot connection problems: http://www.sqljunkies.com/WebLog/edwardm/archive/2006/05/26/21447.aspx

Second, as you already suggested, I would check configuration of components.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Monday, February 13, 2012

ADO Can, EM and QA cannot

Dear all,
I'm using SQl Server 2K on a webserver and the sa password is "abcde". Using
this user name and password, and with ADO, I established our website.
Now the website is still working well,can input data,show data!!
But I cannot login to this SQL Server with "Enterprise Manager" or "Query
Analyzer" on the server. Either with sa or Windows-Authenticate. (I user the
administrator to login to the server).
I'm running EM and QA on the webserver(With administrator account), not on
the client PC.
The EM and QA can work well before.
One thing is, the webserver may be infected by virus of Spida Worm.
Currently, when I try to run EM or QA, then a long time waiting. Then told
me: connection failed,...
But the website system is still working well.
Please tell me how to run up the Enterprise Manager? Thanks a lot.Hi
It is not a good idea to have SQL Server on an externally exposed server,
and it is always better to dedicate the server for a single use.
If you are connecting using ADO then you should be able to use the client
tools using the same login, check that you are using the same protocols.
John
"goldenshine" wrote:
> Dear all,
> I'm using SQl Server 2K on a webserver and the sa password is "abcde". Using
> this user name and password, and with ADO, I established our website.
> Now the website is still working well,can input data,show data!!
> But I cannot login to this SQL Server with "Enterprise Manager" or "Query
> Analyzer" on the server. Either with sa or Windows-Authenticate. (I user the
> administrator to login to the server).
> I'm running EM and QA on the webserver(With administrator account), not on
> the client PC.
> The EM and QA can work well before.
> One thing is, the webserver may be infected by virus of Spida Worm.
> Currently, when I try to run EM or QA, then a long time waiting. Then told
> me: connection failed,...
> But the website system is still working well.
> Please tell me how to run up the Enterprise Manager? Thanks a lot.|||Thanks,John,
Can you please tell me how to check the protocols? Since the website(
Asp.net) can use ADO to connect SQL Server and works well, why
EnterpriseManager cannot?
Thanks
"John Bell" wrote:
> Hi
> It is not a good idea to have SQL Server on an externally exposed server,
> and it is always better to dedicate the server for a single use.
> If you are connecting using ADO then you should be able to use the client
> tools using the same login, check that you are using the same protocols.
> John
>
> "goldenshine" wrote:
> > Dear all,
> > I'm using SQl Server 2K on a webserver and the sa password is "abcde". Using
> > this user name and password, and with ADO, I established our website.
> > Now the website is still working well,can input data,show data!!
> >
> > But I cannot login to this SQL Server with "Enterprise Manager" or "Query
> > Analyzer" on the server. Either with sa or Windows-Authenticate. (I user the
> > administrator to login to the server).
> >
> > I'm running EM and QA on the webserver(With administrator account), not on
> > the client PC.
> > The EM and QA can work well before.
> > One thing is, the webserver may be infected by virus of Spida Worm.
> > Currently, when I try to run EM or QA, then a long time waiting. Then told
> > me: connection failed,...
> > But the website system is still working well.
> >
> > Please tell me how to run up the Enterprise Manager? Thanks a lot.|||Hi
Look in the client network configuration utility on the client and the
server network configuration utitlity on the server.
John
"goldenshine" <goldenshine@.discussions.microsoft.com> wrote in message
news:FA91D6BA-7F42-4BAA-A01C-969E63685059@.microsoft.com...
> Thanks,John,
> Can you please tell me how to check the protocols? Since the website(
> Asp.net) can use ADO to connect SQL Server and works well, why
> EnterpriseManager cannot?
> Thanks
>
> "John Bell" wrote:
>> Hi
>> It is not a good idea to have SQL Server on an externally exposed server,
>> and it is always better to dedicate the server for a single use.
>> If you are connecting using ADO then you should be able to use the client
>> tools using the same login, check that you are using the same protocols.
>> John
>>
>> "goldenshine" wrote:
>> > Dear all,
>> > I'm using SQl Server 2K on a webserver and the sa password is "abcde".
>> > Using
>> > this user name and password, and with ADO, I established our website.
>> > Now the website is still working well,can input data,show data!!
>> >
>> > But I cannot login to this SQL Server with "Enterprise Manager" or
>> > "Query
>> > Analyzer" on the server. Either with sa or Windows-Authenticate. (I
>> > user the
>> > administrator to login to the server).
>> >
>> > I'm running EM and QA on the webserver(With administrator account), not
>> > on
>> > the client PC.
>> > The EM and QA can work well before.
>> > One thing is, the webserver may be infected by virus of Spida Worm.
>> > Currently, when I try to run EM or QA, then a long time waiting. Then
>> > told
>> > me: connection failed,...
>> > But the website system is still working well.
>> >
>> > Please tell me how to run up the Enterprise Manager? Thanks a lot.

ADO can run, EnterpriseManager cannot ?

Sunday, February 12, 2012

Administrator Password changed causes backup failure

We changed our administrator password on all of our servers. We were backin
g
up our SQL databases to another server
(ex: \\anotherserver\dropbox\databackup) However, we can no longer backup
to any other location other than a local drive on our SQL 2000 server.
If we try to create a backup to another location, we get a message that
reads something like: SQL can not verify the location of the file. Do you
want to use this location anyway?
When we try to backup to the location, the we get the error message that
reads: file or folder not on-line.
If we change the network adminstrator password back to it's original, we can
once again backup.
Thank you,
Ron Dittmann
--
Ron DittmannHere is the error code I found in the SqlServerAgent log:
[298] SQLServer Error: 8198, Could not obtain information about Windows
NT
group/user 'domain\username'. [SQLSTATE 42000] (ConnIsLoginSysAdmin)
Any info on this issue would be helpful. We are using Service Pack 3 one
SQL 2000 on Windows 2000 Server with ALL service packs and Windows updates
installed. The password we changed was the Administrator password for the
network, not the "sa" password. We even tried to reenter the Server Agent
password with no luck.
Thank you
Ron Dittmann
"dpolara" wrote:

> We changed our administrator password on all of our servers. We were back
ing
> up our SQL databases to another server
> (ex: \\anotherserver\dropbox\databackup) However, we can no longer backup
> to any other location other than a local drive on our SQL 2000 server.
> If we try to create a backup to another location, we get a message that
> reads something like: SQL can not verify the location of the file. Do you
> want to use this location anyway?
> When we try to backup to the location, the we get the error message that
> reads: file or folder not on-line.
> If we change the network adminstrator password back to it's original, we c
an
> once again backup.
> Thank you,
> Ron Dittmann
> --
> Ron Dittmann|||Check the following troubleshooting article:
How to troubleshoot a SQL Server 8198 error
http://support.microsoft.com/?id=834124
-Sue
On Wed, 13 Oct 2004 20:39:07 -0700, "dpolara"
<dpolara@.discussions.microsoft.com> wrote:

>We changed our administrator password on all of our servers. We were backi
ng
>up our SQL databases to another server
>(ex: \\anotherserver\dropbox\databackup) However, we can no longer backup
>to any other location other than a local drive on our SQL 2000 server.
>If we try to create a backup to another location, we get a message that
>reads something like: SQL can not verify the location of the file. Do you
>want to use this location anyway?
>When we try to backup to the location, the we get the error message that
>reads: file or folder not on-line.
>If we change the network adminstrator password back to it's original, we ca
n
>once again backup.
>Thank you,
>Ron Dittmann

administrator password and sql startup

A reality check please...
After changing the domain administrator password, we are no longer
able to connect to databases on a MS SQL Server 2000 server when
attempting to use ODBC drivers from W2K workstations.
The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
\Administrator under the "Logon under This Account" in the 'Logon' tab
in services.msc. The server name inside the SQL server are set to
mixed mode.
Am I correct in thinking that changing the password field shown in the
"Login under This Account: DomainName\Administrator to match the new
domain administrator password will bring Joy?
Thanks!
BenoitSorry dude, I just saw this post. Yes, if you change a domain acct password
,
you have to change it in the services config box as well.
However, let me caution you... running SQL under an admin acct is bad
enough, but running it under the domain admin acct is just irresponsible.
Seriously, create a separate acct for SQL and give it local admin rights if
you have to, but DON"T use the domain admin acct.
"bntgoogle@.yahoo.com" wrote:

> A reality check please...
> After changing the domain administrator password, we are no longer
> able to connect to databases on a MS SQL Server 2000 server when
> attempting to use ODBC drivers from W2K workstations.
> The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
> \Administrator under the "Logon under This Account" in the 'Logon' tab
> in services.msc. The server name inside the SQL server are set to
> mixed mode.
> Am I correct in thinking that changing the password field shown in the
> "Login under This Account: DomainName\Administrator to match the new
> domain administrator password will bring Joy?
> Thanks!
> Benoit
>

administrator password and sql startup

A reality check please...
After changing the domain administrator password, we are no longer
able to connect to databases on a MS SQL Server 2000 server when
attempting to use ODBC drivers from W2K workstations.
The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
\Administrator under the "Logon under This Account" in the 'Logon' tab
in services.msc. The server name inside the SQL server are set to
mixed mode.
Am I correct in thinking that changing the password field shown in the
"Login under This Account: DomainName\Administrator to match the new
domain administrator password will bring Joy?
Thanks!
Benoit
Sorry dude, I just saw this post. Yes, if you change a domain acct password,
you have to change it in the services config box as well.
However, let me caution you... running SQL under an admin acct is bad
enough, but running it under the domain admin acct is just irresponsible.
Seriously, create a separate acct for SQL and give it local admin rights if
you have to, but DON"T use the domain admin acct.
"bntgoogle@.yahoo.com" wrote:

> A reality check please...
> After changing the domain administrator password, we are no longer
> able to connect to databases on a MS SQL Server 2000 server when
> attempting to use ODBC drivers from W2K workstations.
> The MSSQLSERVER and SQLSERVERAGENT services both show DomainName
> \Administrator under the "Logon under This Account" in the 'Logon' tab
> in services.msc. The server name inside the SQL server are set to
> mixed mode.
> Am I correct in thinking that changing the password field shown in the
> "Login under This Account: DomainName\Administrator to match the new
> domain administrator password will bring Joy?
> Thanks!
> Benoit
>

Thursday, February 9, 2012

Administering many SQL Servers

We have 25+ SQL Servers our DBA group administers. Each is installed under a
domain account, call it Domain1\SQLAdmin. When we change the password to
Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server Agent
password properties on each box to be the new password. Is there any way to
automate this process?Hi
No. We have a similar problem with 1400 servers and are going to have each
server have it's own account and password.
This can reduce the likelihood of on compromised server being used to
compromise other, have developers connect from development to production
though linked servers or xp_cmdshell, and a denial of service (account
lockout) against the service account.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"LRSmith" <LRSmith@.discussions.microsoft.com> wrote in message
news:4A097433-5BE9-4383-BB6E-9A8FDE099103@.microsoft.com...
> We have 25+ SQL Servers our DBA group administers. Each is installed under
> a
> domain account, call it Domain1\SQLAdmin. When we change the password to
> Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server
> Agent
> password properties on each box to be the new password. Is there any way
> to
> automate this process?|||I was afraid that was the answer. Fortunately we don't have 1400 nodes to
worry about. Thanks.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> No. We have a similar problem with 1400 servers and are going to have each
> server have it's own account and password.
> This can reduce the likelihood of on compromised server being used to
> compromise other, have developers connect from development to production
> though linked servers or xp_cmdshell, and a denial of service (account
> lockout) against the service account.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "LRSmith" <LRSmith@.discussions.microsoft.com> wrote in message
> news:4A097433-5BE9-4383-BB6E-9A8FDE099103@.microsoft.com...
> > We have 25+ SQL Servers our DBA group administers. Each is installed under
> > a
> > domain account, call it Domain1\SQLAdmin. When we change the password to
> > Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server
> > Agent
> > password properties on each box to be the new password. Is there any way
> > to
> > automate this process?
>
>

Administering many SQL Servers

We have 25+ SQL Servers our DBA group administers. Each is installed under a
domain account, call it Domain1\SQLAdmin. When we change the password to
Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server Agent
password properties on each box to be the new password. Is there any way to
automate this process?
Hi
No. We have a similar problem with 1400 servers and are going to have each
server have it's own account and password.
This can reduce the likelihood of on compromised server being used to
compromise other, have developers connect from development to production
though linked servers or xp_cmdshell, and a denial of service (account
lockout) against the service account.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"LRSmith" <LRSmith@.discussions.microsoft.com> wrote in message
news:4A097433-5BE9-4383-BB6E-9A8FDE099103@.microsoft.com...
> We have 25+ SQL Servers our DBA group administers. Each is installed under
> a
> domain account, call it Domain1\SQLAdmin. When we change the password to
> Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server
> Agent
> password properties on each box to be the new password. Is there any way
> to
> automate this process?
|||I was afraid that was the answer. Fortunately we don't have 1400 nodes to
worry about. Thanks.
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> No. We have a similar problem with 1400 servers and are going to have each
> server have it's own account and password.
> This can reduce the likelihood of on compromised server being used to
> compromise other, have developers connect from development to production
> though linked servers or xp_cmdshell, and a denial of service (account
> lockout) against the service account.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "LRSmith" <LRSmith@.discussions.microsoft.com> wrote in message
> news:4A097433-5BE9-4383-BB6E-9A8FDE099103@.microsoft.com...
>
>

Administering many SQL Servers

We have 25+ SQL Servers our DBA group administers. Each is installed under a
domain account, call it Domain1\SQLAdmin. When we change the password to
Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server Agent
password properties on each box to be the new password. Is there any way to
automate this process?Hi
No. We have a similar problem with 1400 servers and are going to have each
server have it's own account and password.
This can reduce the likelihood of on compromised server being used to
compromise other, have developers connect from development to production
though linked servers or xp_cmdshell, and a denial of service (account
lockout) against the service account.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"LRSmith" <LRSmith@.discussions.microsoft.com> wrote in message
news:4A097433-5BE9-4383-BB6E-9A8FDE099103@.microsoft.com...
> We have 25+ SQL Servers our DBA group administers. Each is installed under
> a
> domain account, call it Domain1\SQLAdmin. When we change the password to
> Domain1\SQLAdmin we then have to go edit the SQL Server and SQL Server
> Agent
> password properties on each box to be the new password. Is there any way
> to
> automate this process?|||I was afraid that was the answer. Fortunately we don't have 1400 nodes to
worry about. Thanks.
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> No. We have a similar problem with 1400 servers and are going to have each
> server have it's own account and password.
> This can reduce the likelihood of on compromised server being used to
> compromise other, have developers connect from development to production
> though linked servers or xp_cmdshell, and a denial of service (account
> lockout) against the service account.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "LRSmith" <LRSmith@.discussions.microsoft.com> wrote in message
> news:4A097433-5BE9-4383-BB6E-9A8FDE099103@.microsoft.com...
>
>

Admin password for new installtion

Hi,

I just installed VS.NET 2005 on my computer and along the way SQL Server Express edition got installed too. What is the default sa password right out of the box? I actually want to use Windows authentication but was not able to set my domain account in there w/ administrative rights. I'd appreciate some help here.

Thanks,

Sam

My guess is that the default installation here uses Windows authentication and does not set an sa password. You can use any of the management tools (Management Tools Express in Express Advanced) or T-SQL to set the sa password and change the authentication method.

Thanks,
Sam Lester (MSFT)

Admin password

After I changed my admin password in Windows, my SQL Server Service Manager
(i.e. the Agent) no longer starts up. How do I fix this?
Go to the Services and changes to Service Account the MSSQL Server and the
Agent logs in, then tr to start up the services as usual, that will work. If
you dont need any access to the network with the SQL Server Services you
can also change the securty settings to LocalService Account.
But keep the following quote from MS in mind: "Security Note The
LocalSystem account has elevated local privileges. Enable delegation using a
domain user account whenever possible."
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Uncle Ben" <spamfree@.nospam.com> schrieb im Newsbeitrag
news:%23rzfVXLWFHA.2472@.TK2MSFTNGP10.phx.gbl...
> After I changed my admin password in Windows, my SQL Server Service
> Manager
> (i.e. the Agent) no longer starts up. How do I fix this?
>

Thursday, March 29, 2012

Advice on sa password change

Sunday, March 25, 2012

advice in encryption

Thursday, March 8, 2012

ADP connection to SQL

ADP connection to SQL

Saturday, February 25, 2012

ADODB - Cube connection error: Provider could not set DATASOURCE, USERID, or PASSWORD property

ADODB - Cube connection error: Provider could not set DATASOURCE, USERID, or PASSWORD proper

Monday, February 13, 2012

ADO Can, EM and QA cannot

ADO Can, EM and QA cannot

ADO Can, EM and QA cannot

ADO can run, EnterpriseManager cannot ?

ADO can run, EnterpriseManager cannot ?

ADO can run, EnterpriseManager cannot ?

Sunday, February 12, 2012

Administrator Password changed causes backup failure

administrator password and sql startup

administrator password and sql startup

Thursday, February 9, 2012

Administering many SQL Servers

Administering many SQL Servers

Administering many SQL Servers

Admin password for new installtion

Admin password

SQL Adding a User account

Blog Archive

About Me