I'm uploading a table to my Web Hosting Site that has 499 rows (big rows
because they have binary object in them).
After an hour or so of importing using a DTS package, I get the following
error:
Error at Destination for row number 499. could not allocate space for
object 'Pictures' in database "FamPhoto1' because the 'PRIMARY' filegroup is
full.
What could cause this error? All of the space allocations are defined in my
tables? is my web hoster out of space?
Thanks,
GChances are the file was simply not big enough to hold the data you were
trying to import. As such it would attempt to autogrow. If the time it
takes to autogrow is longer than the timeout of the client that initiated
the autogrow it will timeout. That may roll back the autogrow and put you
back to where you started. Always ensure you have plenty of free space in
the db before attempting any operation such as that. Manually grow the
file(s) and you should be all set.
--
Andrew J. Kelly SQL MVP
"G Dean Blake" <gb@.nospam.com> wrote in message
news:eh54jjUMFHA.2604@.TK2MSFTNGP10.phx.gbl...
> I'm uploading a table to my Web Hosting Site that has 499 rows (big rows
> because they have binary object in them).
> After an hour or so of importing using a DTS package, I get the following
> error:
> Error at Destination for row number 499. could not allocate space for
> object 'Pictures' in database "FamPhoto1' because the 'PRIMARY' filegroup
> is full.
> What could cause this error? All of the space allocations are defined in
> my tables? is my web hoster out of space?
> Thanks,
> G
>|||What I don't understand is ...
The Webhoster set up an empty database for me, just the system tables - no
user tables. I have the database on my computer and it works just fine and,
apparently, all of my tables fit into the primary file group just fine. I'm
using the IMPORT to transfer four tables to the webhoster database. If my
tables have plenty of space to work well and they all fit on my computer,
why is there not enough space on the target computer?
When a table is "imported" to another database, what determines how much
space that table will be allocated?
G
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uxX0fHVMFHA.1392@.TK2MSFTNGP10.phx.gbl...
> Chances are the file was simply not big enough to hold the data you were
> trying to import. As such it would attempt to autogrow. If the time it
> takes to autogrow is longer than the timeout of the client that initiated
> the autogrow it will timeout. That may roll back the autogrow and put you
> back to where you started. Always ensure you have plenty of free space in
> the db before attempting any operation such as that. Manually grow the
> file(s) and you should be all set.
> --
> Andrew J. Kelly SQL MVP
>
> "G Dean Blake" <gb@.nospam.com> wrote in message
> news:eh54jjUMFHA.2604@.TK2MSFTNGP10.phx.gbl...
>> I'm uploading a table to my Web Hosting Site that has 499 rows (big rows
>> because they have binary object in them).
>> After an hour or so of importing using a DTS package, I get the following
>> error:
>> Error at Destination for row number 499. could not allocate space for
>> object 'Pictures' in database "FamPhoto1' because the 'PRIMARY' filegroup
>> is full.
>> What could cause this error? All of the space allocations are defined in
>> my tables? is my web hoster out of space?
>> Thanks,
>> G
>|||Well it could be that the drive that the primary filegroup is located on for
the Web site is low on space and yours isn't. It could be your db is
slightly different than the one on the web (indexes, size, recovery model
etc). How large is your primary file vs. the one on the web? Did you try
to grow it manually and see if it errors? The amount of space is dependant
mainly on the size and type of data being imported. The indexexing can play
a large roles as well especially if the clustered index is such that it will
cause page splits when you insert.
--
Andrew J. Kelly SQL MVP
"G Dean Blake" <gb@.nospam.com> wrote in message
news:uRaTXRVMFHA.2252@.TK2MSFTNGP15.phx.gbl...
> What I don't understand is ...
> The Webhoster set up an empty database for me, just the system tables - no
> user tables. I have the database on my computer and it works just fine
> and, apparently, all of my tables fit into the primary file group just
> fine. I'm using the IMPORT to transfer four tables to the webhoster
> database. If my tables have plenty of space to work well and they all fit
> on my computer, why is there not enough space on the target computer?
> When a table is "imported" to another database, what determines how much
> space that table will be allocated?
> G
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:uxX0fHVMFHA.1392@.TK2MSFTNGP10.phx.gbl...
>> Chances are the file was simply not big enough to hold the data you were
>> trying to import. As such it would attempt to autogrow. If the time it
>> takes to autogrow is longer than the timeout of the client that initiated
>> the autogrow it will timeout. That may roll back the autogrow and put
>> you back to where you started. Always ensure you have plenty of free
>> space in the db before attempting any operation such as that. Manually
>> grow the file(s) and you should be all set.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "G Dean Blake" <gb@.nospam.com> wrote in message
>> news:eh54jjUMFHA.2604@.TK2MSFTNGP10.phx.gbl...
>> I'm uploading a table to my Web Hosting Site that has 499 rows (big rows
>> because they have binary object in them).
>> After an hour or so of importing using a DTS package, I get the
>> following error:
>> Error at Destination for row number 499. could not allocate space for
>> object 'Pictures' in database "FamPhoto1' because the 'PRIMARY'
>> filegroup is full.
>> What could cause this error? All of the space allocations are defined
>> in my tables? is my web hoster out of space?
>> Thanks,
>> G
>>
>|||Hi Andrew
I am suffering form the same mesage "PRIMARY File group is full" even though
there is about 20GB of space on my hard drive and the DB is set to Autogrow.
So space is not the issue.
You suggested manually growng the DB, but can you expalin how I would do this.
Cheers
Coburndavis
"Andrew J. Kelly" wrote:
> Well it could be that the drive that the primary filegroup is located on for
> the Web site is low on space and yours isn't. It could be your db is
> slightly different than the one on the web (indexes, size, recovery model
> etc). How large is your primary file vs. the one on the web? Did you try
> to grow it manually and see if it errors? The amount of space is dependant
> mainly on the size and type of data being imported. The indexexing can play
> a large roles as well especially if the clustered index is such that it will
> cause page splits when you insert.
> --
> Andrew J. Kelly SQL MVP
>
> "G Dean Blake" <gb@.nospam.com> wrote in message
> news:uRaTXRVMFHA.2252@.TK2MSFTNGP15.phx.gbl...
> >
> > What I don't understand is ...
> >
> > The Webhoster set up an empty database for me, just the system tables - no
> > user tables. I have the database on my computer and it works just fine
> > and, apparently, all of my tables fit into the primary file group just
> > fine. I'm using the IMPORT to transfer four tables to the webhoster
> > database. If my tables have plenty of space to work well and they all fit
> > on my computer, why is there not enough space on the target computer?
> >
> > When a table is "imported" to another database, what determines how much
> > space that table will be allocated?
> > G
> >
> >
> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> > news:uxX0fHVMFHA.1392@.TK2MSFTNGP10.phx.gbl...
> >> Chances are the file was simply not big enough to hold the data you were
> >> trying to import. As such it would attempt to autogrow. If the time it
> >> takes to autogrow is longer than the timeout of the client that initiated
> >> the autogrow it will timeout. That may roll back the autogrow and put
> >> you back to where you started. Always ensure you have plenty of free
> >> space in the db before attempting any operation such as that. Manually
> >> grow the file(s) and you should be all set.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >>
> >>
> >> "G Dean Blake" <gb@.nospam.com> wrote in message
> >> news:eh54jjUMFHA.2604@.TK2MSFTNGP10.phx.gbl...
> >> I'm uploading a table to my Web Hosting Site that has 499 rows (big rows
> >> because they have binary object in them).
> >> After an hour or so of importing using a DTS package, I get the
> >> following error:
> >>
> >> Error at Destination for row number 499. could not allocate space for
> >> object 'Pictures' in database "FamPhoto1' because the 'PRIMARY'
> >> filegroup is full.
> >>
> >> What could cause this error? All of the space allocations are defined
> >> in my tables? is my web hoster out of space?
> >> Thanks,
> >> G
> >>
> >>
> >>
> >
> >
>
>|||> You suggested manually growng the DB, but can you expalin how I would do this.
ALTER DATABASE dbname MODIFY FILE ( NAME = logical_file_name, SIZE = <desired size>)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"COBURNDAVIS" <COBURNDAVIS@.discussions.microsoft.com> wrote in message
news:AF941E5B-58BF-42F5-8100-B7B5517CCAD4@.microsoft.com...
> Hi Andrew
> I am suffering form the same mesage "PRIMARY File group is full" even though
> there is about 20GB of space on my hard drive and the DB is set to Autogrow.
> So space is not the issue.
> You suggested manually growng the DB, but can you expalin how I would do this.
> Cheers
> Coburndavis
>
> "Andrew J. Kelly" wrote:
>> Well it could be that the drive that the primary filegroup is located on for
>> the Web site is low on space and yours isn't. It could be your db is
>> slightly different than the one on the web (indexes, size, recovery model
>> etc). How large is your primary file vs. the one on the web? Did you try
>> to grow it manually and see if it errors? The amount of space is dependant
>> mainly on the size and type of data being imported. The indexexing can play
>> a large roles as well especially if the clustered index is such that it will
>> cause page splits when you insert.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "G Dean Blake" <gb@.nospam.com> wrote in message
>> news:uRaTXRVMFHA.2252@.TK2MSFTNGP15.phx.gbl...
>> >
>> > What I don't understand is ...
>> >
>> > The Webhoster set up an empty database for me, just the system tables - no
>> > user tables. I have the database on my computer and it works just fine
>> > and, apparently, all of my tables fit into the primary file group just
>> > fine. I'm using the IMPORT to transfer four tables to the webhoster
>> > database. If my tables have plenty of space to work well and they all fit
>> > on my computer, why is there not enough space on the target computer?
>> >
>> > When a table is "imported" to another database, what determines how much
>> > space that table will be allocated?
>> > G
>> >
>> >
>> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> > news:uxX0fHVMFHA.1392@.TK2MSFTNGP10.phx.gbl...
>> >> Chances are the file was simply not big enough to hold the data you were
>> >> trying to import. As such it would attempt to autogrow. If the time it
>> >> takes to autogrow is longer than the timeout of the client that initiated
>> >> the autogrow it will timeout. That may roll back the autogrow and put
>> >> you back to where you started. Always ensure you have plenty of free
>> >> space in the db before attempting any operation such as that. Manually
>> >> grow the file(s) and you should be all set.
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >>
>> >>
>> >> "G Dean Blake" <gb@.nospam.com> wrote in message
>> >> news:eh54jjUMFHA.2604@.TK2MSFTNGP10.phx.gbl...
>> >> I'm uploading a table to my Web Hosting Site that has 499 rows (big rows
>> >> because they have binary object in them).
>> >> After an hour or so of importing using a DTS package, I get the
>> >> following error:
>> >>
>> >> Error at Destination for row number 499. could not allocate space for
>> >> object 'Pictures' in database "FamPhoto1' because the 'PRIMARY'
>> >> filegroup is full.
>> >>
>> >> What could cause this error? All of the space allocations are defined
>> >> in my tables? is my web hoster out of space?
>> >> Thanks,
>> >> G
>> >>
>> >>
>> >>
>> >
>> >
>>|||If space is NOT an issue and you are truely set to AUTOGROW, then I suspect
you current database size is, hmmm, about, what? 2 GB?
If so, then you are using MSDE and just found one of the restrictions of
that edition. The only known solution is to upgrade to a Server-Class
edition or split your database into multiple databases...hey, just like you
would do with MS Access. Sound familiar? That's why MSDE stands for MS
Desktop Edition, it is a personal replacement or alternative to MS Access,
but not for Server-class, production, Client/Server or n-Tier solutions,
only Standard and Enterprise Editions are, and now, the new Workgroup
Edition?although, WE has its own restrictions.
Now, the Web Host sounds suspicious. I don't believe anyone would attempt
to run MSDE as a hosted edition. Are you on a dedicated server or are you
sharing? Do you know if the hosted database is set to AUTOGROW or not? Do
you know how much free space is on the drives for the hosted server? Do you
know if the ISP has quotas turned on for you data file folders?usually, you
would get a different error message if this were the case, but I would check
anyway?
Sincerely,
Anthony Thomas
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:ObeUpDUYFHA.3320@.TK2MSFTNGP12.phx.gbl...
> You suggested manually growng the DB, but can you expalin how I would do
this.
ALTER DATABASE dbname MODIFY FILE ( NAME = logical_file_name, SIZE =<desired size>)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"COBURNDAVIS" <COBURNDAVIS@.discussions.microsoft.com> wrote in message
news:AF941E5B-58BF-42F5-8100-B7B5517CCAD4@.microsoft.com...
> Hi Andrew
> I am suffering form the same mesage "PRIMARY File group is full" even
though
> there is about 20GB of space on my hard drive and the DB is set to
Autogrow.
> So space is not the issue.
> You suggested manually growng the DB, but can you expalin how I would do
this.
> Cheers
> Coburndavis
>
> "Andrew J. Kelly" wrote:
>> Well it could be that the drive that the primary filegroup is located on
for
>> the Web site is low on space and yours isn't. It could be your db is
>> slightly different than the one on the web (indexes, size, recovery model
>> etc). How large is your primary file vs. the one on the web? Did you
try
>> to grow it manually and see if it errors? The amount of space is
dependant
>> mainly on the size and type of data being imported. The indexexing can
play
>> a large roles as well especially if the clustered index is such that it
will
>> cause page splits when you insert.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "G Dean Blake" <gb@.nospam.com> wrote in message
>> news:uRaTXRVMFHA.2252@.TK2MSFTNGP15.phx.gbl...
>> >
>> > What I don't understand is ...
>> >
>> > The Webhoster set up an empty database for me, just the system tables -
no
>> > user tables. I have the database on my computer and it works just fine
>> > and, apparently, all of my tables fit into the primary file group just
>> > fine. I'm using the IMPORT to transfer four tables to the webhoster
>> > database. If my tables have plenty of space to work well and they all
fit
>> > on my computer, why is there not enough space on the target computer?
>> >
>> > When a table is "imported" to another database, what determines how
much
>> > space that table will be allocated?
>> > G
>> >
>> >
>> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> > news:uxX0fHVMFHA.1392@.TK2MSFTNGP10.phx.gbl...
>> >> Chances are the file was simply not big enough to hold the data you
were
>> >> trying to import. As such it would attempt to autogrow. If the time
it
>> >> takes to autogrow is longer than the timeout of the client that
initiated
>> >> the autogrow it will timeout. That may roll back the autogrow and put
>> >> you back to where you started. Always ensure you have plenty of free
>> >> space in the db before attempting any operation such as that.
Manually
>> >> grow the file(s) and you should be all set.
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >>
>> >>
>> >> "G Dean Blake" <gb@.nospam.com> wrote in message
>> >> news:eh54jjUMFHA.2604@.TK2MSFTNGP10.phx.gbl...
>> >> I'm uploading a table to my Web Hosting Site that has 499 rows (big
rows
>> >> because they have binary object in them).
>> >> After an hour or so of importing using a DTS package, I get the
>> >> following error:
>> >>
>> >> Error at Destination for row number 499. could not allocate space
for
>> >> object 'Pictures' in database "FamPhoto1' because the 'PRIMARY'
>> >> filegroup is full.
>> >>
>> >> What could cause this error? All of the space allocations are
defined
>> >> in my tables? is my web hoster out of space?
>> >> Thanks,
>> >> G
>> >>
>> >>
>> >>
>> >
>> >
>>|||For what it's worth, using the FAT file system caps file sizes to a few GB
(3 or 4GB, I forget
the exact size). Worth checking out?
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:u7w8CaGaFHA.3488@.tk2msftngp13.phx.gbl...
> If space is NOT an issue and you are truely set to AUTOGROW, then I
suspect
> you current database size is, hmmm, about, what? 2 GB?
> If so, then you are using MSDE and just found one of the restrictions of
> that edition. The only known solution is to upgrade to a Server-Class
> edition or split your database into multiple databases...hey, just like
you
> would do with MS Access. Sound familiar? That's why MSDE stands for MS
> Desktop Edition, it is a personal replacement or alternative to MS Access,
> but not for Server-class, production, Client/Server or n-Tier solutions,
> only Standard and Enterprise Editions are, and now, the new Workgroup
> Edition-although, WE has its own restrictions.
> Now, the Web Host sounds suspicious. I don't believe anyone would attempt
> to run MSDE as a hosted edition. Are you on a dedicated server or are you
> sharing? Do you know if the hosted database is set to AUTOGROW or not?
Do
> you know how much free space is on the drives for the hosted server? Do
you
> know if the ISP has quotas turned on for you data file folders-usually,
you
> would get a different error message if this were the case, but I would
check
> anyway?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
in
> message news:ObeUpDUYFHA.3320@.TK2MSFTNGP12.phx.gbl...
> > You suggested manually growng the DB, but can you expalin how I would do
> this.
> ALTER DATABASE dbname MODIFY FILE ( NAME = logical_file_name, SIZE => <desired size>)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "COBURNDAVIS" <COBURNDAVIS@.discussions.microsoft.com> wrote in message
> news:AF941E5B-58BF-42F5-8100-B7B5517CCAD4@.microsoft.com...
> > Hi Andrew
> >
> > I am suffering form the same mesage "PRIMARY File group is full" even
> though
> > there is about 20GB of space on my hard drive and the DB is set to
> Autogrow.
> > So space is not the issue.
> >
> > You suggested manually growng the DB, but can you expalin how I would do
> this.
> >
> > Cheers
> >
> > Coburndavis
> >
> >
> > "Andrew J. Kelly" wrote:
> >
> >> Well it could be that the drive that the primary filegroup is located
on
> for
> >> the Web site is low on space and yours isn't. It could be your db is
> >> slightly different than the one on the web (indexes, size, recovery
model
> >> etc). How large is your primary file vs. the one on the web? Did you
> try
> >> to grow it manually and see if it errors? The amount of space is
> dependant
> >> mainly on the size and type of data being imported. The indexexing can
> play
> >> a large roles as well especially if the clustered index is such that it
> will
> >> cause page splits when you insert.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >>
> >>
> >> "G Dean Blake" <gb@.nospam.com> wrote in message
> >> news:uRaTXRVMFHA.2252@.TK2MSFTNGP15.phx.gbl...
> >> >
> >> > What I don't understand is ...
> >> >
> >> > The Webhoster set up an empty database for me, just the system
tables -
> no
> >> > user tables. I have the database on my computer and it works just
fine
> >> > and, apparently, all of my tables fit into the primary file group
just
> >> > fine. I'm using the IMPORT to transfer four tables to the webhoster
> >> > database. If my tables have plenty of space to work well and they
all
> fit
> >> > on my computer, why is there not enough space on the target computer?
> >> >
> >> > When a table is "imported" to another database, what determines how
> much
> >> > space that table will be allocated?
> >> > G
> >> >
> >> >
> >> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> >> > news:uxX0fHVMFHA.1392@.TK2MSFTNGP10.phx.gbl...
> >> >> Chances are the file was simply not big enough to hold the data you
> were
> >> >> trying to import. As such it would attempt to autogrow. If the
time
> it
> >> >> takes to autogrow is longer than the timeout of the client that
> initiated
> >> >> the autogrow it will timeout. That may roll back the autogrow and
put
> >> >> you back to where you started. Always ensure you have plenty of
free
> >> >> space in the db before attempting any operation such as that.
> Manually
> >> >> grow the file(s) and you should be all set.
> >> >>
> >> >> --
> >> >> Andrew J. Kelly SQL MVP
> >> >>
> >> >>
> >> >> "G Dean Blake" <gb@.nospam.com> wrote in message
> >> >> news:eh54jjUMFHA.2604@.TK2MSFTNGP10.phx.gbl...
> >> >> I'm uploading a table to my Web Hosting Site that has 499 rows (big
> rows
> >> >> because they have binary object in them).
> >> >> After an hour or so of importing using a DTS package, I get the
> >> >> following error:
> >> >>
> >> >> Error at Destination for row number 499. could not allocate space
> for
> >> >> object 'Pictures' in database "FamPhoto1' because the 'PRIMARY'
> >> >> filegroup is full.
> >> >>
> >> >> What could cause this error? All of the space allocations are
> defined
> >> >> in my tables? is my web hoster out of space?
> >> >> Thanks,
> >> >> G
> >> >>
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >>
>|||> If so, then you are using MSDE and just found one of the restrictions of
> that edition.
If my memory serves me, you get some other error message of you reach max data size on MSDE. Not
sure, though...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message news:u7w8CaGaFHA.3488@.tk2msftngp13.phx.gbl...
> If space is NOT an issue and you are truely set to AUTOGROW, then I suspect
> you current database size is, hmmm, about, what? 2 GB?
> If so, then you are using MSDE and just found one of the restrictions of
> that edition. The only known solution is to upgrade to a Server-Class
> edition or split your database into multiple databases...hey, just like you
> would do with MS Access. Sound familiar? That's why MSDE stands for MS
> Desktop Edition, it is a personal replacement or alternative to MS Access,
> but not for Server-class, production, Client/Server or n-Tier solutions,
> only Standard and Enterprise Editions are, and now, the new Workgroup
> Edition-although, WE has its own restrictions.
> Now, the Web Host sounds suspicious. I don't believe anyone would attempt
> to run MSDE as a hosted edition. Are you on a dedicated server or are you
> sharing? Do you know if the hosted database is set to AUTOGROW or not? Do
> you know how much free space is on the drives for the hosted server? Do you
> know if the ISP has quotas turned on for you data file folders-usually, you
> would get a different error message if this were the case, but I would check
> anyway?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:ObeUpDUYFHA.3320@.TK2MSFTNGP12.phx.gbl...
>> You suggested manually growng the DB, but can you expalin how I would do
> this.
> ALTER DATABASE dbname MODIFY FILE ( NAME = logical_file_name, SIZE => <desired size>)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "COBURNDAVIS" <COBURNDAVIS@.discussions.microsoft.com> wrote in message
> news:AF941E5B-58BF-42F5-8100-B7B5517CCAD4@.microsoft.com...
>> Hi Andrew
>> I am suffering form the same mesage "PRIMARY File group is full" even
> though
>> there is about 20GB of space on my hard drive and the DB is set to
> Autogrow.
>> So space is not the issue.
>> You suggested manually growng the DB, but can you expalin how I would do
> this.
>> Cheers
>> Coburndavis
>>
>> "Andrew J. Kelly" wrote:
>> Well it could be that the drive that the primary filegroup is located on
> for
>> the Web site is low on space and yours isn't. It could be your db is
>> slightly different than the one on the web (indexes, size, recovery model
>> etc). How large is your primary file vs. the one on the web? Did you
> try
>> to grow it manually and see if it errors? The amount of space is
> dependant
>> mainly on the size and type of data being imported. The indexexing can
> play
>> a large roles as well especially if the clustered index is such that it
> will
>> cause page splits when you insert.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "G Dean Blake" <gb@.nospam.com> wrote in message
>> news:uRaTXRVMFHA.2252@.TK2MSFTNGP15.phx.gbl...
>> >
>> > What I don't understand is ...
>> >
>> > The Webhoster set up an empty database for me, just the system tables -
> no
>> > user tables. I have the database on my computer and it works just fine
>> > and, apparently, all of my tables fit into the primary file group just
>> > fine. I'm using the IMPORT to transfer four tables to the webhoster
>> > database. If my tables have plenty of space to work well and they all
> fit
>> > on my computer, why is there not enough space on the target computer?
>> >
>> > When a table is "imported" to another database, what determines how
> much
>> > space that table will be allocated?
>> > G
>> >
>> >
>> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> > news:uxX0fHVMFHA.1392@.TK2MSFTNGP10.phx.gbl...
>> >> Chances are the file was simply not big enough to hold the data you
> were
>> >> trying to import. As such it would attempt to autogrow. If the time
> it
>> >> takes to autogrow is longer than the timeout of the client that
> initiated
>> >> the autogrow it will timeout. That may roll back the autogrow and put
>> >> you back to where you started. Always ensure you have plenty of free
>> >> space in the db before attempting any operation such as that.
> Manually
>> >> grow the file(s) and you should be all set.
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >>
>> >>
>> >> "G Dean Blake" <gb@.nospam.com> wrote in message
>> >> news:eh54jjUMFHA.2604@.TK2MSFTNGP10.phx.gbl...
>> >> I'm uploading a table to my Web Hosting Site that has 499 rows (big
> rows
>> >> because they have binary object in them).
>> >> After an hour or so of importing using a DTS package, I get the
>> >> following error:
>> >>
>> >> Error at Destination for row number 499. could not allocate space
> for
>> >> object 'Pictures' in database "FamPhoto1' because the 'PRIMARY'
>> >> filegroup is full.
>> >>
>> >> What could cause this error? All of the space allocations are
> defined
>> >> in my tables? is my web hoster out of space?
>> >> Thanks,
>> >> G
>> >>
>> >>
>> >>
>> >
>> >
>>
>|||Nope, that's the exact error message. Unfortunately though, MSDE maximum
size is not necessarily the only possible cause. You do get a different
error message if you max out your 8 concurrent connections, but this is the
message for the Database Size restriciton. Only because I wrestled with a
System Admin for about an hour one time before he brought that little tidbit
of information to my attention...then all became clear.
That and the fact that we are talking about an ISP system would beg this
question, but I would certainly ask or at least query the system to find
out.
Sincerely,
Anthony Thomas
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23uL2kFcaFHA.720@.TK2MSFTNGP15.phx.gbl...
> If so, then you are using MSDE and just found one of the restrictions of
> that edition.
If my memory serves me, you get some other error message of you reach max
data size on MSDE. Not
sure, though...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:u7w8CaGaFHA.3488@.tk2msftngp13.phx.gbl...
> If space is NOT an issue and you are truely set to AUTOGROW, then I
suspect
> you current database size is, hmmm, about, what? 2 GB?
> If so, then you are using MSDE and just found one of the restrictions of
> that edition. The only known solution is to upgrade to a Server-Class
> edition or split your database into multiple databases...hey, just like
you
> would do with MS Access. Sound familiar? That's why MSDE stands for MS
> Desktop Edition, it is a personal replacement or alternative to MS Access,
> but not for Server-class, production, Client/Server or n-Tier solutions,
> only Standard and Enterprise Editions are, and now, the new Workgroup
> Edition-although, WE has its own restrictions.
> Now, the Web Host sounds suspicious. I don't believe anyone would attempt
> to run MSDE as a hosted edition. Are you on a dedicated server or are you
> sharing? Do you know if the hosted database is set to AUTOGROW or not?
Do
> you know how much free space is on the drives for the hosted server? Do
you
> know if the ISP has quotas turned on for you data file folders-usually,
you
> would get a different error message if this were the case, but I would
check
> anyway?
> Sincerely,
>
> Anthony Thomas
>
> --
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
in
> message news:ObeUpDUYFHA.3320@.TK2MSFTNGP12.phx.gbl...
>> You suggested manually growng the DB, but can you expalin how I would do
> this.
> ALTER DATABASE dbname MODIFY FILE ( NAME = logical_file_name, SIZE => <desired size>)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "COBURNDAVIS" <COBURNDAVIS@.discussions.microsoft.com> wrote in message
> news:AF941E5B-58BF-42F5-8100-B7B5517CCAD4@.microsoft.com...
>> Hi Andrew
>> I am suffering form the same mesage "PRIMARY File group is full" even
> though
>> there is about 20GB of space on my hard drive and the DB is set to
> Autogrow.
>> So space is not the issue.
>> You suggested manually growng the DB, but can you expalin how I would do
> this.
>> Cheers
>> Coburndavis
>>
>> "Andrew J. Kelly" wrote:
>> Well it could be that the drive that the primary filegroup is located on
> for
>> the Web site is low on space and yours isn't. It could be your db is
>> slightly different than the one on the web (indexes, size, recovery
model
>> etc). How large is your primary file vs. the one on the web? Did you
> try
>> to grow it manually and see if it errors? The amount of space is
> dependant
>> mainly on the size and type of data being imported. The indexexing can
> play
>> a large roles as well especially if the clustered index is such that it
> will
>> cause page splits when you insert.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "G Dean Blake" <gb@.nospam.com> wrote in message
>> news:uRaTXRVMFHA.2252@.TK2MSFTNGP15.phx.gbl...
>> >
>> > What I don't understand is ...
>> >
>> > The Webhoster set up an empty database for me, just the system
tables -
> no
>> > user tables. I have the database on my computer and it works just
fine
>> > and, apparently, all of my tables fit into the primary file group just
>> > fine. I'm using the IMPORT to transfer four tables to the webhoster
>> > database. If my tables have plenty of space to work well and they all
> fit
>> > on my computer, why is there not enough space on the target computer?
>> >
>> > When a table is "imported" to another database, what determines how
> much
>> > space that table will be allocated?
>> > G
>> >
>> >
>> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> > news:uxX0fHVMFHA.1392@.TK2MSFTNGP10.phx.gbl...
>> >> Chances are the file was simply not big enough to hold the data you
> were
>> >> trying to import. As such it would attempt to autogrow. If the time
> it
>> >> takes to autogrow is longer than the timeout of the client that
> initiated
>> >> the autogrow it will timeout. That may roll back the autogrow and
put
>> >> you back to where you started. Always ensure you have plenty of free
>> >> space in the db before attempting any operation such as that.
> Manually
>> >> grow the file(s) and you should be all set.
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >>
>> >>
>> >> "G Dean Blake" <gb@.nospam.com> wrote in message
>> >> news:eh54jjUMFHA.2604@.TK2MSFTNGP10.phx.gbl...
>> >> I'm uploading a table to my Web Hosting Site that has 499 rows (big
> rows
>> >> because they have binary object in them).
>> >> After an hour or so of importing using a DTS package, I get the
>> >> following error:
>> >>
>> >> Error at Destination for row number 499. could not allocate space
> for
>> >> object 'Pictures' in database "FamPhoto1' because the 'PRIMARY'
>> >> filegroup is full.
>> >>
>> >> What could cause this error? All of the space allocations are
> defined
>> >> in my tables? is my web hoster out of space?
>> >> Thanks,
>> >> G
>> >>
>> >>
>> >>
>> >
>> >
>>
>|||> Nope, that's the exact error message.
Thanks for the confirmation, Anthony.
And I agree that it would be surprising if the ISP run on an MSDE, but you have seen stranger things
before. :-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:%23aJaEFiaFHA.1040@.TK2MSFTNGP10.phx.gbl...
> Nope, that's the exact error message. Unfortunately though, MSDE maximum
> size is not necessarily the only possible cause. You do get a different
> error message if you max out your 8 concurrent connections, but this is the
> message for the Database Size restriciton. Only because I wrestled with a
> System Admin for about an hour one time before he brought that little tidbit
> of information to my attention...then all became clear.
> That and the fact that we are talking about an ISP system would beg this
> question, but I would certainly ask or at least query the system to find
> out.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:%23uL2kFcaFHA.720@.TK2MSFTNGP15.phx.gbl...
>> If so, then you are using MSDE and just found one of the restrictions of
>> that edition.
> If my memory serves me, you get some other error message of you reach max
> data size on MSDE. Not
> sure, though...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
> news:u7w8CaGaFHA.3488@.tk2msftngp13.phx.gbl...
>> If space is NOT an issue and you are truely set to AUTOGROW, then I
> suspect
>> you current database size is, hmmm, about, what? 2 GB?
>> If so, then you are using MSDE and just found one of the restrictions of
>> that edition. The only known solution is to upgrade to a Server-Class
>> edition or split your database into multiple databases...hey, just like
> you
>> would do with MS Access. Sound familiar? That's why MSDE stands for MS
>> Desktop Edition, it is a personal replacement or alternative to MS Access,
>> but not for Server-class, production, Client/Server or n-Tier solutions,
>> only Standard and Enterprise Editions are, and now, the new Workgroup
>> Edition-although, WE has its own restrictions.
>> Now, the Web Host sounds suspicious. I don't believe anyone would attempt
>> to run MSDE as a hosted edition. Are you on a dedicated server or are you
>> sharing? Do you know if the hosted database is set to AUTOGROW or not?
> Do
>> you know how much free space is on the drives for the hosted server? Do
> you
>> know if the ISP has quotas turned on for you data file folders-usually,
> you
>> would get a different error message if this were the case, but I would
> check
>> anyway?
>> Sincerely,
>>
>> Anthony Thomas
>>
>> --
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in
>> message news:ObeUpDUYFHA.3320@.TK2MSFTNGP12.phx.gbl...
>> You suggested manually growng the DB, but can you expalin how I would do
>> this.
>> ALTER DATABASE dbname MODIFY FILE ( NAME = logical_file_name, SIZE =>> <desired size>)
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "COBURNDAVIS" <COBURNDAVIS@.discussions.microsoft.com> wrote in message
>> news:AF941E5B-58BF-42F5-8100-B7B5517CCAD4@.microsoft.com...
>> Hi Andrew
>> I am suffering form the same mesage "PRIMARY File group is full" even
>> though
>> there is about 20GB of space on my hard drive and the DB is set to
>> Autogrow.
>> So space is not the issue.
>> You suggested manually growng the DB, but can you expalin how I would do
>> this.
>> Cheers
>> Coburndavis
>>
>> "Andrew J. Kelly" wrote:
>> Well it could be that the drive that the primary filegroup is located on
>> for
>> the Web site is low on space and yours isn't. It could be your db is
>> slightly different than the one on the web (indexes, size, recovery
> model
>> etc). How large is your primary file vs. the one on the web? Did you
>> try
>> to grow it manually and see if it errors? The amount of space is
>> dependant
>> mainly on the size and type of data being imported. The indexexing can
>> play
>> a large roles as well especially if the clustered index is such that it
>> will
>> cause page splits when you insert.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "G Dean Blake" <gb@.nospam.com> wrote in message
>> news:uRaTXRVMFHA.2252@.TK2MSFTNGP15.phx.gbl...
>> >
>> > What I don't understand is ...
>> >
>> > The Webhoster set up an empty database for me, just the system
> tables -
>> no
>> > user tables. I have the database on my computer and it works just
> fine
>> > and, apparently, all of my tables fit into the primary file group just
>> > fine. I'm using the IMPORT to transfer four tables to the webhoster
>> > database. If my tables have plenty of space to work well and they all
>> fit
>> > on my computer, why is there not enough space on the target computer?
>> >
>> > When a table is "imported" to another database, what determines how
>> much
>> > space that table will be allocated?
>> > G
>> >
>> >
>> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> > news:uxX0fHVMFHA.1392@.TK2MSFTNGP10.phx.gbl...
>> >> Chances are the file was simply not big enough to hold the data you
>> were
>> >> trying to import. As such it would attempt to autogrow. If the time
>> it
>> >> takes to autogrow is longer than the timeout of the client that
>> initiated
>> >> the autogrow it will timeout. That may roll back the autogrow and
> put
>> >> you back to where you started. Always ensure you have plenty of free
>> >> space in the db before attempting any operation such as that.
>> Manually
>> >> grow the file(s) and you should be all set.
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >>
>> >>
>> >> "G Dean Blake" <gb@.nospam.com> wrote in message
>> >> news:eh54jjUMFHA.2604@.TK2MSFTNGP10.phx.gbl...
>> >> I'm uploading a table to my Web Hosting Site that has 499 rows (big
>> rows
>> >> because they have binary object in them).
>> >> After an hour or so of importing using a DTS package, I get the
>> >> following error:
>> >>
>> >> Error at Destination for row number 499. could not allocate space
>> for
>> >> object 'Pictures' in database "FamPhoto1' because the 'PRIMARY'
>> >> filegroup is full.
>> >>
>> >> What could cause this error? All of the space allocations are
>> defined
>> >> in my tables? is my web hoster out of space?
>> >> Thanks,
>> >> G
>> >>
>> >>
>> >>
>> >
>> >
>>
>>
>|||Try this:
Right click on database in question. Select Properties. Then go to 'Data
Files' Tab.
Under the Location Column click on the Elipse Button (the grey square with
the three dots!!)
Go to the path where you .MDF's are saved (usually program Files\Microsoft
SQL Server\MSSQL\Datain the File Name Box type any name (best to use the DB
Name with Underscore 2 eg:DBNAME_02
You can then click on the Sapce aloocted ( whcih by default is 1 to say 2000
MB (2GB) or just let it grow in accordance with the RFile Properties you
selected on the lower half of the screen.
--
Cheers
Coburndavis
"G Dean Blake" wrote:
> I'm uploading a table to my Web Hosting Site that has 499 rows (big rows
> because they have binary object in them).
> After an hour or so of importing using a DTS package, I get the following
> error:
> Error at Destination for row number 499. could not allocate space for
> object 'Pictures' in database "FamPhoto1' because the 'PRIMARY' filegroup is
> full.
> What could cause this error? All of the space allocations are defined in my
> tables? is my web hoster out of space?
> Thanks,
> G
>
>|||Try this:
Right click on database in question. Select Properties. Then go to 'Data
Files' Tab.
Under the Location Column click on the Elipse Button (the grey square with
the three dots!!)
Go to the path where you .MDF's are saved (usually program Files\Microsoft
SQL Server\MSSQL\Data In the File Name Box type any name (best to use the DB
Name with Underscore 2 eg:DBNAME_02
You can then click on the Space allocated ( which by default is 1 to say
2000 MB (2GB) or just let it grow in accordance with the File Properties you
selected on the lower half of the screen.
--
Cheers
Coburndavis
"G Dean Blake" wrote:
> I'm uploading a table to my Web Hosting Site that has 499 rows (big rows
> because they have binary object in them).
> After an hour or so of importing using a DTS package, I get the following
> error:
> Error at Destination for row number 499. could not allocate space for
> object 'Pictures' in database "FamPhoto1' because the 'PRIMARY' filegroup is
> full.
> What could cause this error? All of the space allocations are defined in my
> tables? is my web hoster out of space?
> Thanks,
> G
>
>
