Multi value parameter not working

I have installed MS sql server 2005 developer edition beta2.
In report designer,i have given a parameter to a multi value and when see in
preview i am able to see the multi valued parameter.
but when i run it and see it in reportserver,even though i select multi
values,while displaying the results its taking only the last value selected.
please help me in this regard.I think that with Beta 2 there were some problems with multi-value. It is
working in the release version. If you have MSDN you can download it.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"sirisha" <sirisha@.discussions.microsoft.com> wrote in message
news:D7D10346-8D31-4810-A287-AD6D1D41030B@.microsoft.com...
>I have installed MS sql server 2005 developer edition beta2.
> In report designer,i have given a parameter to a multi value and when see
> in
> preview i am able to see the multi valued parameter.
> but when i run it and see it in reportserver,even though i select multi
> values,while displaying the results its taking only the last value
> selected.
> please help me in this regard.
>sql

Multi Server Jobs

I am running two instances of SQL Server 2005 Developer Edition (SP1) on the
same machine. Both SQL Server and Agent services use a local user account
which is member of Windows Administrators. The wizard for Enlisting TSX
fails with the following report:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'NIMA\sql2005_1' is running (Success)
The service 'SQLAgent$SQL2005_1' is running.
- Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
Enlisting target server 'NIMA\sql2005_2' with master server
'NIMA\sql2005_1'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'NIMA\sql2005_2'. (Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=20476
--
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect
to server. .) (Microsoft SQL Server, Error: 22026)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
Any help would be greatly appreciated,
leilaHello Leila,
Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
SP2.
Have you tried a domain account for SQL Agent?
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons
> I am running two instances of SQL Server 2005 Developer Edition (SP1)
> on the same machine. Both SQL Server and Agent services use a local
> user account which is member of Windows Administrators. The wizard for
> Enlisting TSX fails with the following report:
> Enlist TSX Progress
> - Create MSXOperator (Success)
> Checking for an existing MSXOperator.
> Updating existing MSXOperator.
> Successfully updated MSXOperator.
> - Make sure the Agent service for 'NIMA\sql2005_1' is running
> (Success)
> The service 'SQLAgent$SQL2005_1' is running.
> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
> Enlisting target server 'NIMA\sql2005_2' with master server
> 'NIMA\sql2005_1'.
> Using new enlistment method.
> Messages
> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9
> .00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplat
> es.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=2047
> 6
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> The enlist operation failed (reason: SQLServerAgent Error: Unable to
> connect to server. .) (Microsoft SQL Server, Error: 22026)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=0
> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
> Any help would be greatly appreciated,
> leil|||Actually I don't have a domain on my notebook, I have used .\username for
agents.
"Simon Sabin" <SimonSabin@.noemail.noemail> wrote in message
news:62959f1a43cc68c90a27d3a103d4@.msnews.microsoft.com...
> Hello Leila,
> Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
> SP2.
> Have you tried a domain account for SQL Agent?
> Simon Sabin
> SQL Server MVP
> http://sqlblogcasts.com/blogs/simons
>
>> I am running two instances of SQL Server 2005 Developer Edition (SP1)
>> on the same machine. Both SQL Server and Agent services use a local
>> user account which is member of Windows Administrators. The wizard for
>> Enlisting TSX fails with the following report:
>> Enlist TSX Progress
>> - Create MSXOperator (Success)
>> Checking for an existing MSXOperator.
>> Updating existing MSXOperator.
>> Successfully updated MSXOperator.
>> - Make sure the Agent service for 'NIMA\sql2005_1' is running
>> (Success)
>> The service 'SQLAgent$SQL2005_1' is running.
>> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
>> Enlisting target server 'NIMA\sql2005_2' with master server
>> 'NIMA\sql2005_1'.
>> Using new enlistment method.
>> Messages
>> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
>> (Microsoft.SqlServer.Smo)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9
>> .00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplat
>> es.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=2047
>> 6
>> --
>> ADDITIONAL INFORMATION:
>> An exception occurred while executing a Transact-SQL statement or
>> batch. (Microsoft.SqlServer.ConnectionInfo)
>> --
>> The enlist operation failed (reason: SQLServerAgent Error: Unable to
>> connect to server. .) (Microsoft SQL Server, Error: 22026)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=0
>> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
>> Any help would be greatly appreciated,
>> leila
>

Multi Server Jobs

I am running two instances of SQL Server 2005 Developer Edition (SP1) on the
same machine. Both SQL Server and Agent services use a local user account
which is member of Windows Administrators. The wizard for Enlisting TSX
fails with the following report:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'NIMA\sql2005_1' is running (Success)
The service 'SQLAgent$SQL2005_1' is running.
- Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
Enlisting target server 'NIMA\sql2005_2' with master server
'NIMA\sql2005_1'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'NIMA\sql2005_2'. (Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect
to server. .) (Microsoft SQL Server, Error: 22026)
For help, click:
http://go.microsoft.com/fwlink?Prod...26&LinkId=20476
Any help would be greatly appreciated,
leilaHello Leila,
Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
SP2.
Have you tried a domain account for SQL Agent?
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons

> I am running two instances of SQL Server 2005 Developer Edition (SP1)
> on the same machine. Both SQL Server and Agent services use a local
> user account which is member of Windows Administrators. The wizard for
> Enlisting TSX fails with the following report:
> Enlist TSX Progress
> - Create MSXOperator (Success)
> Checking for an existing MSXOperator.
> Updating existing MSXOperator.
> Successfully updated MSXOperator.
> - Make sure the Agent service for 'NIMA\sql2005_1' is running
> (Success)
> The service 'SQLAgent$SQL2005_1' is running.
> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
> Enlisting target server 'NIMA\sql2005_2' with master server
> 'NIMA\sql2005_1'.
> Using new enlistment method.
> Messages
> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...erver&ProdVer=9
> .00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplat
> es.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=2047
> 6
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> The enlist operation failed (reason: SQLServerAgent Error: Unable to
> connect to server. .) (Microsoft SQL Server, Error: 22026)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...erver&ProdVer=0
> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
> Any help would be greatly appreciated,
> leila|||Actually I don't have a domain on my notebook, I have used .\username for
agents.
"Simon Sabin" <SimonSabin@.noemail.noemail> wrote in message
news:62959f1a43cc68c90a27d3a103d4@.msnews
.microsoft.com...
> Hello Leila,
> Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
> SP2.
> Have you tried a domain account for SQL Agent?
> Simon Sabin
> SQL Server MVP
> http://sqlblogcasts.com/blogs/simons
>
>sql

Multi Server Jobs

I am running two instances of SQL Server 2005 Developer Edition (SP1) on the
same machine. Both SQL Server and Agent services use a local user account
which is member of Windows Administrators. The wizard for Enlisting TSX
fails with the following report:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'NIMA\sql2005_1' is running (Success)
The service 'SQLAgent$SQL2005_1' is running.
- Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
Enlisting target server 'NIMA\sql2005_2' with master server
'NIMA\sql2005_1'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'NIMA\sql2005_2'. (Microsoft.SqlServer.Smo)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=MSX+enlist+JobServer&LinkId=20476[/url]
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect
to server. .) (Microsoft SQL Server, Error: 22026)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00 .2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476[ /url]
Any help would be greatly appreciated,
leila
Hello Leila,
Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
SP2.
Have you tried a domain account for SQL Agent?
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons

> I am running two instances of SQL Server 2005 Developer Edition (SP1)
> on the same machine. Both SQL Server and Agent services use a local
> user account which is member of Windows Administrators. The wizard for
> Enlisting TSX fails with the following report:
> Enlist TSX Progress
> - Create MSXOperator (Success)
> Checking for an existing MSXOperator.
> Updating existing MSXOperator.
> Successfully updated MSXOperator.
> - Make sure the Agent service for 'NIMA\sql2005_1' is running
> (Success)
> The service 'SQLAgent$SQL2005_1' is running.
> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
> Enlisting target server 'NIMA\sql2005_2' with master server
> 'NIMA\sql2005_1'.
> Using new enlistment method.
> Messages
> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9
> .00.2047.00&EvtSrc=Microsoft.SqlServer.Management. Smo.ExceptionTemplat
> es.FailedOperationExceptionText&EvtID=MSX+enlist+J obServer&LinkId=2047
> 6
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> The enlist operation failed (reason: SQLServerAgent Error: Unable to
> connect to server. .) (Microsoft SQL Server, Error: 22026)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=0
> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20 476
> Any help would be greatly appreciated,
> leila
|||Actually I don't have a domain on my notebook, I have used .\username for
agents.
"Simon Sabin" <SimonSabin@.noemail.noemail> wrote in message
news:62959f1a43cc68c90a27d3a103d4@.msnews.microsoft .com...
> Hello Leila,
> Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
> SP2.
> Have you tried a domain account for SQL Agent?
> Simon Sabin
> SQL Server MVP
> http://sqlblogcasts.com/blogs/simons
>
>

Multi Server Administration (Error Enlist MSX)

With Sql-Server 2000 i am using since a long time the jobserver (MSX) with TSX-servers.

Now I installed Sql-Server 2005 Standard Edition (the same i have tested with developer edition) on NT-2003 SP1.

I have 2 Sql-Server instances installed.

Now i tryed to configure one instance as MSX-Server and the other one as TSX-Server.

No Chance. When i do it with Management-Studio the following error ist displayed:
The enlist operation failed (reason:SqlServerAgent Error: Unable to connect to 'MSX HG-ALV-012\I1'). (Microsoft Sql Server,Error:22026).

In the Agent-log i found after every try the following error-messages:

Date 06.12.2005 17:29:42
Log SQL Agent (Current - 06.12.2005 17:29:00)

Message
[298] SQLServer Error: 805, SSL Provider: Die Zertifikatkette wurde von einer nicht vertrauenswürdigen Zertifizierungsstelle ausgestellt. [SQLSTATE 08001]

[298] SQLServer Error: 805, Client unable to establish connection [SQLSTATE 08001]

Message in Eventlog:
Date 06.12.2005 17:29:42
Log Windows NT (System)

Source Schannel
Category (0)
Event 3221262354
Computer HG-ALV-012

Message
Das vom Remoteserver erhaltene Zertifikat wurde von einer nicht vertrauenswürdigen Zertifizierungsstelle
ausgestellt. Aus diesem Grund k?nnen keine der im Zertifikat enthalten Daten verifiziert werden. Die
SSL-Verbindungsanforderung ist fehlgeschlagen. Die angeh?ngten Daten enthalten das Serverzertifikat.
I don't know what this has to do with certificates? The Configuration for the connections on the server (tcp) is definitely set to "ForceEncrypten=No".

Both Sql Server instances are running under the same Domain-Account. (Also the Agents!)

Has anyone an idea how to solve that problem?

There is a good Webcast exactly on this topic recorded at Dec 15 2005.
Theme: Upgrading SQL Server Agent to SQL Server 2000.

EventID is 1032285816

Look at http://msevents.microsoft.com/cui/WebCastEventDetails.aspx?EventID=1032285816&EventCategory=5&culture=en-US&CountryCode=US

Regards

Ralph Kemperdick

Multi Server Administration (Error Enlist MSX)

With Sql-Server 2000 i am using since a long time the jobserver (MSX) with TSX-servers.

Now I installed Sql-Server 2005 Standard Edition (the same i have tested with developer edition) on NT-2003 SP1.

I have 2 Sql-Server instances installed.

Now i tryed to configure one instance as MSX-Server and the other one as TSX-Server.

No Chance. When i do it with Management-Studio the following error ist displayed:
The enlist operation failed (reason:SqlServerAgent Error: Unable to connect to 'MSX HG-ALV-012\I1'). (Microsoft Sql Server,Error:22026).

In the Agent-log i found after every try the following error-messages:

Date 06.12.2005 17:29:42
Log SQL Agent (Current - 06.12.2005 17:29:00)

Message
[298] SQLServer Error: 805, SSL Provider: Die Zertifikatkette wurde von einer nicht vertrauenswürdigen Zertifizierungsstelle ausgestellt. [SQLSTATE 08001]

[298] SQLServer Error: 805, Client unable to establish connection [SQLSTATE 08001]

Message in Eventlog:
Date 06.12.2005 17:29:42
Log Windows NT (System)

Source Schannel
Category (0)
Event 3221262354
Computer HG-ALV-012

Message
Das vom Remoteserver erhaltene Zertifikat wurde von einer nicht vertrauenswürdigen Zertifizierungsstelle
ausgestellt. Aus diesem Grund k?nnen keine der im Zertifikat enthalten Daten verifiziert werden. Die
SSL-Verbindungsanforderung ist fehlgeschlagen. Die angeh?ngten Daten enthalten das Serverzertifikat.
I don't know what this has to do with certificates? The Configuration for the connections on the server (tcp) is definitely set to "ForceEncrypten=No".

Both Sql Server instances are running under the same Domain-Account. (Also the Agents!)

Has anyone an idea how to solve that problem?

There is a good Webcast exactly on this topic recorded at Dec 15 2005.
Theme: Upgrading SQL Server Agent to SQL Server 2000.

EventID is 1032285816

Look at http://msevents.microsoft.com/cui/WebCastEventDetails.aspx?EventID=1032285816&EventCategory=5&culture=en-US&CountryCode=US

Regards

Ralph Kemperdick

sql

multi processor server

Can the Standard edition of SS2000 take advantage of multiple processors or
do we need the enterprise edition? Do we need the enterprise edition to take
advantage of memory over 4G?
Thanks,
Dan D.
Std edition of SQL Server 2000 can use up to 4 processors although not all
commands will use them in parallel. For instance Creating or reindexing an
index will not use multiple processors. But queries can use parallelism when
appropriate. You do need Enterprise Edition to use more than 2GB of memory
in 2000. IN 2005 though Std edition can use up to the OS maximum for memory.
Andrew J. Kelly SQL MVP
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:AA36EAB7-E084-4DBB-A9FC-D79204FA5A0D@.microsoft.com...
> Can the Standard edition of SS2000 take advantage of multiple processors
> or
> do we need the enterprise edition? Do we need the enterprise edition to
> take
> advantage of memory over 4G?
> Thanks,
> --
> Dan D.
|||We have a box with 8 processors. Will the standard edition of 2005 use the 8
processors?
Thanks Andrew,
Dan D.
"Andrew J. Kelly" wrote:

> Std edition of SQL Server 2000 can use up to 4 processors although not all
> commands will use them in parallel. For instance Creating or reindexing an
> index will not use multiple processors. But queries can use parallelism when
> appropriate. You do need Enterprise Edition to use more than 2GB of memory
> in 2000. IN 2005 though Std edition can use up to the OS maximum for memory.
> --
> Andrew J. Kelly SQL MVP
>
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:AA36EAB7-E084-4DBB-A9FC-D79204FA5A0D@.microsoft.com...
>
>
|||Not 8 individual processors. It will use 4 dual core or 4 Hyper-Threaded
processors but not 8 physical processors.
Andrew J. Kelly SQL MVP
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:8254B71A-D71B-404B-BE48-6521820989C5@.microsoft.com...[vbcol=seagreen]
> We have a box with 8 processors. Will the standard edition of 2005 use the
> 8
> processors?
> Thanks Andrew,
> --
> Dan D.
>
> "Andrew J. Kelly" wrote:
|||Thanks.
Dan D.
"Andrew J. Kelly" wrote:

> Not 8 individual processors. It will use 4 dual core or 4 Hyper-Threaded
> processors but not 8 physical processors.
> --
> Andrew J. Kelly SQL MVP
>
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:8254B71A-D71B-404B-BE48-6521820989C5@.microsoft.com...
>
>

multi processor server

Can the Standard edition of SS2000 take advantage of multiple processors or
do we need the enterprise edition? Do we need the enterprise edition to take
advantage of memory over 4G?
Thanks,
--
Dan D.Std edition of SQL Server 2000 can use up to 4 processors although not all
commands will use them in parallel. For instance Creating or reindexing an
index will not use multiple processors. But queries can use parallelism when
appropriate. You do need Enterprise Edition to use more than 2GB of memory
in 2000. IN 2005 though Std edition can use up to the OS maximum for memory.
Andrew J. Kelly SQL MVP
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:AA36EAB7-E084-4DBB-A9FC-D79204FA5A0D@.microsoft.com...
> Can the Standard edition of SS2000 take advantage of multiple processors
> or
> do we need the enterprise edition? Do we need the enterprise edition to
> take
> advantage of memory over 4G?
> Thanks,
> --
> Dan D.|||We have a box with 8 processors. Will the standard edition of 2005 use the 8
processors?
Thanks Andrew,
--
Dan D.
"Andrew J. Kelly" wrote:

> Std edition of SQL Server 2000 can use up to 4 processors although not all
> commands will use them in parallel. For instance Creating or reindexing an
> index will not use multiple processors. But queries can use parallelism wh
en
> appropriate. You do need Enterprise Edition to use more than 2GB of memory
> in 2000. IN 2005 though Std edition can use up to the OS maximum for memor
y.
> --
> Andrew J. Kelly SQL MVP
>
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:AA36EAB7-E084-4DBB-A9FC-D79204FA5A0D@.microsoft.com...
>
>|||Not 8 individual processors. It will use 4 dual core or 4 Hyper-Threaded
processors but not 8 physical processors.
Andrew J. Kelly SQL MVP
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:8254B71A-D71B-404B-BE48-6521820989C5@.microsoft.com...[vbcol=seagreen]
> We have a box with 8 processors. Will the standard edition of 2005 use the
> 8
> processors?
> Thanks Andrew,
> --
> Dan D.
>
> "Andrew J. Kelly" wrote:
>|||Thanks.
--
Dan D.
"Andrew J. Kelly" wrote:

> Not 8 individual processors. It will use 4 dual core or 4 Hyper-Threaded
> processors but not 8 physical processors.
> --
> Andrew J. Kelly SQL MVP
>
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:8254B71A-D71B-404B-BE48-6521820989C5@.microsoft.com...
>
>

multi processor server

Can the Standard edition of SS2000 take advantage of multiple processors or
do we need the enterprise edition? Do we need the enterprise edition to take
advantage of memory over 4G?
Thanks,
--
Dan D.Std edition of SQL Server 2000 can use up to 4 processors although not all
commands will use them in parallel. For instance Creating or reindexing an
index will not use multiple processors. But queries can use parallelism when
appropriate. You do need Enterprise Edition to use more than 2GB of memory
in 2000. IN 2005 though Std edition can use up to the OS maximum for memory.
--
Andrew J. Kelly SQL MVP
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:AA36EAB7-E084-4DBB-A9FC-D79204FA5A0D@.microsoft.com...
> Can the Standard edition of SS2000 take advantage of multiple processors
> or
> do we need the enterprise edition? Do we need the enterprise edition to
> take
> advantage of memory over 4G?
> Thanks,
> --
> Dan D.|||We have a box with 8 processors. Will the standard edition of 2005 use the 8
processors?
Thanks Andrew,
--
Dan D.
"Andrew J. Kelly" wrote:
> Std edition of SQL Server 2000 can use up to 4 processors although not all
> commands will use them in parallel. For instance Creating or reindexing an
> index will not use multiple processors. But queries can use parallelism when
> appropriate. You do need Enterprise Edition to use more than 2GB of memory
> in 2000. IN 2005 though Std edition can use up to the OS maximum for memory.
> --
> Andrew J. Kelly SQL MVP
>
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:AA36EAB7-E084-4DBB-A9FC-D79204FA5A0D@.microsoft.com...
> > Can the Standard edition of SS2000 take advantage of multiple processors
> > or
> > do we need the enterprise edition? Do we need the enterprise edition to
> > take
> > advantage of memory over 4G?
> >
> > Thanks,
> > --
> > Dan D.
>
>|||Not 8 individual processors. It will use 4 dual core or 4 Hyper-Threaded
processors but not 8 physical processors.
--
Andrew J. Kelly SQL MVP
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:8254B71A-D71B-404B-BE48-6521820989C5@.microsoft.com...
> We have a box with 8 processors. Will the standard edition of 2005 use the
> 8
> processors?
> Thanks Andrew,
> --
> Dan D.
>
> "Andrew J. Kelly" wrote:
>> Std edition of SQL Server 2000 can use up to 4 processors although not
>> all
>> commands will use them in parallel. For instance Creating or reindexing
>> an
>> index will not use multiple processors. But queries can use parallelism
>> when
>> appropriate. You do need Enterprise Edition to use more than 2GB of
>> memory
>> in 2000. IN 2005 though Std edition can use up to the OS maximum for
>> memory.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
>> news:AA36EAB7-E084-4DBB-A9FC-D79204FA5A0D@.microsoft.com...
>> > Can the Standard edition of SS2000 take advantage of multiple
>> > processors
>> > or
>> > do we need the enterprise edition? Do we need the enterprise edition to
>> > take
>> > advantage of memory over 4G?
>> >
>> > Thanks,
>> > --
>> > Dan D.
>>|||Thanks.
--
Dan D.
"Andrew J. Kelly" wrote:
> Not 8 individual processors. It will use 4 dual core or 4 Hyper-Threaded
> processors but not 8 physical processors.
> --
> Andrew J. Kelly SQL MVP
>
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:8254B71A-D71B-404B-BE48-6521820989C5@.microsoft.com...
> > We have a box with 8 processors. Will the standard edition of 2005 use the
> > 8
> > processors?
> >
> > Thanks Andrew,
> > --
> > Dan D.
> >
> >
> > "Andrew J. Kelly" wrote:
> >
> >> Std edition of SQL Server 2000 can use up to 4 processors although not
> >> all
> >> commands will use them in parallel. For instance Creating or reindexing
> >> an
> >> index will not use multiple processors. But queries can use parallelism
> >> when
> >> appropriate. You do need Enterprise Edition to use more than 2GB of
> >> memory
> >> in 2000. IN 2005 though Std edition can use up to the OS maximum for
> >> memory.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >>
> >>
> >> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> >> news:AA36EAB7-E084-4DBB-A9FC-D79204FA5A0D@.microsoft.com...
> >> > Can the Standard edition of SS2000 take advantage of multiple
> >> > processors
> >> > or
> >> > do we need the enterprise edition? Do we need the enterprise edition to
> >> > take
> >> > advantage of memory over 4G?
> >> >
> >> > Thanks,
> >> > --
> >> > Dan D.
> >>
> >>
> >>
>
>

muliple instances

Does anyone know if we need Standard or Enterprise Edition if we want to use Multiple instances for SQL2000.
Thanks, Mark.Either will work.|||Yep works with Standard, Enterprise, Personal and Developer not sure about MSDE though.

Originally posted by mark2
Does anyone know if we need Standard or Enterprise Edition if we want to use Multiple instances for SQL2000.

Thanks, Mark.|||Thanks, now I'm certain what I can tell the customer.

MSSQLSERVER error(s) - severity and state

Hi
W2K3 std edition (no SP) - SQL Server Std SP3
I have a lot of errors showing up in app log on different days and times in
the form of:
***********************************
MSSQLSERVER, Category (2), Event ID: 17055
Description:
18052
Error: 3314, Severoty:21, State: 4
***********************************
The 'error' number varies between, 3314, 9001 and 823.
The account is always the same one.
Trawling through the SQL log - I can see some entries with the following
detail:
***********************************
database 'XYZ' cannot be opened. it has been marked SUSPECT by recovery. See
the event log for more information.
***********************************
DBCC CHECKDB shows no errors on this database.
Any pointers on this very much appreciated.
All SQL services are currently running.
Thanks
Bryan
If I were you, I would suck and backup as much of the data as you can
from the database files / disks. Seems to me that this is a hard error
inidcating that your underlying disks are about to die (or the
controller has a defect). Backup up and then checking / replacing the
databases would be the best to do. (for me)
HTH, Jens Suessmeyer.
|||Hi Jens
Thanks for the prompt reply.
Would this still be the case, as I have a whole bunch of DBs stting on the
same disk location.
I should have also noted that this is a SAN attached server.
Are there any particular tools (that are non intrusive as this is a
production server) that can check the integrity of a particular database
(other than DBCC CHECKDB/CHECKALLOC/CHECKCATALOG)?
Thanks
Bry
"Jens" wrote:

> If I were you, I would suck and backup as much of the data as you can
> from the database files / disks. Seems to me that this is a hard error
> inidcating that your underlying disks are about to die (or the
> controller has a defect). Backup up and then checking / replacing the
> databases would be the best to do. (for me)
> HTH, Jens Suessmeyer.
>
|||All of the errors point to disk problems, but given you are on a SAN(NAS?) I
would expect the problem is not hardware, but either overloading or
networking.
If you NAS/SAN configuration is not tuned properly, you could get the error
codes you listed.
Another possibility (which is why I added NAS rather than SAN) is that if
you have a bad or misconfigured switch, you could be seeing packe drops if
your server is 100MB and the switch port is 10MB.
Just ideas.
Joseph R.P. Maloney, CSP,CCP,CDP
"bryan" wrote:

> Hi
> W2K3 std edition (no SP) - SQL Server Std SP3
> I have a lot of errors showing up in app log on different days and times in
> the form of:
> ***********************************
> MSSQLSERVER, Category (2), Event ID: 17055
> Description:
> 18052
> Error: 3314, Severoty:21, State: 4
> ***********************************
> The 'error' number varies between, 3314, 9001 and 823.
> The account is always the same one.
> Trawling through the SQL log - I can see some entries with the following
> detail:
> ***********************************
> database 'XYZ' cannot be opened. it has been marked SUSPECT by recovery. See
> the event log for more information.
> ***********************************
> DBCC CHECKDB shows no errors on this database.
> Any pointers on this very much appreciated.
> All SQL services are currently running.
> Thanks
> Bryan
>
>
|||Hi Joseph
Thanks for your comments, always appreciated. I shall certainly take a look
at all your suggestions.
I will update any progress I make.
Best rgds
Bryan
"jrpm" wrote:
[vbcol=seagreen]
> All of the errors point to disk problems, but given you are on a SAN(NAS?) I
> would expect the problem is not hardware, but either overloading or
> networking.
> If you NAS/SAN configuration is not tuned properly, you could get the error
> codes you listed.
> Another possibility (which is why I added NAS rather than SAN) is that if
> you have a bad or misconfigured switch, you could be seeing packe drops if
> your server is 100MB and the switch port is 10MB.
> Just ideas.
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "bryan" wrote:

MSSQLSERVER error(s) - severity and state

Hi
W2K3 std edition (no SP) - SQL Server Std SP3
I have a lot of errors showing up in app log on different days and times in
the form of:
***********************************
MSSQLSERVER, Category (2), Event ID: 17055
Description:
18052
Error: 3314, Severoty:21, State: 4
***********************************
The 'error' number varies between, 3314, 9001 and 823.
The account is always the same one.
Trawling through the SQL log - I can see some entries with the following
detail:
***********************************
database 'XYZ' cannot be opened. it has been marked SUSPECT by recovery. See
the event log for more information.
***********************************
DBCC CHECKDB shows no errors on this database.
Any pointers on this very much appreciated.
All SQL services are currently running.
Thanks
BryanIf I were you, I would suck and backup as much of the data as you can
from the database files / disks. Seems to me that this is a hard error
inidcating that your underlying disks are about to die (or the
controller has a defect). Backup up and then checking / replacing the
databases would be the best to do. (for me)
HTH, Jens Suessmeyer.|||Hi Jens
Thanks for the prompt reply.
Would this still be the case, as I have a whole bunch of DBs stting on the
same disk location.
I should have also noted that this is a SAN attached server.
Are there any particular tools (that are non intrusive as this is a
production server) that can check the integrity of a particular database
(other than DBCC CHECKDB/CHECKALLOC/CHECKCATALOG)?
Thanks
Bry
"Jens" wrote:
> If I were you, I would suck and backup as much of the data as you can
> from the database files / disks. Seems to me that this is a hard error
> inidcating that your underlying disks are about to die (or the
> controller has a defect). Backup up and then checking / replacing the
> databases would be the best to do. (for me)
> HTH, Jens Suessmeyer.
>|||All of the errors point to disk problems, but given you are on a SAN(NAS?) I
would expect the problem is not hardware, but either overloading or
networking.
If you NAS/SAN configuration is not tuned properly, you could get the error
codes you listed.
Another possibility (which is why I added NAS rather than SAN) is that if
you have a bad or misconfigured switch, you could be seeing packe drops if
your server is 100MB and the switch port is 10MB.
Just ideas.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"bryan" wrote:
> Hi
> W2K3 std edition (no SP) - SQL Server Std SP3
> I have a lot of errors showing up in app log on different days and times in
> the form of:
> ***********************************
> MSSQLSERVER, Category (2), Event ID: 17055
> Description:
> 18052
> Error: 3314, Severoty:21, State: 4
> ***********************************
> The 'error' number varies between, 3314, 9001 and 823.
> The account is always the same one.
> Trawling through the SQL log - I can see some entries with the following
> detail:
> ***********************************
> database 'XYZ' cannot be opened. it has been marked SUSPECT by recovery. See
> the event log for more information.
> ***********************************
> DBCC CHECKDB shows no errors on this database.
> Any pointers on this very much appreciated.
> All SQL services are currently running.
> Thanks
> Bryan
>
>|||Hi Joseph
Thanks for your comments, always appreciated. I shall certainly take a look
at all your suggestions.
I will update any progress I make.
Best rgds
Bryan
"jrpm" wrote:
> All of the errors point to disk problems, but given you are on a SAN(NAS?) I
> would expect the problem is not hardware, but either overloading or
> networking.
> If you NAS/SAN configuration is not tuned properly, you could get the error
> codes you listed.
> Another possibility (which is why I added NAS rather than SAN) is that if
> you have a bad or misconfigured switch, you could be seeing packe drops if
> your server is 100MB and the switch port is 10MB.
> Just ideas.
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "bryan" wrote:
> > Hi
> >
> > W2K3 std edition (no SP) - SQL Server Std SP3
> >
> > I have a lot of errors showing up in app log on different days and times in
> > the form of:
> >
> > ***********************************
> > MSSQLSERVER, Category (2), Event ID: 17055
> > Description:
> > 18052
> > Error: 3314, Severoty:21, State: 4
> > ***********************************
> > The 'error' number varies between, 3314, 9001 and 823.
> >
> > The account is always the same one.
> >
> > Trawling through the SQL log - I can see some entries with the following
> > detail:
> >
> > ***********************************
> > database 'XYZ' cannot be opened. it has been marked SUSPECT by recovery. See
> > the event log for more information.
> > ***********************************
> >
> > DBCC CHECKDB shows no errors on this database.
> > Any pointers on this very much appreciated.
> >
> > All SQL services are currently running.
> >
> > Thanks
> > Bryan
> >
> >
> >

MSSQLSERVER error(s) - severity and state

Hi
W2K3 std edition (no SP) - SQL Server Std SP3
I have a lot of errors showing up in app log on different days and times in
the form of:
***********************************
MSSQLSERVER, Category (2), Event ID: 17055
Description:
18052
Error: 3314, Severoty:21, State: 4
***********************************
The 'error' number varies between, 3314, 9001 and 823.
The account is always the same one.
Trawling through the SQL log - I can see some entries with the following
detail:
***********************************
database 'XYZ' cannot be opened. it has been marked SUSPECT by recovery. See
the event log for more information.
***********************************
DBCC CHECKDB shows no errors on this database.
Any pointers on this very much appreciated.
All SQL services are currently running.
Thanks
BryanIf I were you, I would suck and backup as much of the data as you can
from the database files / disks. Seems to me that this is a hard error
inidcating that your underlying disks are about to die (or the
controller has a defect). Backup up and then checking / replacing the
databases would be the best to do. (for me)
HTH, Jens Suessmeyer.|||Hi Jens
Thanks for the prompt reply.
Would this still be the case, as I have a whole bunch of DBs stting on the
same disk location.
I should have also noted that this is a SAN attached server.
Are there any particular tools (that are non intrusive as this is a
production server) that can check the integrity of a particular database
(other than DBCC CHECKDB/CHECKALLOC/CHECKCATALOG)?
Thanks
Bry
"Jens" wrote:

> If I were you, I would suck and backup as much of the data as you can
> from the database files / disks. Seems to me that this is a hard error
> inidcating that your underlying disks are about to die (or the
> controller has a defect). Backup up and then checking / replacing the
> databases would be the best to do. (for me)
> HTH, Jens Suessmeyer.
>|||All of the errors point to disk problems, but given you are on a SAN(NAS?) I
would expect the problem is not hardware, but either overloading or
networking.
If you NAS/SAN configuration is not tuned properly, you could get the error
codes you listed.
Another possibility (which is why I added NAS rather than SAN) is that if
you have a bad or misconfigured switch, you could be seeing packe drops if
your server is 100MB and the switch port is 10MB.
Just ideas.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"bryan" wrote:

> Hi
> W2K3 std edition (no SP) - SQL Server Std SP3
> I have a lot of errors showing up in app log on different days and times i
n
> the form of:
> ***********************************
> MSSQLSERVER, Category (2), Event ID: 17055
> Description:
> 18052
> Error: 3314, Severoty:21, State: 4
> ***********************************
> The 'error' number varies between, 3314, 9001 and 823.
> The account is always the same one.
> Trawling through the SQL log - I can see some entries with the following
> detail:
> ***********************************
> database 'XYZ' cannot be opened. it has been marked SUSPECT by recovery. S
ee
> the event log for more information.
> ***********************************
> DBCC CHECKDB shows no errors on this database.
> Any pointers on this very much appreciated.
> All SQL services are currently running.
> Thanks
> Bryan
>
>|||Hi Joseph
Thanks for your comments, always appreciated. I shall certainly take a look
at all your suggestions.
I will update any progress I make.
Best rgds
Bryan
"jrpm" wrote:
[vbcol=seagreen]
> All of the errors point to disk problems, but given you are on a SAN(NAS?)
I
> would expect the problem is not hardware, but either overloading or
> networking.
> If you NAS/SAN configuration is not tuned properly, you could get the erro
r
> codes you listed.
> Another possibility (which is why I added NAS rather than SAN) is that if
> you have a bad or misconfigured switch, you could be seeing packe drops if
> your server is 100MB and the switch port is 10MB.
> Just ideas.
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "bryan" wrote:
>

MSSQL2K and WIN2K3 SP1

We have a Windows Server 2003 Standard with SQL Server 2000 Standard
edition serving as a development server. There are several DTS packages
hosted on the server and they connect to an entry from the local hosts
table. The reason for this is that each of the DEV, QA and PROD
servers in this group have an entry with the same name (ex. SVR_DBNAME)
but each of which point to their own IP address, allowing us to copy
the packages between servers without going back and changing all the
server name references.
Recently, WIN2K3 SP1 was installed on the machine and immediately, the
DTS packages - which use WIndows Authentication - failed with a message
indicating that the system could not authenticate against the local
Windows user:
Login failed for user '(null)'
Once SP1 was removed, the packages resumed working. What setting does
the service pack change that is causing this?
thanks
markHi
A couple of questions
Does the server/s have Mixed authentication mode or windows only?
Did you try ( If I understood correctly) to add an owner of DTS Packages to
the group of Admin of WIN2K3?
<markfcook@.gmail.com> wrote in message
news:1161054855.189750.67760@.m73g2000cwd.googlegroups.com...
> We have a Windows Server 2003 Standard with SQL Server 2000 Standard
> edition serving as a development server. There are several DTS packages
> hosted on the server and they connect to an entry from the local hosts
> table. The reason for this is that each of the DEV, QA and PROD
> servers in this group have an entry with the same name (ex. SVR_DBNAME)
> but each of which point to their own IP address, allowing us to copy
> the packages between servers without going back and changing all the
> server name references.
> Recently, WIN2K3 SP1 was installed on the machine and immediately, the
> DTS packages - which use WIndows Authentication - failed with a message
> indicating that the system could not authenticate against the local
> Windows user:
> Login failed for user '(null)'
> Once SP1 was removed, the packages resumed working. What setting does
> the service pack change that is causing this?
> thanks
> mark
>|||Q1) mixed mode authentication is used
Q2) the windows account is a member of the local administrators group
Uri Dimant wrote:
> Hi
> A couple of questions
> Does the server/s have Mixed authentication mode or windows only?
> Did you try ( If I understood correctly) to add an owner of DTS Packages to
> the group of Admin of WIN2K3?
>
>
>
> <markfcook@.gmail.com> wrote in message
> news:1161054855.189750.67760@.m73g2000cwd.googlegroups.com...
> > We have a Windows Server 2003 Standard with SQL Server 2000 Standard
> > edition serving as a development server. There are several DTS packages
> > hosted on the server and they connect to an entry from the local hosts
> > table. The reason for this is that each of the DEV, QA and PROD
> > servers in this group have an entry with the same name (ex. SVR_DBNAME)
> > but each of which point to their own IP address, allowing us to copy
> > the packages between servers without going back and changing all the
> > server name references.
> >
> > Recently, WIN2K3 SP1 was installed on the machine and immediately, the
> > DTS packages - which use WIndows Authentication - failed with a message
> > indicating that the system could not authenticate against the local
> > Windows user:
> >
> > Login failed for user '(null)'
> >
> > Once SP1 was removed, the packages resumed working. What setting does
> > the service pack change that is causing this?
> >
> > thanks
> >
> > mark
> >

MSSQL2005 SP1 setup

I have an Evaluation version of Enterprise edition MSSQL2005 for development. I tried to install MSSQL2005 sp1 and it is necessary to upgrade to the release version of SQL2005. Currently, I just got the release CD on hand, how can I upgrade the evaluation version to release version except uninstalling the eval and install with the release edition? Thanks in advance

You can "Upgrade" from Eval to the release version by launching setup from the CD. Setup will find the existing eval instance inform you that you can upgrade the instance.

jeff.

MSSQL Version

I have currently Standard Edition of MSSQL installed on my various servers. These servers are interacting with my one central server which also has Standard Edition of MSSQL.
Please let me know if I change my central server Standard Edition of MSSQL to Enterprise Edition and keep the other server with the Standard Edition, will this effect the working ?
Also please confirm, what are the changes in terms of query syntax or database setting that I will have to change for this change of version.i would not imagine there'd be any change required in your sql code as it remains fairly standard.

if you change the central server to enterprise edition you will obviously have to do some reconfigurations, but that's a given when installing something new, but i wouldn't imagine anything too drastic.

should connect and run well, good luck|||You can run a mix of Developer, Personal, Standard, and Enterprise versions of SQL Server with no problem. The Transact-SQL syntax is exactly the same on all of them, although there may be some SQL features that only exist on certain versions. As an example, clustering is only available to the Enterprise version, so you can't use clustering features in the Standard version, although the syntax would be the same if you could.

-PatP|||Thanks a lot !

MSsql Standard connect error

Hello
I have installed Mssql 2000 standard Edition on windows 2003 sp1 with
instance name "mssql" ( hostname ="DBServer". Now I can only connect
from localhost with path "DBServer\mssql". From all other computers in
my network i cannot connect ( error "Mssql server does not exist...").
I cant even connect from localhost with path "localhost\mssql".
Previous I had Mssql 2000 Developer Edition installed on other Win2003
SP1 and I had no problems with connecting.
What can be wrong ?
Best Regards
Wojciech Znaniecki
Is SP3 or higher installed on the Win2K3 server? Is the instance listening
on TCP? Check the SQL Server errorlog to find out...
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"wojtas_z" <wojtas_z@.poczta.fm> wrote in message
news:1131012588.047990.42900@.g14g2000cwa.googlegro ups.com...
> Hello
> I have installed Mssql 2000 standard Edition on windows 2003 sp1 with
> instance name "mssql" ( hostname ="DBServer". Now I can only connect
> from localhost with path "DBServer\mssql". From all other computers in
> my network i cannot connect ( error "Mssql server does not exist...").
> I cant even connect from localhost with path "localhost\mssql".
> Previous I had Mssql 2000 Developer Edition installed on other Win2003
> SP1 and I had no problems with connecting.
> What can be wrong ?
> Best Regards
> Wojciech Znaniecki
>

MSsql Standard connect error

Hello
I have installed Mssql 2000 standard Edition on windows 2003 sp1 with
instance name "mssql" ( hostname ="DBServer". Now I can only connect
from localhost with path "DBServer\mssql". From all other computers in
my network i cannot connect ( error "Mssql server does not exist...").
I cant even connect from localhost with path "localhost\mssql".
Previous I had Mssql 2000 Developer Edition installed on other Win2003
SP1 and I had no problems with connecting.
What can be wrong ?
Best Regards
Wojciech ZnanieckiIs SP3 or higher installed on the Win2K3 server? Is the instance listening
on TCP? Check the SQL Server errorlog to find out...
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"wojtas_z" <wojtas_z@.poczta.fm> wrote in message
news:1131012588.047990.42900@.g14g2000cwa.googlegroups.com...
> Hello
> I have installed Mssql 2000 standard Edition on windows 2003 sp1 with
> instance name "mssql" ( hostname ="DBServer". Now I can only connect
> from localhost with path "DBServer\mssql". From all other computers in
> my network i cannot connect ( error "Mssql server does not exist...").
> I cant even connect from localhost with path "localhost\mssql".
> Previous I had Mssql 2000 Developer Edition installed on other Win2003
> SP1 and I had no problems with connecting.
> What can be wrong ?
> Best Regards
> Wojciech Znaniecki
>

MSSQL Server 2005 Not Reporting Errors to Windows Event Log

Hello All,

I just performed a fresh install of MSSQL 2005 Server Developer Edition on my XPSP2 machine along with MSSQL 2005 SP1 and I noticed that errors are not being reported in the Windows Event Viewer. Is there a way to enable/disable logging here?

I need to view these logs because when the tasks > 'copy database' task fails it submits its error in the Windows Event Log however since I reinstalled MSSQL 2005 these log entries don't appear here.

thanks in advance.

Hi,

if you are using a job for this you can switch the Windows event logging on.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Its not a job. I just manually select the task from Management Studio. In the last installation performing this task created log entries in the windows event log but for some reason they aren't appearing now.

|||

Hi:

The main log for SQL Server 2005 installation has changed, and placed in the following location:

%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt

For more information, please refer to the following MSDN reference.

http://msdn2.microsoft.com/en-us/library/ms143702.aspx

Hope this helps. :-)

Thanks.

|||

Interesting... I wonder why events don't show up in the Windows Event Log anymore? Especially since MSSQL 2005 specifically says that it will make log entries in the Windows Event Log in the Copy Database task wizard.

|||

Hi,

If the Severity Level is 19 or Higher then only it will be logged in the Windows Event Log.

HTH

Hemantgiri S. Goswami