Exceeding the 4G limit

Hi Andrea, I have this same issue on a production MOSS 2007 Intranet server
at school. How do I get around it? Can I add a new Database? I'm new to this
so if you know what to do to fix this issue without going to SQL 2005 server
then I'd appreciate knowing how
Thanks
Paul
Gold Coast
Oz
"Andrea Montanari" wrote:

> hi Jib,
> jib wrote:
> as Bill already stated, you'll stat gettinge "exceptions":
> Msg 1105:
> "Could not allocate space for object 'dbo.t' in database 'ext' because the
> 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files,
> dropping objects in the filegroup, adding additional files to the filegroup,
> or setting autogrowth on for existing files in the filegroup."
>
> the message can be little misleading and probably something similar to error
> 1827
> "CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative
> database size would exceed your licensed limit of %I64d MB per %S_MSG."
> could probably be a better "indicator" of the real problem, but such an
> exception has not been defined..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
>
Thanks Andrea, How do I split the 4GB database? I've tried to add a new
database but it still hits the 4GB limit. If you know how to split the
existing 4GB database in SQL Express then please let me know?
Many Thanks
Paul
"Andrea Montanari" wrote:

> hi Paul,
> Paul@.GoldCoast wrote:
> it's not legal to "hack" or workaround that limit of 2gb per database in
> MSDE and 4gb per database in SQLExpress...
> the only legal workaround is to split the database into more databases...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
>
|||Ah, the REAL answer here is to figure out how to use SQL Express within the
limitations. Invariably, an oversized database (one that's larger than 4GB)
contains binary large objects (BLOBs). IMHO, these should not be stored in
the database--and Microsoft agrees. That's why they're implementing the
FileStream datatype in Katmai (SS 2008). It's not hard to reengineer your
database to move the pictures and documents into a structured file system
(where they should be) and simply put pointers to the files in the database.
The result? Better performance (for about 6 reasons) and the ability to live
within the 4GB database size.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Paul@.GoldCoast" <PaulGoldCoast@.discussions.microsoft.com> wrote in message
news:B7DD9231-E00B-4A91-9EBB-85A5231F2D2E@.microsoft.com...[vbcol=seagreen]
> Hi Andrea, I have this same issue on a production MOSS 2007 Intranet
> server
> at school. How do I get around it? Can I add a new Database? I'm new to
> this
> so if you know what to do to fix this issue without going to SQL 2005
> server
> then I'd appreciate knowing how
> Thanks
> Paul
> Gold Coast
> Oz
> "Andrea Montanari" wrote: