Known sp3a bugs.

Hello everyone,
We have upgraded to SQL Server 2000/sp2. When a service
pack comes, generally companies wait for sometime before
they apply. This is just to avoid potential new bugs and
find out some information.
My question is: Are there any known issues with SP3a? If
yes, what they are and whether its safe to apply the
patch.
Thanks in advance,
mzeeshanWe've had it installed on a dozen servers for awhile now with no problems. I
really think the practice of releasing patches has changed in that now they
are pretty thoroughly tested prior to public release. The problem with
waiting to install it is MS releases the bug fixes in the service pack once
they release the service pack and virus writers quickly write programs to
attach the patched holes knowing that admins are reluctant to patch the
systems right away. Not sure how to combat that but it is a problem
HTH.
--
Ray Higdon MCSE, MCDBA, CCNA
--
"mzeeshan" <mzeeshan@.yahoo.com> wrote in message
news:0fbe01c38a88$c3912300$a401280a@.phx.gbl...
> Hello everyone,
> We have upgraded to SQL Server 2000/sp2. When a service
> pack comes, generally companies wait for sometime before
> they apply. This is just to avoid potential new bugs and
> find out some information.
> My question is: Are there any known issues with SP3a? If
> yes, what they are and whether its safe to apply the
> patch.
> Thanks in advance,
> mzeeshan|||Thanks for your reply. I know the problems, the SQL
slammer worm was created by someone based on a CERT
advisory. And, if I am not wrong, the patch was already
there but not installed by users till it became the
problem. Fortunately, we were spared as all our boxes
were inaccessible from outside.
The flip side is the creation of new problems generated
by service packs themselves. If I can recall, there was a
service pack (may be 4 or 5) with WindowsNT that created
so many problems that a new one (sp6) was quickly
released.
Its good to hear that MS is more careful now.
Thanks anyway,
mzeeshan
>--Original Message--
>We've had it installed on a dozen servers for awhile now
with no problems. I
>really think the practice of releasing patches has
changed in that now they
>are pretty thoroughly tested prior to public release.
The problem with
>waiting to install it is MS releases the bug fixes in
the service pack once
>they release the service pack and virus writers quickly
write programs to
>attach the patched holes knowing that admins are
reluctant to patch the
>systems right away. Not sure how to combat that but it
is a problem
>HTH.
>--
>Ray Higdon MCSE, MCDBA, CCNA
>--
>"mzeeshan" <mzeeshan@.yahoo.com> wrote in message
>news:0fbe01c38a88$c3912300$a401280a@.phx.gbl...
>> Hello everyone,
>> We have upgraded to SQL Server 2000/sp2. When a service
>> pack comes, generally companies wait for sometime
before
>> they apply. This is just to avoid potential new bugs
and
>> find out some information.
>> My question is: Are there any known issues with SP3a?
If
>> yes, what they are and whether its safe to apply the
>> patch.
>> Thanks in advance,
>> mzeeshan
>
>.
>|||Didn't mean to sound insensitive to the concerns of reluctant admins, just
pointing it out, there's wisdom in waiting if you can afford to..everything
in one way or another is a cost-benefit analysis :)
GL
--
Ray Higdon MCSE, MCDBA, CCNA
--
"mzeeshan" <mzeeshan@.yahoo.com> wrote in message
news:2052f01c38a9e$01b99030$a601280a@.phx.gbl...
> Thanks for your reply. I know the problems, the SQL
> slammer worm was created by someone based on a CERT
> advisory. And, if I am not wrong, the patch was already
> there but not installed by users till it became the
> problem. Fortunately, we were spared as all our boxes
> were inaccessible from outside.
> The flip side is the creation of new problems generated
> by service packs themselves. If I can recall, there was a
> service pack (may be 4 or 5) with WindowsNT that created
> so many problems that a new one (sp6) was quickly
> released.
> Its good to hear that MS is more careful now.
> Thanks anyway,
> mzeeshan
> >--Original Message--
> >We've had it installed on a dozen servers for awhile now
> with no problems. I
> >really think the practice of releasing patches has
> changed in that now they
> >are pretty thoroughly tested prior to public release.
> The problem with
> >waiting to install it is MS releases the bug fixes in
> the service pack once
> >they release the service pack and virus writers quickly
> write programs to
> >attach the patched holes knowing that admins are
> reluctant to patch the
> >systems right away. Not sure how to combat that but it
> is a problem
> >
> >HTH.
> >
> >--
> >Ray Higdon MCSE, MCDBA, CCNA
> >--
> >"mzeeshan" <mzeeshan@.yahoo.com> wrote in message
> >news:0fbe01c38a88$c3912300$a401280a@.phx.gbl...
> >> Hello everyone,
> >>
> >> We have upgraded to SQL Server 2000/sp2. When a service
> >> pack comes, generally companies wait for sometime
> before
> >> they apply. This is just to avoid potential new bugs
> and
> >> find out some information.
> >>
> >> My question is: Are there any known issues with SP3a?
> If
> >> yes, what they are and whether its safe to apply the
> >> patch.
> >>
> >> Thanks in advance,
> >> mzeeshan
> >
> >
> >.
> >|||SP3 has all of MS's security fixes for SQL Server as well... I'd advise
going to it as quickly as you feel comfortable.
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"mzeeshan" <mzeeshan@.yahoo.com> wrote in message
news:0fbe01c38a88$c3912300$a401280a@.phx.gbl...
> Hello everyone,
> We have upgraded to SQL Server 2000/sp2. When a service
> pack comes, generally companies wait for sometime before
> they apply. This is just to avoid potential new bugs and
> find out some information.
> My question is: Are there any known issues with SP3a? If
> yes, what they are and whether its safe to apply the
> patch.
> Thanks in advance,
> mzeeshan

Key cannot be null. Parameter name: key

We just upgraded to SS2005. After the upgrade, we can no longer create
subscriptions out of Execution Snapshot.
Try this experiment:
Create a report, with a simple SQL statement like "select * from CustomerDim
where CustomerPk = @.CustomerPk"
Go to Report Parameter, check the "Allow Null" box
Deploy the report
Go to the report on report server, render the report from Execution Snapshot
Now go to Subscription, and try to create a new subscription. The Parameter
CustomerPk will be grayed out, because of the Execution Snapshot
After you clicked OK, the subscription will return the error:
Key cannot be null. Parameter name: key
This error does not occur before the upgrade.
How can we create subscriptions out of Execution Snapshot in SS2005?
Thanks,
John WI've got the same problem. Did you find any solution?
Regards,
/Mattias
"LBJOHN" wrote:
> We just upgraded to SS2005. After the upgrade, we can no longer create
> subscriptions out of Execution Snapshot.
> Try this experiment:
> Create a report, with a simple SQL statement like "select * from CustomerDim
> where CustomerPk = @.CustomerPk"
> Go to Report Parameter, check the "Allow Null" box
> Deploy the report
> Go to the report on report server, render the report from Execution Snapshot
> Now go to Subscription, and try to create a new subscription. The Parameter
> CustomerPk will be grayed out, because of the Execution Snapshot
> After you clicked OK, the subscription will return the error:
> Key cannot be null. Parameter name: key
> This error does not occur before the upgrade.
> How can we create subscriptions out of Execution Snapshot in SS2005?
> Thanks,
> John W