Performance difference between Std & Enterprise Editions

Our main server is a Compaq Quad 700Mhz server with 4GB RAM and one instance
of SQLServer that was standard edition. We upgraded the SQLServer to
Enterprise edition and set the max memory to 3584MB. Performance is worse
now. Is this coincidental or should we expect it? Is there some other
setting that we need to do?
BTW, we implemented log shipping and found that the msdb DB did not contain
the tables and stored procedures we needed. Apparently the upgrade from Std
to Enterprise edition did not upgrade the msdb DB. We backed up an msdb DB
on another Enterprise SQLServer system and restored it on our main server.
The resored msdb DB has the tables and stored procedures we needed and we
were able to fire up the log shipping. Is this situation normal?
--
Picine KarppehdLook at the topics "UPDATE STATISTICS" and "Reading Pages" in Books Online.
The former will show you how to update the statistics on your database,
which may not be optimal after the upgrade. The latter describes "advanced
scan," a type of read-ahead I/O which Ent uses but Std doesn't, and may
account for some of the differences.
Might also see http://support.microsoft.com/?kbid=243589
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Picine Karppehd" <PicineKarppehd@.hotmail.com.(donotspam)> wrote in message
news:E1126808-7BF5-4802-A4FD-DACE5E8965A9@.microsoft.com...
> Our main server is a Compaq Quad 700Mhz server with 4GB RAM and one
instance
> of SQLServer that was standard edition. We upgraded the SQLServer to
> Enterprise edition and set the max memory to 3584MB. Performance is worse
> now. Is this coincidental or should we expect it? Is there some other
> setting that we need to do?
> BTW, we implemented log shipping and found that the msdb DB did not
contain
> the tables and stored procedures we needed. Apparently the upgrade from
Std
> to Enterprise edition did not upgrade the msdb DB. We backed up an msdb
DB
> on another Enterprise SQLServer system and restored it on our main server.
> The resored msdb DB has the tables and stored procedures we needed and we
> were able to fire up the log shipping. Is this situation normal?
> --
> Picine Karppehd
>