Advice on RAID

We sell a software package that runs on dedicated servers at sites that
typically have no db administrator. SQL Server 2000 is the database, and the
application is very write intensive – data for 50 to 200 parameters is
written to the database every minute, 24 hours a day, 7 days a week. Typical
database size is about 4 or 5 GB. Usually there are a few client
workstations. The application is also read intensive. We have configured
the systems with 3 drives such that tempdb is on C, database files are on D
and the log is on E. Because of frequent disk failures and the relatively
high expense of correcting those failures, we want to switch to RAID. Having
little experience, we are looking for advice. RAID 10 is probably not an
option because of the expense. I would highly appreciate any suggestions.
Rethink your aversion to RAID10. It performs better than RAID5 on
write-intensive installations and there is more high-availability associated
with it. Calculate how much revenue your business will lose in one day.
It's likely more than a handful of disks.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"KMP" <KMP@.discussions.microsoft.com> wrote in message
news:87394BC3-4BD5-4D70-A0B4-C4D4C2DCC7AA@.microsoft.com...
We sell a software package that runs on dedicated servers at sites that
typically have no db administrator. SQL Server 2000 is the database, and
the
application is very write intensive – data for 50 to 200 parameters is
written to the database every minute, 24 hours a day, 7 days a week.
Typical
database size is about 4 or 5 GB. Usually there are a few client
workstations. The application is also read intensive. We have configured
the systems with 3 drives such that tempdb is on C, database files are on D
and the log is on E. Because of frequent disk failures and the relatively
high expense of correcting those failures, we want to switch to RAID.
Having
little experience, we are looking for advice. RAID 10 is probably not an
option because of the expense. I would highly appreciate any suggestions.
|||With such small amounts of data you might as well go with RAID 1
(mirroring), with three pairs of drives. RAID 10 has advantages but
with just 4 to 5 GB of data it would be difficult justifying enough
drives to make a good RAID 10 set. For a write intensive application
you should avoid RAID 5 altogether.
One question I have to ask. You say you have "frequent disk
failures". What kind of drives are you using? (For server
applications I expect SCSI.) What brand are they?
Good luck!
Roy
On Wed, 22 Feb 2006 12:11:27 -0800, KMP
<KMP@.discussions.microsoft.com> wrote:

>We sell a software package that runs on dedicated servers at sites that
>typically have no db administrator. SQL Server 2000 is the database, and the
>application is very write intensive data for 50 to 200 parameters is
>written to the database every minute, 24 hours a day, 7 days a week. Typical
>database size is about 4 or 5 GB. Usually there are a few client
>workstations. The application is also read intensive. We have configured
>the systems with 3 drives such that tempdb is on C, database files are on D
>and the log is on E. Because of frequent disk failures and the relatively
>high expense of correcting those failures, we want to switch to RAID. Having
>little experience, we are looking for advice. RAID 10 is probably not an
>option because of the expense. I would highly appreciate any suggestions.

Advice on RAID

We sell a software package that runs on dedicated servers at sites that
typically have no db administrator. SQL Server 2000 is the database, and the
application is very write intensive â' data for 50 to 200 parameters is
written to the database every minute, 24 hours a day, 7 days a week. Typical
database size is about 4 or 5 GB. Usually there are a few client
workstations. The application is also read intensive. We have configured
the systems with 3 drives such that tempdb is on C, database files are on D
and the log is on E. Because of frequent disk failures and the relatively
high expense of correcting those failures, we want to switch to RAID. Having
little experience, we are looking for advice. RAID 10 is probably not an
option because of the expense. I would highly appreciate any suggestions.Rethink your aversion to RAID10. It performs better than RAID5 on
write-intensive installations and there is more high-availability associated
with it. Calculate how much revenue your business will lose in one day.
It's likely more than a handful of disks.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"KMP" <KMP@.discussions.microsoft.com> wrote in message
news:87394BC3-4BD5-4D70-A0B4-C4D4C2DCC7AA@.microsoft.com...
We sell a software package that runs on dedicated servers at sites that
typically have no db administrator. SQL Server 2000 is the database, and
the
application is very write intensive â' data for 50 to 200 parameters is
written to the database every minute, 24 hours a day, 7 days a week.
Typical
database size is about 4 or 5 GB. Usually there are a few client
workstations. The application is also read intensive. We have configured
the systems with 3 drives such that tempdb is on C, database files are on D
and the log is on E. Because of frequent disk failures and the relatively
high expense of correcting those failures, we want to switch to RAID.
Having
little experience, we are looking for advice. RAID 10 is probably not an
option because of the expense. I would highly appreciate any suggestions.|||With such small amounts of data you might as well go with RAID 1
(mirroring), with three pairs of drives. RAID 10 has advantages but
with just 4 to 5 GB of data it would be difficult justifying enough
drives to make a good RAID 10 set. For a write intensive application
you should avoid RAID 5 altogether.
One question I have to ask. You say you have "frequent disk
failures". What kind of drives are you using? (For server
applications I expect SCSI.) What brand are they?
Good luck!
Roy
On Wed, 22 Feb 2006 12:11:27 -0800, KMP
<KMP@.discussions.microsoft.com> wrote:
>We sell a software package that runs on dedicated servers at sites that
>typically have no db administrator. SQL Server 2000 is the database, and the
>application is very write intensive ? data for 50 to 200 parameters is
>written to the database every minute, 24 hours a day, 7 days a week. Typical
>database size is about 4 or 5 GB. Usually there are a few client
>workstations. The application is also read intensive. We have configured
>the systems with 3 drives such that tempdb is on C, database files are on D
>and the log is on E. Because of frequent disk failures and the relatively
>high expense of correcting those failures, we want to switch to RAID. Having
>little experience, we are looking for advice. RAID 10 is probably not an
>option because of the expense. I would highly appreciate any suggestions.

Advice on RAID

We sell a software package that runs on dedicated servers at sites that
typically have no db administrator. SQL Server 2000 is the database, and th
e
application is very write intensive – data for 50 to 200 parameters is
written to the database every minute, 24 hours a day, 7 days a week. Typica
l
database size is about 4 or 5 GB. Usually there are a few client
workstations. The application is also read intensive. We have configured
the systems with 3 drives such that tempdb is on C, database files are on D
and the log is on E. Because of frequent disk failures and the relatively
high expense of correcting those failures, we want to switch to RAID. Havin
g
little experience, we are looking for advice. RAID 10 is probably not an
option because of the expense. I would highly appreciate any suggestions.Rethink your aversion to RAID10. It performs better than RAID5 on
write-intensive installations and there is more high-availability associated
with it. Calculate how much revenue your business will lose in one day.
It's likely more than a handful of disks.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"KMP" <KMP@.discussions.microsoft.com> wrote in message
news:87394BC3-4BD5-4D70-A0B4-C4D4C2DCC7AA@.microsoft.com...
We sell a software package that runs on dedicated servers at sites that
typically have no db administrator. SQL Server 2000 is the database, and
the
application is very write intensive – data for 50 to 200 parameters is
written to the database every minute, 24 hours a day, 7 days a week.
Typical
database size is about 4 or 5 GB. Usually there are a few client
workstations. The application is also read intensive. We have configured
the systems with 3 drives such that tempdb is on C, database files are on D
and the log is on E. Because of frequent disk failures and the relatively
high expense of correcting those failures, we want to switch to RAID.
Having
little experience, we are looking for advice. RAID 10 is probably not an
option because of the expense. I would highly appreciate any suggestions.|||With such small amounts of data you might as well go with RAID 1
(mirroring), with three pairs of drives. RAID 10 has advantages but
with just 4 to 5 GB of data it would be difficult justifying enough
drives to make a good RAID 10 set. For a write intensive application
you should avoid RAID 5 altogether.
One question I have to ask. You say you have "frequent disk
failures". What kind of drives are you using? (For server
applications I expect SCSI.) What brand are they?
Good luck!
Roy
On Wed, 22 Feb 2006 12:11:27 -0800, KMP
<KMP@.discussions.microsoft.com> wrote:

>We sell a software package that runs on dedicated servers at sites that
>typically have no db administrator. SQL Server 2000 is the database, and t
he
>application is very write intensive data for 50 to 200 parameters is
>written to the database every minute, 24 hours a day, 7 days a week. Typic
al
>database size is about 4 or 5 GB. Usually there are a few client
>workstations. The application is also read intensive. We have configured
>the systems with 3 drives such that tempdb is on C, database files are on D
>and the log is on E. Because of frequent disk failures and the relatively
>high expense of correcting those failures, we want to switch to RAID. Havi
ng
>little experience, we are looking for advice. RAID 10 is probably not an
>option because of the expense. I would highly appreciate any suggestions.

Advice needed - Regarding data transfer between databases on seperate servers

Hello everyone,

Here's my situation...

I'm running a web service which involves 51 seperate servers and databases.

There are fifty licensee servers (One for each US state) and one corporate server.

Each night I need to upload sales and membership data from the licensee's databases to the corporate database to compile reports.

The application platform I'm using is ASP.NET 2.0 and the the database is SQL2005 express.

I want this process to be run automatically, so I believe it's a scheduled windows service I need to setup up in .NET to make the data transfers.

If anyone has already set something up like this, or knows the steps to take? I would love to have your input.

Thanks in advance,

Robert

Did you mean 50 Databases on same server or 50 different servers?

You could set up a DTS package and schedule it to run at a particular time every day. You dont need to do anything with .NET. This can be done completely at the backend.

|||

ndinakar:

Did you mean 50 Databases on same server or 50 different servers?

You could set up a DTS package and schedule it to run at a particular time every day. You dont need to do anything with .NET. This can be done completely at the backend.

This is correct, note that SQLAgent service has to be up & running inorder to have your DTS (in SQL Server 2000) or SSIS (in SQL Server 2005) packages executed on time.

If this service was not started (stopped), any scheduled tasks in SQL Server will not work.

Conclusion: Make sure this SQLAgent service is always up & running in all your database servers (check them after batching your OS or restarting it).

One of the bad thing about this way is, you can not generate reports at anytime .. you have to wait (say till next day) in order to see the reports for all states.

How to overcome this is by using replication (for example), by replicating the data you need from source tables (in diffrent servers) into ONE server (e.g. main branch) so you can generate the reports from all 50 data sources at any time and updated;

Just a suggestion:
If the amount of data is not that much, you can export the data (say in Excel format) then send them by email to your main branch.
This might save some traffic (bandwidth) for you, but on the another hand you need to imported to SQL Server before generating the reports.
One more good thing about this way is, you will always have a copy in your email for all 50 databases.

There are many ways to do this, actullay depends on the case and how important to get the report on anytime and how large the data is.

Good luck.

|||

Hi Guys,

Thanks for the responses!

Nethi - Yes thats right - There will be 50 seperate licensee databases, which run on 50 seperate licensee servers. Each night I need to retrieve data from each of 50 seperate databases and upload it to a database on the corporate server to run reports the next day. (51 seperate servers/databases involved)

The sales data I'll be uploading nightly will be minimal, because i'll only be capturing sales that were made that day (12 am till 11:59:59 pm the licensee's server time) The membership data will be a larger file, because I need to upload all records every night, which will overwrite the prior membership data records. So in this case there will be many rows, but the actual data being uploaded from each row is minimal.

Tell me - Using DTS...

Can I fully specify what data needs to be uploaded? (Conditions such as record creation time, etc)
The servers may be in different time zones - Would this cause problems for DTS regarding capture periods?
Using DTS, will the uploads be secure?
If a scheduled data transfer fails for some reason or another, does DTS have a feature to report the failure, and what would be involved in capturing the data that wasn't transfered as scheduled? Is it complicated, difficult and time consuming?

Thanks again for your input and advice

Robert

|||

>>>Can I fully specify what data needs to be uploaded? (Conditions such as record creation time, etc)

You can use a mix of script in DTS - VB Script/T-SQL. You can call stored procedures. Google for DTS and read up some articles to get some info.

>>>The servers may be in different time zones - Would this cause problems for DTS regarding capture periods?

The DTS will run from the server its created on, on the schedule its scheduled to run. You can schedule it according to souce server timezone or target server timezone.

>>>Using DTS, will the uploads be secure?

DTS will use either Windows Authentication or SQL authentication. You can set up either way.

>>>If a scheduled data transfer fails for some reason or another, does DTS have a feature to report the failure, and what would be involved in capturing the data that wasn't transfered as scheduled? Is it complicated, difficult and time consuming?

You call the DTS package from a scheduled job. The job has additional options of reporting - email/pager and different options for success/failure.

|||

As much as I know Sql Server 2005 Express does not support DTS.

sql

Adventures with 64 bit SQL servers and legacy systems

First of all, thanks to everyone who helped me figure out how to run a
legacy DTS with a 32 bit driver on a 64 bit server. In case anyone
else has this problelm, you also have to download this from Microsoft:
Microsoft SQL Server 2000 DTS Designer Components
Now, my question is this: We have two critical procedures that use the
open query via linked server. I don't think I can modify this to use
DTS. I am having trouble creating a linked server with the 32 bit
driver. It works on the 2000 box and I have had difficulty finding
documentation of how to successfully do this. Erro is as follows:
Cannot initialize the data source object of OLE DB provider - Is there
any way I can modify the default drivers - I need the old 32 bit ODBC
driver that doesn't appear in the list to pull in our Thorougbred
Basic legacy data...
Thanks - any ideas would be appreciated.
"Kristina" <KristinaDBA@.gmail.com> wrote in message
news:1174072527.860042.123270@.n76g2000hsh.googlegr oups.com...
> First of all, thanks to everyone who helped me figure out how to run a
> legacy DTS with a 32 bit driver on a 64 bit server. In case anyone
> else has this problelm, you also have to download this from Microsoft:
> Microsoft SQL Server 2000 DTS Designer Components
> Now, my question is this: We have two critical procedures that use the
> open query via linked server. I don't think I can modify this to use
> DTS. I am having trouble creating a linked server with the 32 bit
> driver. It works on the 2000 box and I have had difficulty finding
> documentation of how to successfully do this. Erro is as follows:
> Cannot initialize the data source object of OLE DB provider - Is there
> any way I can modify the default drivers - I need the old 32 bit ODBC
> driver that doesn't appear in the list to pull in our Thorougbred
> Basic legacy data...
> Thanks - any ideas would be appreciated.
>
You can't use a 32bit OleDb provider in 64bit SQL Server. But you can
always run a 32bit instance of SQL 2005 on 64bit Windows.
David
|||On Mar 16, 5:05 pm, "David Browne" <davidbaxterbrowne no potted
m...@.hotmail.com> wrote:
> "Kristina" <Kristina...@.gmail.com> wrote in message
> news:1174072527.860042.123270@.n76g2000hsh.googlegr oups.com...
>
>
>
>
>
> You can't use a 32bit OleDb provider in 64bit SQL Server. But you can
> always run a 32bit instance of SQL 2005 on 64bit Windows.
> David- Hide quoted text -
> - Show quoted text -
I know, that was my suggestion, but I was out-voted by the network
administrators...thanks for the reply. I will have to find a way to
work around this.

Adventures with 64 bit SQL servers and legacy systems

First of all, thanks to everyone who helped me figure out how to run a
legacy DTS with a 32 bit driver on a 64 bit server. In case anyone
else has this problelm, you also have to download this from Microsoft:
Microsoft SQL Server 2000 DTS Designer Components
Now, my question is this: We have two critical procedures that use the
open query via linked server. I don't think I can modify this to use
DTS. I am having trouble creating a linked server with the 32 bit
driver. It works on the 2000 box and I have had difficulty finding
documentation of how to successfully do this. Erro is as follows:
Cannot initialize the data source object of OLE DB provider - Is there
any way I can modify the default drivers - I need the old 32 bit ODBC
driver that doesn't appear in the list to pull in our Thorougbred
Basic legacy data...
Thanks - any ideas would be appreciated."Kristina" <KristinaDBA@.gmail.com> wrote in message
news:1174072527.860042.123270@.n76g2000hsh.googlegroups.com...
> First of all, thanks to everyone who helped me figure out how to run a
> legacy DTS with a 32 bit driver on a 64 bit server. In case anyone
> else has this problelm, you also have to download this from Microsoft:
> Microsoft SQL Server 2000 DTS Designer Components
> Now, my question is this: We have two critical procedures that use the
> open query via linked server. I don't think I can modify this to use
> DTS. I am having trouble creating a linked server with the 32 bit
> driver. It works on the 2000 box and I have had difficulty finding
> documentation of how to successfully do this. Erro is as follows:
> Cannot initialize the data source object of OLE DB provider - Is there
> any way I can modify the default drivers - I need the old 32 bit ODBC
> driver that doesn't appear in the list to pull in our Thorougbred
> Basic legacy data...
> Thanks - any ideas would be appreciated.
>
You can't use a 32bit OleDb provider in 64bit SQL Server. But you can
always run a 32bit instance of SQL 2005 on 64bit Windows.
David|||On Mar 16, 5:05 pm, "David Browne" <davidbaxterbrowne no potted
m...@.hotmail.com> wrote:
> "Kristina" <Kristina...@.gmail.com> wrote in message
> news:1174072527.860042.123270@.n76g2000hsh.googlegroups.com...
>
>
>
>
>
>
>
> You can't use a 32bit OleDb provider in 64bit SQL Server. But you can
> always run a 32bit instance of SQL 2005 on 64bit Windows.
> David- Hide quoted text -
> - Show quoted text -
I know, that was my suggestion, but I was out-voted by the network
administrators...thanks for the reply. I will have to find a way to
work around this.

Adventures with 64 bit SQL servers and legacy systems

First of all, thanks to everyone who helped me figure out how to run a
legacy DTS with a 32 bit driver on a 64 bit server. In case anyone
else has this problelm, you also have to download this from Microsoft:
Microsoft SQL Server 2000 DTS Designer Components
Now, my question is this: We have two critical procedures that use the
open query via linked server. I don't think I can modify this to use
DTS. I am having trouble creating a linked server with the 32 bit
driver. It works on the 2000 box and I have had difficulty finding
documentation of how to successfully do this. Erro is as follows:
Cannot initialize the data source object of OLE DB provider - Is there
any way I can modify the default drivers - I need the old 32 bit ODBC
driver that doesn't appear in the list to pull in our Thorougbred
Basic legacy data...
Thanks - any ideas would be appreciated."Kristina" <KristinaDBA@.gmail.com> wrote in message
news:1174072527.860042.123270@.n76g2000hsh.googlegroups.com...
> First of all, thanks to everyone who helped me figure out how to run a
> legacy DTS with a 32 bit driver on a 64 bit server. In case anyone
> else has this problelm, you also have to download this from Microsoft:
> Microsoft SQL Server 2000 DTS Designer Components
> Now, my question is this: We have two critical procedures that use the
> open query via linked server. I don't think I can modify this to use
> DTS. I am having trouble creating a linked server with the 32 bit
> driver. It works on the 2000 box and I have had difficulty finding
> documentation of how to successfully do this. Erro is as follows:
> Cannot initialize the data source object of OLE DB provider - Is there
> any way I can modify the default drivers - I need the old 32 bit ODBC
> driver that doesn't appear in the list to pull in our Thorougbred
> Basic legacy data...
> Thanks - any ideas would be appreciated.
>
You can't use a 32bit OleDb provider in 64bit SQL Server. But you can
always run a 32bit instance of SQL 2005 on 64bit Windows.
David|||On Mar 16, 5:05 pm, "David Browne" <davidbaxterbrowne no potted
m...@.hotmail.com> wrote:
> "Kristina" <Kristina...@.gmail.com> wrote in message
> news:1174072527.860042.123270@.n76g2000hsh.googlegroups.com...
>
>
> > First of all, thanks to everyone who helped me figure out how to run a
> > legacy DTS with a 32 bit driver on a 64 bit server. In case anyone
> > else has this problelm, you also have to download this from Microsoft:
> > Microsoft SQL Server 2000 DTS Designer Components
> > Now, my question is this: We have two critical procedures that use the
> > open query via linked server. I don't think I can modify this to use
> > DTS. I am having trouble creating a linked server with the 32 bit
> > driver. It works on the 2000 box and I have had difficulty finding
> > documentation of how to successfully do this. Erro is as follows:
> > Cannot initialize the data source object of OLE DB provider - Is there
> > any way I can modify the default drivers - I need the old 32 bit ODBC
> > driver that doesn't appear in the list to pull in our Thorougbred
> > Basic legacy data...
> > Thanks - any ideas would be appreciated.
> You can't use a 32bit OleDb provider in 64bit SQL Server. But you can
> always run a 32bit instance of SQL 2005 on 64bit Windows.
> David- Hide quoted text -
> - Show quoted text -
I know, that was my suggestion, but I was out-voted by the network
administrators...thanks for the reply. I will have to find a way to
work around this.sql

ADSI Via Linked Server

Ok I have been through all the help and newsgroups that I can find and I can
not find the answer to my problem.
I have two SQL 2000 SP3 servers and 3 doamin controllers. On both SQL
servers I did the AD_addlinkedserver and the sp_addlinkedsrvlogin for all
local accounts to a doamin account.
One one SQL server it worked fine and I am able to run my query with no
problem but when I try to run the same query on the second SQL server I get:
Server: Msg 7320, Level 16, State 2, Line 1
Could not execute query against OLE DB provider 'ADsDSOObject'.
OLE DB error trace [OLE/DB Provider 'ADsDSOObject' ICommandText::Execute
returned 0x80040e22].
Here is the select command that I am using:
SELECT * FROM OPENQUERY( ADSI,'SELECT Name, CN FROM
''LDAP://ou=Users,DC=Domain,DC=com'' Where memberof = ''CN=Microsoft Office
2003 Standard001,OU=USA,DC=Domain,DC=com''')
Like I said this works on one SQL server but not the other. Both SQL servers
are part of the same doamin and I am trying to qury information form that
domain.
Any ideas would be great.
Did you check the MSDN article ?
http://msdn.microsoft.com/library/de...uted_query.asp
You might have a look on the error output and send it here:
http://groups.google.de/groups?hl=de...a09%26rnum%3D1
HTH, Jens Suessmeyer.
"Jesse" <Jesse@.discussions.microsoft.com> schrieb im Newsbeitrag
news:75491BB5-A8F9-4C00-A385-8836F517F641@.microsoft.com...
> Ok I have been through all the help and newsgroups that I can find and I
> can
> not find the answer to my problem.
> I have two SQL 2000 SP3 servers and 3 doamin controllers. On both SQL
> servers I did the AD_addlinkedserver and the sp_addlinkedsrvlogin for all
> local accounts to a doamin account.
> One one SQL server it worked fine and I am able to run my query with no
> problem but when I try to run the same query on the second SQL server I
> get:
> Server: Msg 7320, Level 16, State 2, Line 1
> Could not execute query against OLE DB provider 'ADsDSOObject'.
> OLE DB error trace [OLE/DB Provider 'ADsDSOObject' ICommandText::Execute
> returned 0x80040e22].
> Here is the select command that I am using:
> SELECT * FROM OPENQUERY( ADSI,'SELECT Name, CN FROM
> ''LDAP://ou=Users,DC=Domain,DC=com'' Where memberof = ''CN=Microsoft
> Office
> 2003 Standard001,OU=USA,DC=Domain,DC=com''')
> Like I said this works on one SQL server but not the other. Both SQL
> servers
> are part of the same doamin and I am trying to qury information form that
> domain.
> Any ideas would be great.
|||Jens,
Yes I saw that article and that is what I used to create my link and server
logon information.
"Jens Sü?meyer" wrote:

> Did you check the MSDN article ?
> http://msdn.microsoft.com/library/de...uted_query.asp
> You might have a look on the error output and send it here:
> http://groups.google.de/groups?hl=de...a09%26rnum%3D1
> HTH, Jens Suessmeyer.
>
> "Jesse" <Jesse@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:75491BB5-A8F9-4C00-A385-8836F517F641@.microsoft.com...
>
>

ADSI Via Linked Server

Ok I have been through all the help and newsgroups that I can find and I can
not find the answer to my problem.
I have two SQL 2000 SP3 servers and 3 doamin controllers. On both SQL
servers I did the AD_addlinkedserver and the sp_addlinkedsrvlogin for all
local accounts to a doamin account.
One one SQL server it worked fine and I am able to run my query with no
problem but when I try to run the same query on the second SQL server I get:
Server: Msg 7320, Level 16, State 2, Line 1
Could not execute query against OLE DB provider 'ADsDSOObject'.
OLE DB error trace [OLE/DB Provider 'ADsDSOObject' ICommandText::Execute
returned 0x80040e22].
Here is the select command that I am using:
SELECT * FROM OPENQUERY( ADSI,'SELECT Name, CN FROM
''LDAP://ou=Users,DC=Domain,DC=com'' Where memberof = ''CN=Microsoft Office
2003 Standard001,OU=USA,DC=Domain,DC=com''')
Like I said this works on one SQL server but not the other. Both SQL servers
are part of the same doamin and I am trying to qury information form that
domain.
Any ideas would be great.Did you check the MSDN article ?
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adsi/adsi/distributed_query.asp
You might have a look on the error output and send it here:
http://groups.google.de/groups?hl=de&lr=&threadm=pa5ReRhvBHA.2164%40cpmsftngxa09&rnum=1&prev=/groups%3Fq%3Dsql%2Bserver%2Badsi%2Blinked%2Bserver%2B7320%26hl%3Dde%26lr%3D%26selm%3Dpa5ReRhvBHA.2164%2540cpmsftngxa09%26rnum%3D1
HTH, Jens Suessmeyer.
"Jesse" <Jesse@.discussions.microsoft.com> schrieb im Newsbeitrag
news:75491BB5-A8F9-4C00-A385-8836F517F641@.microsoft.com...
> Ok I have been through all the help and newsgroups that I can find and I
> can
> not find the answer to my problem.
> I have two SQL 2000 SP3 servers and 3 doamin controllers. On both SQL
> servers I did the AD_addlinkedserver and the sp_addlinkedsrvlogin for all
> local accounts to a doamin account.
> One one SQL server it worked fine and I am able to run my query with no
> problem but when I try to run the same query on the second SQL server I
> get:
> Server: Msg 7320, Level 16, State 2, Line 1
> Could not execute query against OLE DB provider 'ADsDSOObject'.
> OLE DB error trace [OLE/DB Provider 'ADsDSOObject' ICommandText::Execute
> returned 0x80040e22].
> Here is the select command that I am using:
> SELECT * FROM OPENQUERY( ADSI,'SELECT Name, CN FROM
> ''LDAP://ou=Users,DC=Domain,DC=com'' Where memberof = ''CN=Microsoft
> Office
> 2003 Standard001,OU=USA,DC=Domain,DC=com''')
> Like I said this works on one SQL server but not the other. Both SQL
> servers
> are part of the same doamin and I am trying to qury information form that
> domain.
> Any ideas would be great.|||Jens,
Yes I saw that article and that is what I used to create my link and server
logon information.
"Jens Sü�meyer" wrote:
> Did you check the MSDN article ?
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adsi/adsi/distributed_query.asp
> You might have a look on the error output and send it here:
> http://groups.google.de/groups?hl=de&lr=&threadm=pa5ReRhvBHA.2164%40cpmsftngxa09&rnum=1&prev=/groups%3Fq%3Dsql%2Bserver%2Badsi%2Blinked%2Bserver%2B7320%26hl%3Dde%26lr%3D%26selm%3Dpa5ReRhvBHA.2164%2540cpmsftngxa09%26rnum%3D1
> HTH, Jens Suessmeyer.
>
> "Jesse" <Jesse@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:75491BB5-A8F9-4C00-A385-8836F517F641@.microsoft.com...
> > Ok I have been through all the help and newsgroups that I can find and I
> > can
> > not find the answer to my problem.
> >
> > I have two SQL 2000 SP3 servers and 3 doamin controllers. On both SQL
> > servers I did the AD_addlinkedserver and the sp_addlinkedsrvlogin for all
> > local accounts to a doamin account.
> >
> > One one SQL server it worked fine and I am able to run my query with no
> > problem but when I try to run the same query on the second SQL server I
> > get:
> >
> > Server: Msg 7320, Level 16, State 2, Line 1
> > Could not execute query against OLE DB provider 'ADsDSOObject'.
> > OLE DB error trace [OLE/DB Provider 'ADsDSOObject' ICommandText::Execute
> > returned 0x80040e22].
> >
> > Here is the select command that I am using:
> >
> > SELECT * FROM OPENQUERY( ADSI,'SELECT Name, CN FROM
> > ''LDAP://ou=Users,DC=Domain,DC=com'' Where memberof = ''CN=Microsoft
> > Office
> > 2003 Standard001,OU=USA,DC=Domain,DC=com''')
> >
> > Like I said this works on one SQL server but not the other. Both SQL
> > servers
> > are part of the same doamin and I am trying to qury information form that
> > domain.
> >
> > Any ideas would be great.
>
>

ADO Connection port with clustered servers

I am using ADO to connect to clustered SQL Servers, how do I know which port to use?
My current connection string format is:
Provider=sqloledb;Network Library=DBMSSOCN;Data Source=<server ip>,<server port>;Initial Catalog=<my catalog>;/<user>/<pass>
But with clustered servers this will not work as ports are assigned dynamically.
Thanks
If the client machine is using MDAC 2.6 or greater it will figure out the
port number.
MDAC sends a UDP packet to the server to gather this information before
sending the login packet.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||So should I just not include the port number in the connection string?
"Kevin McDonnell [MSFT]" wrote:

> If the client machine is using MDAC 2.6 or greater it will figure out the
> port number.
> MDAC sends a UDP packet to the server to gather this information before
> sending the login packet.
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>

ADO Connection port with clustered servers

I am using ADO to connect to clustered SQL Servers, how do I know which port
to use?
My current connection string format is:
Provider=sqloledb;Network Library=DBMSSOCN;Data Source=<server ip>,<server p
ort>;Initial Catalog=<my catalog>;/<user>/<pass>
But with clustered servers this will not work as ports are assigned dynamica
lly.
ThanksIf the client machine is using MDAC 2.6 or greater it will figure out the
port number.
MDAC sends a UDP packet to the server to gather this information before
sending the login packet.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||So should I just not include the port number in the connection string?
"Kevin McDonnell [MSFT]" wrote:

> If the client machine is using MDAC 2.6 or greater it will figure out the
> port number.
> MDAC sends a UDP packet to the server to gather this information before
> sending the login packet.
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>

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

Administering SQl 2000 from SQL 2005

I have some old SQL servers that I cannot upgrade becuase of the application
that uses them. Can I manage these servers from SQL 2005? IF so, are there
any known gotchas? Thanks in advance.
--
BettieYou can do all most common tasks using the new 2005 Studio, the "new and
improved" features won't work however
like i.e. Preformance Tunning Wizard.
By the way - I haven't seen any issues with my "legacy" application after
upgrading to 2005 server, as long as you keep
the specific databases on SQL2000's compatibility level (uprgade process
leaves them there by default).
rgrds
rafael
"Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>I have some old SQL servers that I cannot upgrade becuase of the
>application
> that uses them. Can I manage these servers from SQL 2005? IF so, are there
> any known gotchas? Thanks in advance.
> --
> Bettie|||No problems. I am using SQL 2005 Management studio to manage couple of my
SQL 2000 servers.
But the other way will not work out...
Thanks
Hari
"Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>I have some old SQL servers that I cannot upgrade becuase of the
>application
> that uses them. Can I manage these servers from SQL 2005? IF so, are there
> any known gotchas? Thanks in advance.
> --
> Bettie|||Thanks -- I'll try the upgrade in the lab.
--
Bettie
"Rafael Lenartowicz" wrote:
> You can do all most common tasks using the new 2005 Studio, the "new and
> improved" features won't work however
> like i.e. Preformance Tunning Wizard.
> By the way - I haven't seen any issues with my "legacy" application after
> upgrading to 2005 server, as long as you keep
> the specific databases on SQL2000's compatibility level (uprgade process
> leaves them there by default).
> rgrds
> rafael
>
> "Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
> news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
> >I have some old SQL servers that I cannot upgrade becuase of the
> >application
> > that uses them. Can I manage these servers from SQL 2005? IF so, are there
> > any known gotchas? Thanks in advance.
> > --
> > Bettie
>
>

Administering SQl 2000 from SQL 2005

I have some old SQL servers that I cannot upgrade becuase of the application
that uses them. Can I manage these servers from SQL 2005? IF so, are there
any known gotchas? Thanks in advance.
Bettie
You can do all most common tasks using the new 2005 Studio, the "new and
improved" features won't work however
like i.e. Preformance Tunning Wizard.
By the way - I haven't seen any issues with my "legacy" application after
upgrading to 2005 server, as long as you keep
the specific databases on SQL2000's compatibility level (uprgade process
leaves them there by default).
rgrds
rafael
"Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>I have some old SQL servers that I cannot upgrade becuase of the
>application
> that uses them. Can I manage these servers from SQL 2005? IF so, are there
> any known gotchas? Thanks in advance.
> --
> Bettie
|||No problems. I am using SQL 2005 Management studio to manage couple of my
SQL 2000 servers.
But the other way will not work out...
Thanks
Hari
"Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>I have some old SQL servers that I cannot upgrade becuase of the
>application
> that uses them. Can I manage these servers from SQL 2005? IF so, are there
> any known gotchas? Thanks in advance.
> --
> Bettie
|||Thanks -- I'll try the upgrade in the lab.
Bettie
"Rafael Lenartowicz" wrote:

> You can do all most common tasks using the new 2005 Studio, the "new and
> improved" features won't work however
> like i.e. Preformance Tunning Wizard.
> By the way - I haven't seen any issues with my "legacy" application after
> upgrading to 2005 server, as long as you keep
> the specific databases on SQL2000's compatibility level (uprgade process
> leaves them there by default).
> rgrds
> rafael
>
> "Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
> news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>
>

Administering SQl 2000 from SQL 2005

I have some old SQL servers that I cannot upgrade becuase of the application
that uses them. Can I manage these servers from SQL 2005? IF so, are there
any known gotchas? Thanks in advance.
--
BettieYou can do all most common tasks using the new 2005 Studio, the "new and
improved" features won't work however
like i.e. Preformance Tunning Wizard.
By the way - I haven't seen any issues with my "legacy" application after
upgrading to 2005 server, as long as you keep
the specific databases on SQL2000's compatibility level (uprgade process
leaves them there by default).
rgrds
rafael
"Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>I have some old SQL servers that I cannot upgrade becuase of the
>application
> that uses them. Can I manage these servers from SQL 2005? IF so, are there
> any known gotchas? Thanks in advance.
> --
> Bettie|||No problems. I am using SQL 2005 Management studio to manage couple of my
SQL 2000 servers.
But the other way will not work out...
Thanks
Hari
"Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in message
news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>I have some old SQL servers that I cannot upgrade becuase of the
>application
> that uses them. Can I manage these servers from SQL 2005? IF so, are there
> any known gotchas? Thanks in advance.
> --
> Bettie|||Thanks -- I'll try the upgrade in the lab.
--
Bettie
"Rafael Lenartowicz" wrote:

> You can do all most common tasks using the new 2005 Studio, the "new and
> improved" features won't work however
> like i.e. Preformance Tunning Wizard.
> By the way - I haven't seen any issues with my "legacy" application after
> upgrading to 2005 server, as long as you keep
> the specific databases on SQL2000's compatibility level (uprgade process
> leaves them there by default).
> rgrds
> rafael
>
> "Bettie Claxton" <BettieClaxton@.discussions.microsoft.com> wrote in messag
e
> news:0E984055-B655-4094-91A5-5B45C998545B@.microsoft.com...
>
>

Administering MSDE with Enterprise Manager

Can I administer SQL 2000 MSDE Release A from SQL Server's Enterprise
Manager (EM) located on another machine on the same network?
When I try to do this the EM setup wizard locates the host running MSDE but
it cannot connect either with Windows authentication or the strong password
created during MSDE's install.
EM can see other instances of SQL Server 2000 on the network (these are not
MSDE).
MSDE is running on XP (SP1) and EM is running on W2K workstation.
Many thanks.
Even if you can figure out your connectivity problem, it's probably not
legal anyway. From the Appropriate Uses of MSDE FAQ at
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
Q. Can I use SQL Server tools and services in conjunction with MSDE?
A. You can only use SQL Server tools and services in conjunction with
MSDE if you acquired MSDE through SQL Server 2000 (Developer Edition,
Standard Edition, or Enterprise Edition), and if you are using MSDE in
conjunction with a properly licensed copy of SQL Server 2000. Visit the How
to Buy page for information on obtaining a valid SQL Server license.
Note: The tools and services included with SQL Server Developer
Edition may not be used to manage production server environments.
The following utilities are installed by the MSDE setup application
and are provided without restrictions for use with the copy of MSDE that is
installed by your application: bcp.exe, cnfgsvr.exe, dcomscm.exe, osql.exe,
sqlmaint.exe, sqlmangr.exe, scm.exe, sqladhlp.exe, and svrnetcn.exe. The
dtsrun.exe utility is also provided, but can only be used to run existing
Data Transformation Services (DTS) packages against the copy of MSDE
installed by your application; it cannot be used to develop new DTS
packages.
There's not enough information in your post to determine whether or not it's
legal, but in the vast majority of instances it's not and I'm told that it
requires a room full of lawyers and white board to figure out. There are a
bunch of 3rd-party tools out there that might be of use. Have a look at
Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
> Can I administer SQL 2000 MSDE Release A from SQL Server's Enterprise
> Manager (EM) located on another machine on the same network?
> When I try to do this the EM setup wizard locates the host running MSDE
> but
> it cannot connect either with Windows authentication or the strong
> password
> created during MSDE's install.
> EM can see other instances of SQL Server 2000 on the network (these are
> not
> MSDE).
> MSDE is running on XP (SP1) and EM is running on W2K workstation.
> Many thanks.
>
begin 666 ts.gif
J1TE&.#EA`0`!`( ``````/___R'Y! $`````+ `````!``$```(!1 `[
`
end
|||Thanks. I think it is an authentication issue rather than a 'property
rights' issue. This is because:
1) I just installed the same version of MSDE on a W98SE machine and was able
to register it successfully with the copy of 'Enterprise manager';
2) I just deleted the XP 'atempted' registration and tried to re-register
it. The dialog "Register SQL Server Messages" returns the error:
"SVR1 - Registration failed for user 'sa'. Reason: Not associated with a
trusted SQL server connection"
Any idea how to make this Server connection trusted?
Thanks!
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> Even if you can figure out your connectivity problem, it's probably not
> legal anyway. From the Appropriate Uses of MSDE FAQ at
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
> Q. Can I use SQL Server tools and services in conjunction with
MSDE?
> A. You can only use SQL Server tools and services in conjunction
with
> MSDE if you acquired MSDE through SQL Server 2000 (Developer Edition,
> Standard Edition, or Enterprise Edition), and if you are using MSDE in
> conjunction with a properly licensed copy of SQL Server 2000. Visit the
How
> to Buy page for information on obtaining a valid SQL Server license.
> Note: The tools and services included with SQL Server Developer
> Edition may not be used to manage production server environments.
> The following utilities are installed by the MSDE setup application
> and are provided without restrictions for use with the copy of MSDE that
is
> installed by your application: bcp.exe, cnfgsvr.exe, dcomscm.exe,
osql.exe,
> sqlmaint.exe, sqlmangr.exe, scm.exe, sqladhlp.exe, and svrnetcn.exe. The
> dtsrun.exe utility is also provided, but can only be used to run existing
> Data Transformation Services (DTS) packages against the copy of MSDE
> installed by your application; it cannot be used to develop new DTS
> packages.
>
> There's not enough information in your post to determine whether or not
it's
> legal, but in the vast majority of instances it's not and I'm told that it
> requires a room full of lawyers and white board to figure out. There are a
> bunch of 3rd-party tools out there that might be of use. Have a look at
> Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
> news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
>
>
|||Hi Andrew,
This message means you don't have Mixed Mode authentication enabled. If you
do have enterprise manager connected, you can change this easily by looking
under the "security" tab in the properties of the server. (Right-click the
server to get to it). You need mixed mode before you can use "sa" or any sql
server username.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
news:OzXHOC3nEHA.2616@.tk2msftngp13.phx.gbl...
> Thanks. I think it is an authentication issue rather than a 'property
> rights' issue. This is because:
> 1) I just installed the same version of MSDE on a W98SE machine and was
able[vbcol=seagreen]
> to register it successfully with the copy of 'Enterprise manager';
> 2) I just deleted the XP 'atempted' registration and tried to re-register
> it. The dialog "Register SQL Server Messages" returns the error:
> "SVR1 - Registration failed for user 'sa'. Reason: Not associated with a
> trusted SQL server connection"
> Any idea how to make this Server connection trusted?
> Thanks!
>
> "Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
> news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> MSDE?
> with
> How
application[vbcol=seagreen]
> is
> osql.exe,
existing[vbcol=seagreen]
> it's
it[vbcol=seagreen]
a[vbcol=seagreen]
> rights.
MSDE[vbcol=seagreen]
are
>
|||Found it. The install command that I used:
SETUP SAPWD="wombat" created 'Windows Only Authentication'. A registry tweak
changed it to mixed, and then I could log on. Not sure exactly why Windows
authentication failed except that the admin name and pwd were different on
the MSDE machine from those on the machine that I was connecting from.
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> Even if you can figure out your connectivity problem, it's probably not
> legal anyway. From the Appropriate Uses of MSDE FAQ at
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
> Q. Can I use SQL Server tools and services in conjunction with
MSDE?
> A. You can only use SQL Server tools and services in conjunction
with
> MSDE if you acquired MSDE through SQL Server 2000 (Developer Edition,
> Standard Edition, or Enterprise Edition), and if you are using MSDE in
> conjunction with a properly licensed copy of SQL Server 2000. Visit the
How
> to Buy page for information on obtaining a valid SQL Server license.
> Note: The tools and services included with SQL Server Developer
> Edition may not be used to manage production server environments.
> The following utilities are installed by the MSDE setup application
> and are provided without restrictions for use with the copy of MSDE that
is
> installed by your application: bcp.exe, cnfgsvr.exe, dcomscm.exe,
osql.exe,
> sqlmaint.exe, sqlmangr.exe, scm.exe, sqladhlp.exe, and svrnetcn.exe. The
> dtsrun.exe utility is also provided, but can only be used to run existing
> Data Transformation Services (DTS) packages against the copy of MSDE
> installed by your application; it cannot be used to develop new DTS
> packages.
>
> There's not enough information in your post to determine whether or not
it's
> legal, but in the vast majority of instances it's not and I'm told that it
> requires a room full of lawyers and white board to figure out. There are a
> bunch of 3rd-party tools out there that might be of use. Have a look at
> Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
> news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
>
>

Administering MSDE with Enterprise Manager

Can I administer SQL 2000 MSDE Release A from SQL Server's Enterprise
Manager (EM) located on another machine on the same network?
When I try to do this the EM setup wizard locates the host running MSDE but
it cannot connect either with Windows authentication or the strong password
created during MSDE's install.
EM can see other instances of SQL Server 2000 on the network (these are not
MSDE).
MSDE is running on XP (SP1) and EM is running on W2K workstation.
Many thanks.
Even if you can figure out your connectivity problem, it's probably not
legal anyway. From the Appropriate Uses of MSDE FAQ at
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
Q. Can I use SQL Server tools and services in conjunction with MSDE?
A. You can only use SQL Server tools and services in conjunction with
MSDE if you acquired MSDE through SQL Server 2000 (Developer Edition,
Standard Edition, or Enterprise Edition), and if you are using MSDE in
conjunction with a properly licensed copy of SQL Server 2000. Visit the How
to Buy page for information on obtaining a valid SQL Server license.
Note: The tools and services included with SQL Server Developer
Edition may not be used to manage production server environments.
The following utilities are installed by the MSDE setup application
and are provided without restrictions for use with the copy of MSDE that is
installed by your application: bcp.exe, cnfgsvr.exe, dcomscm.exe, osql.exe,
sqlmaint.exe, sqlmangr.exe, scm.exe, sqladhlp.exe, and svrnetcn.exe. The
dtsrun.exe utility is also provided, but can only be used to run existing
Data Transformation Services (DTS) packages against the copy of MSDE
installed by your application; it cannot be used to develop new DTS
packages.
There's not enough information in your post to determine whether or not it's
legal, but in the vast majority of instances it's not and I'm told that it
requires a room full of lawyers and white board to figure out. There are a
bunch of 3rd-party tools out there that might be of use. Have a look at
Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
> Can I administer SQL 2000 MSDE Release A from SQL Server's Enterprise
> Manager (EM) located on another machine on the same network?
> When I try to do this the EM setup wizard locates the host running MSDE
> but
> it cannot connect either with Windows authentication or the strong
> password
> created during MSDE's install.
> EM can see other instances of SQL Server 2000 on the network (these are
> not
> MSDE).
> MSDE is running on XP (SP1) and EM is running on W2K workstation.
> Many thanks.
>
begin 666 ts.gif
J1TE&.#EA`0`!`( ``````/___R'Y! $`````+ `````!``$```(!1 `[
`
end
|||Thanks. I think it is an authentication issue rather than a 'property
rights' issue. This is because:
1) I just installed the same version of MSDE on a W98SE machine and was able
to register it successfully with the copy of 'Enterprise manager';
2) I just deleted the XP 'atempted' registration and tried to re-register
it. The dialog "Register SQL Server Messages" returns the error:
"SVR1 - Registration failed for user 'sa'. Reason: Not associated with a
trusted SQL server connection"
Any idea how to make this Server connection trusted?
Thanks!
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> Even if you can figure out your connectivity problem, it's probably not
> legal anyway. From the Appropriate Uses of MSDE FAQ at
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
> Q. Can I use SQL Server tools and services in conjunction with
MSDE?
> A. You can only use SQL Server tools and services in conjunction
with
> MSDE if you acquired MSDE through SQL Server 2000 (Developer Edition,
> Standard Edition, or Enterprise Edition), and if you are using MSDE in
> conjunction with a properly licensed copy of SQL Server 2000. Visit the
How
> to Buy page for information on obtaining a valid SQL Server license.
> Note: The tools and services included with SQL Server Developer
> Edition may not be used to manage production server environments.
> The following utilities are installed by the MSDE setup application
> and are provided without restrictions for use with the copy of MSDE that
is
> installed by your application: bcp.exe, cnfgsvr.exe, dcomscm.exe,
osql.exe,
> sqlmaint.exe, sqlmangr.exe, scm.exe, sqladhlp.exe, and svrnetcn.exe. The
> dtsrun.exe utility is also provided, but can only be used to run existing
> Data Transformation Services (DTS) packages against the copy of MSDE
> installed by your application; it cannot be used to develop new DTS
> packages.
>
> There's not enough information in your post to determine whether or not
it's
> legal, but in the vast majority of instances it's not and I'm told that it
> requires a room full of lawyers and white board to figure out. There are a
> bunch of 3rd-party tools out there that might be of use. Have a look at
> Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
> news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
>
>
|||Hi Andrew,
This message means you don't have Mixed Mode authentication enabled. If you
do have enterprise manager connected, you can change this easily by looking
under the "security" tab in the properties of the server. (Right-click the
server to get to it). You need mixed mode before you can use "sa" or any sql
server username.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
news:OzXHOC3nEHA.2616@.tk2msftngp13.phx.gbl...
> Thanks. I think it is an authentication issue rather than a 'property
> rights' issue. This is because:
> 1) I just installed the same version of MSDE on a W98SE machine and was
able[vbcol=seagreen]
> to register it successfully with the copy of 'Enterprise manager';
> 2) I just deleted the XP 'atempted' registration and tried to re-register
> it. The dialog "Register SQL Server Messages" returns the error:
> "SVR1 - Registration failed for user 'sa'. Reason: Not associated with a
> trusted SQL server connection"
> Any idea how to make this Server connection trusted?
> Thanks!
>
> "Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
> news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> MSDE?
> with
> How
application[vbcol=seagreen]
> is
> osql.exe,
existing[vbcol=seagreen]
> it's
it[vbcol=seagreen]
a[vbcol=seagreen]
> rights.
MSDE[vbcol=seagreen]
are
>
|||Found it. The install command that I used:
SETUP SAPWD="wombat" created 'Windows Only Authentication'. A registry tweak
changed it to mixed, and then I could log on. Not sure exactly why Windows
authentication failed except that the admin name and pwd were different on
the MSDE machine from those on the machine that I was connecting from.
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> Even if you can figure out your connectivity problem, it's probably not
> legal anyway. From the Appropriate Uses of MSDE FAQ at
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
> Q. Can I use SQL Server tools and services in conjunction with
MSDE?
> A. You can only use SQL Server tools and services in conjunction
with
> MSDE if you acquired MSDE through SQL Server 2000 (Developer Edition,
> Standard Edition, or Enterprise Edition), and if you are using MSDE in
> conjunction with a properly licensed copy of SQL Server 2000. Visit the
How
> to Buy page for information on obtaining a valid SQL Server license.
> Note: The tools and services included with SQL Server Developer
> Edition may not be used to manage production server environments.
> The following utilities are installed by the MSDE setup application
> and are provided without restrictions for use with the copy of MSDE that
is
> installed by your application: bcp.exe, cnfgsvr.exe, dcomscm.exe,
osql.exe,
> sqlmaint.exe, sqlmangr.exe, scm.exe, sqladhlp.exe, and svrnetcn.exe. The
> dtsrun.exe utility is also provided, but can only be used to run existing
> Data Transformation Services (DTS) packages against the copy of MSDE
> installed by your application; it cannot be used to develop new DTS
> packages.
>
> There's not enough information in your post to determine whether or not
it's
> legal, but in the vast majority of instances it's not and I'm told that it
> requires a room full of lawyers and white board to figure out. There are a
> bunch of 3rd-party tools out there that might be of use. Have a look at
> Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
> news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
>
>

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...
>
>