DMO reports product level as sp3 instead of sp3a

Hi,
1. I am using the "ProductLevel" property of the "SQLServer2" SQL DMO object
to determine the product level of my SQL server 2000 installation. However
even when I have installed "SQL Server 2000 sp3a" on my machine, this
property still reports the server product level as sp3 (instead of sp3a). Is
there a workaround for this using which I can get the exact product level?
2. I am using the "xp_msver" sproc to get the SQL server version. The SQL
server 2000 installation with sp3 installed has version no= 8.0.760. This
version is reported by xp_msver. However when "sp3a" is installed on this,
the version is still reported as "8.0.760" when it should be "8.0.761". Is
this a bug in the execution of xp_msver?
Plz reply ASAP.
ThanxOn Mon, 14 Mar 2005 12:42:16 +0530, Onkar Walavalkar wrote:
(snip)
Hi Onkar,
As far as I know, SP3a and SP3 are the same WRT the server part; the
only differences are in the client tools. That's why the server will
never report SP3a, and that's why both SP3 and SP3a correspond to
version 8.00.760.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)

Distribution Subsystem: agent (null) failed.

Win 2k & SQL 2k SP3a
This error appears in my Application Log. How can I fix/remove/delete
this? How can I determine what dB this is from?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17052
Date:12/23/2005
Time:8:00:11 AM
User:ROUSES.COM\Administrator
Computer:ROUSEONE
Description:
Error: 14151, Severity: 18, State: 1
Replication-Replication Distribution Subsystem: agent (null) failed.
The subscription to publication '(null)' has expired and does not
exist.
Data:
0000: 47 37 00 00 12 00 00 00 G7.....
0008: 09 00 00 00 52 00 4f 00 ...R.O.
0010: 55 00 53 00 45 00 4f 00 U.S.E.O.
0018: 4e 00 45 00 00 00 0d 00 N.E....
0020: 00 00 64 00 69 00 73 00 ..d.i.s.
0028: 74 00 72 00 69 00 62 00 t.r.i.b.
0030: 75 00 74 00 69 00 6f 00 u.t.i.o.
0038: 6e 00 00 00 n...
Run your agents one by one to see if you can manually force this error in
your event log.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"LPR-3rd" <lreames@.gmail.com> wrote in message
news:1135354198.113526.29560@.z14g2000cwz.googlegro ups.com...
> Win 2k & SQL 2k SP3a
> This error appears in my Application Log. How can I fix/remove/delete
> this? How can I determine what dB this is from?
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 12/23/2005
> Time: 8:00:11 AM
> User: ROUSES.COM\Administrator
> Computer: ROUSEONE
> Description:
> Error: 14151, Severity: 18, State: 1
> Replication-Replication Distribution Subsystem: agent (null) failed.
> The subscription to publication '(null)' has expired and does not
> exist.
> Data:
> 0000: 47 37 00 00 12 00 00 00 G7.....
> 0008: 09 00 00 00 52 00 4f 00 ...R.O.
> 0010: 55 00 53 00 45 00 4f 00 U.S.E.O.
> 0018: 4e 00 45 00 00 00 0d 00 N.E....
> 0020: 00 00 64 00 69 00 73 00 ..d.i.s.
> 0028: 74 00 72 00 69 00 62 00 t.r.i.b.
> 0030: 75 00 74 00 69 00 6f 00 u.t.i.o.
> 0038: 6e 00 00 00 n...
>

Distribution database indexes

All,
I can seem to find much info on this. I'm trying to determine when and if I
need to rebuild the indexes on the Distribution database. We're running
transactional replicaiton 24/7 so I'm concerned it will interupt service.
Thanks in advance.
For the most part the transactions/queries which hit the distribution
database are seeks you will probably find that the impact of fragmentation
is minimal.
While you can defrag your indexes online in SQL 2000 you can't rebuild them
online in SQL 2000 (you can in SQL 2005). I suspect your problems are not
related to indexes.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:AD2E42BC-DD48-4964-9EE8-5134FED52DD4@.microsoft.com...
> All,
> I can seem to find much info on this. I'm trying to determine when and if
> I
> need to rebuild the indexes on the Distribution database. We're running
> transactional replicaiton 24/7 so I'm concerned it will interupt service.
> Thanks in advance.
|||We're not having problems, I was looking for general info about distribution
db indexes.
Thanks for the info!
"Hilary Cotter" wrote:

> For the most part the transactions/queries which hit the distribution
> database are seeks you will probably find that the impact of fragmentation
> is minimal.
> While you can defrag your indexes online in SQL 2000 you can't rebuild them
> online in SQL 2000 (you can in SQL 2005). I suspect your problems are not
> related to indexes.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
> news:AD2E42BC-DD48-4964-9EE8-5134FED52DD4@.microsoft.com...
>
>