I know from experience that when the number of concurrent users on an MSDE
database exceeds the limit, an error is logged and the workload govenor
kicks in. Does something similar occur when the 2 GB limit is exceeded? I
had the experience yesterday where an application stopped responding for no
apparent reason. It's MSDE database was near 2 GB and the only thing we
could figure was that MSDE was trying to extend the database past 2GB.
Unfortunately there was no error logged, either from MSDE or from my
application.
MSDE will not allow you to extend the size of the database beyond 2GB. There
is no limit on the size of the log file, but there will be an inherent limit
on insert transactions due to the limit on the database size. If your
database has reached 2GB you should still be able to query data or perform
deletes or updates (as long as the update don't tigger an extent). If MSDE
failed to create an extent then there should be an log entry created in the
SQL Server log.
Jim
"Andy Walldorff" <andyw@.REMOVEsuperior.net> wrote in message
news:OfI6oIJHEHA.3288@.TK2MSFTNGP12.phx.gbl...
> I know from experience that when the number of concurrent users on an MSDE
> database exceeds the limit, an error is logged and the workload govenor
> kicks in. Does something similar occur when the 2 GB limit is exceeded?
I
> had the experience yesterday where an application stopped responding for
no
> apparent reason. It's MSDE database was near 2 GB and the only thing we
> could figure was that MSDE was trying to extend the database past 2GB.
> Unfortunately there was no error logged, either from MSDE or from my
> application.
>
|||Thanks
"Jim Young" <thorium48@.hotmail.com> wrote in message
news:uxhZEINHEHA.4092@.TK2MSFTNGP11.phx.gbl...
> MSDE will not allow you to extend the size of the database beyond 2GB.
There
> is no limit on the size of the log file, but there will be an inherent
limit
> on insert transactions due to the limit on the database size. If your
> database has reached 2GB you should still be able to query data or perform
> deletes or updates (as long as the update don't tigger an extent). If MSDE
> failed to create an extent then there should be an log entry created in
the
> SQL Server log.
> Jim
> "Andy Walldorff" <andyw@.REMOVEsuperior.net> wrote in message
> news:OfI6oIJHEHA.3288@.TK2MSFTNGP12.phx.gbl...
MSDE
> I
> no
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment