MSDE Performance verses SQL 2005 Express

I have been testing one of our Apps under SQL 2005 Express and I am seeing a big downgrade in performance compared to MSDE on the same hardware. Has anyone else experienced this?

Cheers

Aussie Coder

Hi Aussie Coder,

Could you give me an idea what specific tasks your testing and what the change in performance has been in your tests?

Regards,

Mike Wachal
SQL Express team

|||The tests involved loading a list control with a page of records and then using the down arrow key to scroll through a dataset of 2000 records. There is only enough records stored on the client side to fill the list control. I believe the data access engine I am using implements a server side cursor to access each record on an as needed basis. It also provides some buffering of the records, so it could be buffering 2 or three pages of records ahead, but this is transparent to my use of the engine. In my testing, the SQL Server was running on the same computer as the client app.

Under MSDE 2000 Release A, the scrolling is quite smooth and responsive. Under MSSQL 2005 Express, there is a noticable lag in the retrieval of records as the display page is updated.

The update process for scrolling down involves removing the top record from the page, retrieving the next record in sequence and adding it to the bottom of the page and then redrawing the list.

I hope this adds some light to what might be happening

Cheers
Aussie Coder|||

Getting back to this after a while, sorry. There was not any significant performance testing done comparing SQL Express and MSDE, so I can't offer much. I'm working on correcting this oversight, so I'll keep your scenario in mind as I push the team to do some comparisons.

Mike

|||Any new info on this? Our app does very similar caching for list controls.

MSDE Performance verses SQL 2005 Express

I have been testing one of our Apps under SQL 2005 Express and I am seeing a big downgrade in performance compared to MSDE on the same hardware. Has anyone else experienced this?

Cheers

Aussie Coder

Hi Aussie Coder,

Could you give me an idea what specific tasks your testing and what the change in performance has been in your tests?

Regards,

Mike Wachal
SQL Express team

|||The tests involved loading a list control with a page of records and then using the down arrow key to scroll through a dataset of 2000 records. There is only enough records stored on the client side to fill the list control. I believe the data access engine I am using implements a server side cursor to access each record on an as needed basis. It also provides some buffering of the records, so it could be buffering 2 or three pages of records ahead, but this is transparent to my use of the engine. In my testing, the SQL Server was running on the same computer as the client app.

Under MSDE 2000 Release A, the scrolling is quite smooth and responsive. Under MSSQL 2005 Express, there is a noticable lag in the retrieval of records as the display page is updated.

The update process for scrolling down involves removing the top record from the page, retrieving the next record in sequence and adding it to the bottom of the page and then redrawing the list.

I hope this adds some light to what might be happening

Cheers
Aussie Coder|||

Getting back to this after a while, sorry. There was not any significant performance testing done comparing SQL Express and MSDE, so I can't offer much. I'm working on correcting this oversight, so I'll keep your scenario in mind as I push the team to do some comparisons.

Mike

|||Any new info on this? Our app does very similar caching for list controls.

MSDE Performance verses SQL 2005 Express

I have been testing one of our Apps under SQL 2005 Express and I am seeing a big downgrade in performance compared to MSDE on the same hardware. Has anyone else experienced this?

Cheers

Aussie Coder

Hi Aussie Coder,

Could you give me an idea what specific tasks your testing and what the change in performance has been in your tests?

Regards,

Mike Wachal
SQL Express team

|||The tests involved loading a list control with a page of records and then using the down arrow key to scroll through a dataset of 2000 records. There is only enough records stored on the client side to fill the list control. I believe the data access engine I am using implements a server side cursor to access each record on an as needed basis. It also provides some buffering of the records, so it could be buffering 2 or three pages of records ahead, but this is transparent to my use of the engine. In my testing, the SQL Server was running on the same computer as the client app.

Under MSDE 2000 Release A, the scrolling is quite smooth and responsive. Under MSSQL 2005 Express, there is a noticable lag in the retrieval of records as the display page is updated.

The update process for scrolling down involves removing the top record from the page, retrieving the next record in sequence and adding it to the bottom of the page and then redrawing the list.

I hope this adds some light to what might be happening

Cheers
Aussie Coder

|||

Getting back to this after a while, sorry. There was not any significant performance testing done comparing SQL Express and MSDE, so I can't offer much. I'm working on correcting this oversight, so I'll keep your scenario in mind as I push the team to do some comparisons.

Mike

|||Any new info on this? Our app does very similar caching for list controls.sql

MSDE Limitations

What are the limitations of MSDE compared to SQL 2000?
tia,
Jim Evans
Thanks for the information, Anikan.
Jim Evans
"Anikan" <anonymous@.discussions.microsoft.com> wrote in message
news:1a8d01c4ad7f$17d25a50$a301280a@.phx.gbl...
>
> It's a scaled down version of sql 2000 but it doesn't
> mean its not as powerfull. It is scaled down to allow for
> it's easy redistribution. Clients might not need a full
> fledged SQL server and it may not seem feasible to
> purchase SQL Server for a small application but they
> might still need one? MSDE is limited to only 5
> concurrent database connections and is subject to various
> performance goveners. MSDE also has NO gui for
> administration such as SQL Enterprise Manager but it does
> come with various admin programs to accomplish those
> tasks (just not as pretty). Hope that helps.
>
|||There is additional information in these documents:
http://msdn.microsoft.com/library/de...ar_ts_67ax.asp
http://msdn.microsoft.com/library/de...asp?frame=true
http://msdn.microsoft.com/library/de...asp?frame=true
http://msdn.microsoft.com/library/de...asp?frame=true
http://www.microsoft.com/sql/msde/
Alan Brewer [MSFT]
Lead Programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
|||http://www.aspfaq.com/2343
http://www.aspfaq.com/2345
http://www.aspfaq.com/
(Reverse address to reply.)
"news.microsoft.com" <jim@.cabill.com> wrote in message
news:uAStEQXrEHA.3520@.TK2MSFTNGP11.phx.gbl...
> What are the limitations of MSDE compared to SQL 2000?
> tia,
> Jim Evans
>
|||Thanks, Aaron, some interesting information.
Jim Evans
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:e4BnOwwrEHA.3428@.TK2MSFTNGP11.phx.gbl...
> http://www.aspfaq.com/2343
> http://www.aspfaq.com/2345
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "news.microsoft.com" <jim@.cabill.com> wrote in message
> news:uAStEQXrEHA.3520@.TK2MSFTNGP11.phx.gbl...
>
|||| > might still need one? MSDE is limited to only 5
| > concurrent database connections and is subject to various
| > performance goveners.
That is pretty much wrong. There isn't such a limit, and the performance
governors don't have much effect at all. In a nutshell: after 8 concurrent
jobs, it gets hard to predict how long a query will take. In the real world,
that is the case for any server, pretty much even at 1 job. There isn't much
need to know how long a query will take, and good luck knowing when 10 of your
50 users will all load up the server at about the same time.
The 4 limits worth thinking about are: 1) 2 Gig db, 2) 2 CPUs 3) not all
replication options, 4) full text indexing.
Yes, it is very odd that MS makes such a powerful piece of software so easy to
get.
Carl K
|||> MSDE is limited to only 5
> concurrent database connections
Not true! Where do people get this mis-information? Please read the
following before providing "answers":
http://msdn.microsoft.com/library/en...r_sa2_0ciq.asp

> MSDE also has NO gui for
> administration such as SQL Enterprise Manager
No, but plenty of alternatives exist (several of them free):
http://www.aspfaq.com/2442
http://www.aspfaq.com/
(Reverse address to reply.)
|||Hi Aaron,
It's everywhere. Even Rory (now MS) said it the other day on Dot Net
Rocks...
Regards,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:O1KO226rEHA.3980@.TK2MSFTNGP12.phx.gbl...
> Not true! Where do people get this mis-information? Please read the
> following before providing "answers":
> http://msdn.microsoft.com/library/en...r_sa2_0ciq.asp
|||> It's everywhere. Even Rory (now MS) said it the other day on Dot Net
> Rocks...
*sigh*
I guess we'll always have "yes men" and very few people who actually read
the documentation or -- heaven forbid -- use the product.
:-(