Preventing Deadlock: file

Showing posts with label file. Show all posts

Friday, March 30, 2012

Print File Size

Just installed SP2 and started experimenting with the print functionality.
The size of the print jobs are huge. I had a fairly simple six page report
with a spooling size of over 100 mb, a single page over 17mb. Is there
anything that can be done to reduce this size . If not, we will not be able
to use the functionality as the network just will bog down - it is back to
printing out pdf files - which the users do not like.
Any hope of getting around this?This is the current behavior and there is no workaround. We are looking at
what we can do to make this better for the Yukon Release.
--
| Thread-Topic: Print File Size
| thread-index: AcVi/0NJpHDoEkgjQrGWFSnnPT784w==| X-WBNR-Posting-Host: 24.97.250.114
| From: "=?Utf-8?B?Y2hyaXM=?=" <chris@.discussions.microsoft.com>
| Subject: Print File Size
| Date: Fri, 27 May 2005 14:01:33 -0700
| Lines: 12
| Message-ID: <BBD25630-CC0A-4176-AEE4-03EC7BE22C6D@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:44927
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| Just installed SP2 and started experimenting with the print
functionality.
| The size of the print jobs are huge. I had a fairly simple six page
report
| with a spooling size of over 100 mb, a single page over 17mb. Is there
| anything that can be done to reduce this size . If not, we will not be
able
| to use the functionality as the network just will bog down - it is back
to
| printing out pdf files - which the users do not like.
|
| Any hope of getting around this?
|
|
|
|
|

Monday, March 26, 2012

PrimaryKey consisting of two PKs with autoincrement?

I want to create a table where I can make a history of a file, while it's
processed by my application. The file will change and even get a new file, so
I created a Document table and a Journal table. The Journal table contains
the time, the event that did occure and a FK to the Document table. One line
represents a specific document (one unique file).
I added two primary keys to this table, one for the transaction and one for
the document itself. So always when a file changes (gets a new file) a new
line will be inserted with a new document key, but the same transaction key.
When a completly new file gets processed a new transaction should start and
the document key will again begin by zero.
I just would like to new if it is possible to make the document key
autoincremental, so that I don't have to worry about it in the application. I
don't really think that the transaction key can be made autoincremental, as
the database does not know, if it is a completly new file or just a new
version of an older file.
But could there be any problems with making the document key
autoincremental? I just want it to be zero again, every time a new
transaction key starts, but I think the database will just count on.
Hi
Take a look at an INDETITY property that is a good choice for artificial
keys.
"Stampede" <Stampede@.discussions.microsoft.com> wrote in message
news:F835C787-5BC8-4835-A31D-D38C4EA581A1@.microsoft.com...
> I want to create a table where I can make a history of a file, while it's
> processed by my application. The file will change and even get a new file,
so
> I created a Document table and a Journal table. The Journal table contains
> the time, the event that did occure and a FK to the Document table. One
line
> represents a specific document (one unique file).
> I added two primary keys to this table, one for the transaction and one
for
> the document itself. So always when a file changes (gets a new file) a new
> line will be inserted with a new document key, but the same transaction
key.
> When a completly new file gets processed a new transaction should start
and
> the document key will again begin by zero.
> I just would like to new if it is possible to make the document key
> autoincremental, so that I don't have to worry about it in the
application. I
> don't really think that the transaction key can be made autoincremental,
as
> the database does not know, if it is a completly new file or just a new
> version of an older file.
> But could there be any problems with making the document key
> autoincremental? I just want it to be zero again, every time a new
> transaction key starts, but I think the database will just count on.

PrimaryKey consisting of two PKs with autoincrement?

I want to create a table where I can make a history of a file, while it's
processed by my application. The file will change and even get a new file, so
I created a Document table and a Journal table. The Journal table contains
the time, the event that did occure and a FK to the Document table. One line
represents a specific document (one unique file).
I added two primary keys to this table, one for the transaction and one for
the document itself. So always when a file changes (gets a new file) a new
line will be inserted with a new document key, but the same transaction key.
When a completly new file gets processed a new transaction should start and
the document key will again begin by zero.
I just would like to new if it is possible to make the document key
autoincremental, so that I don't have to worry about it in the application. I
don't really think that the transaction key can be made autoincremental, as
the database does not know, if it is a completly new file or just a new
version of an older file.
But could there be any problems with making the document key
autoincremental? I just want it to be zero again, every time a new
transaction key starts, but I think the database will just count on.Hi
Take a look at an INDETITY property that is a good choice for artificial
keys.
"Stampede" <Stampede@.discussions.microsoft.com> wrote in message
news:F835C787-5BC8-4835-A31D-D38C4EA581A1@.microsoft.com...
> I want to create a table where I can make a history of a file, while it's
> processed by my application. The file will change and even get a new file,
so
> I created a Document table and a Journal table. The Journal table contains
> the time, the event that did occure and a FK to the Document table. One
line
> represents a specific document (one unique file).
> I added two primary keys to this table, one for the transaction and one
for
> the document itself. So always when a file changes (gets a new file) a new
> line will be inserted with a new document key, but the same transaction
key.
> When a completly new file gets processed a new transaction should start
and
> the document key will again begin by zero.
> I just would like to new if it is possible to make the document key
> autoincremental, so that I don't have to worry about it in the
application. I
> don't really think that the transaction key can be made autoincremental,
as
> the database does not know, if it is a completly new file or just a new
> version of an older file.
> But could there be any problems with making the document key
> autoincremental? I just want it to be zero again, every time a new
> transaction key starts, but I think the database will just count on.

PrimaryKey consisting of two PKs with autoincrement?

I want to create a table where I can make a history of a file, while it's
processed by my application. The file will change and even get a new file, s
o
I created a Document table and a Journal table. The Journal table contains
the time, the event that did occure and a FK to the Document table. One line
represents a specific document (one unique file).
I added two primary keys to this table, one for the transaction and one for
the document itself. So always when a file changes (gets a new file) a new
line will be inserted with a new document key, but the same transaction key.
When a completly new file gets processed a new transaction should start and
the document key will again begin by zero.
I just would like to new if it is possible to make the document key
autoincremental, so that I don't have to worry about it in the application.
I
don't really think that the transaction key can be made autoincremental, as
the database does not know, if it is a completly new file or just a new
version of an older file.
But could there be any problems with making the document key
autoincremental? I just want it to be zero again, every time a new
transaction key starts, but I think the database will just count on.Hi
Take a look at an INDETITY property that is a good choice for artificial
keys.
"Stampede" <Stampede@.discussions.microsoft.com> wrote in message
news:F835C787-5BC8-4835-A31D-D38C4EA581A1@.microsoft.com...
> I want to create a table where I can make a history of a file, while it's
> processed by my application. The file will change and even get a new file,
so
> I created a Document table and a Journal table. The Journal table contains
> the time, the event that did occure and a FK to the Document table. One
line
> represents a specific document (one unique file).
> I added two primary keys to this table, one for the transaction and one
for
> the document itself. So always when a file changes (gets a new file) a new
> line will be inserted with a new document key, but the same transaction
key.
> When a completly new file gets processed a new transaction should start
and
> the document key will again begin by zero.
> I just would like to new if it is possible to make the document key
> autoincremental, so that I don't have to worry about it in the
application. I
> don't really think that the transaction key can be made autoincremental,
as
> the database does not know, if it is a completly new file or just a new
> version of an older file.
> But could there be any problems with making the document key
> autoincremental? I just want it to be zero again, every time a new
> transaction key starts, but I think the database will just count on.

Primary versus unique keys

What impact is there in using a unique index instead of a primary key?

How does this impact performance?

How does this impact data file size?

Does it impact anything else?

Thanks

Hi,

http://www.mssqlcity.com/FAQ/General/primary_vs_unique_constraints.htm

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

|||

It that the only difference?

Is there any impact on Replication, Database Mirroing (SQL 2005), or any other features?

Thanks

|||

There is an impact on transactional replication (all options) since it requires a primary key (unique indexes do not work). No impact to either merge or snapshot replication.

Database Mirroring and other features don't care.

Tuesday, March 20, 2012

Primary Key Constraint Violation

I need to insert a text file where might contains duplicate data into
a table with primary keys using a DTS package. is there anyone out
there could help me? I have tried couple way to get around, but still
doesn't work.I would load trhe text file in to a table of the correct structure, but =with no PK constraint. Then use SELECT DISTINCT -- to retrieve the =data you need and insert into final table. (INSERT INTO -- SELECT =DISTINCT -- FROM can by helpful for that part).
Mike John
"Matt" <tkiansoon@.yahoo.com> wrote in message =news:7a4ed84d.0308270840.25fe7496@.posting.google.com...
> I need to insert a text file where might contains duplicate data into
> a table with primary keys using a DTS package. is there anyone out
> there could help me? I have tried couple way to get around, but still
> doesn't work.|||You could load it into a staging table first and then de-dupe it or have a
index with ignore duplicate key on the staging table (but this would slow
the load unless the text file is ordered the same as the index which would
need to be unique clustered) and assumes that the entire row is a duplicate
if the key is.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Matt" <tkiansoon@.yahoo.com> wrote in message
news:7a4ed84d.0308270840.25fe7496@.posting.google.com...
I need to insert a text file where might contains duplicate data into
a table with primary keys using a DTS package. is there anyone out
there could help me? I have tried couple way to get around, but still
doesn't work.

Monday, March 12, 2012

primary filegroup is full?

Hi,
I'm trying to use DTS to import a text file into a table and I get an error
saying that space cannot be allocated for the file because the primary
filegroup is full.
Any ideas how to extend the primary filegroup?
thanksRafale
It looks like during the DTS's execution an autogrow feature kicks in and
it takes some time
Check it out if you have enough available space and try to import the data
with small tranasctions.
"Rafael Chemtob" <rchemtobb@.nospam.yahoo.com> wrote in message
news:%236fCfYeOFHA.244@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I'm trying to use DTS to import a text file into a table and I get an
error
> saying that space cannot be allocated for the file because the primary
> filegroup is full.
> Any ideas how to extend the primary filegroup?
> thanks
>|||Yes I hit the same deal a few years ago try to shrink the files and the
tran log in that does not work then you need more hard disk space. aka
another disk drive or nas
*** Sent via Developersdex http://www.examnotes.net ***|||Hi,
Looks like any one of the below 3 reasons had created this error:-
1. You have restricted the file growth
2. Transaction log (LDF) has gone high due to DTS
3. Not enough room in hard disk
The solutions for each of the above problems are:-
1. Remove the restricted growth and monitor the growth while DTS
2. Take Transaction log backup and shrink the LDF file. See Backup LOG and
DBCC SHRINKFILE commands in books online. After shrink start the
DTS
3. Add a new file (NDF) and put it in a hard disk drive where u have more
space and start DTS
Thanks
Hari
SQL Server MVP
"Rafael Chemtob" <rchemtobb@.nospam.yahoo.com> wrote in message
news:%236fCfYeOFHA.244@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I'm trying to use DTS to import a text file into a table and I get an
> error
> saying that space cannot be allocated for the file because the primary
> filegroup is full.
> Any ideas how to extend the primary filegroup?
> thanks
>

Friday, March 9, 2012

'PRIMARY' filegroup is full problem

quote:

>Could not allocate space for object 'myTableName' in database

'myDatabase'

quote:

>because the 'PRIMARY' filegroup is full.

Using the Enterprise manager, I click on the database symbol and choose
"properties". The size of the database is '8132 MB' and it claims the space
available is '0.00 MB'.
However, on both the data file and the log file, I've got the following
properties set:
Automatically Grow File: YES
By Percent: 10%
Maximum file size: Unrestricted file growth
I've checked the disk and there's ~50 GB of free disk space, and it's fairly
contiguous space too.
Is my problem just that I need to increase the % growth from the current
value of 10% to something higher? I ask only because I have another
database that is smaller (but comparable in size) and this sort of data
import works with a growth size set of just 5%.
A second related question is whether there is a way to identify what % of
the database size is taken up by one particular (existing) table? If I knew
this, I'm sure I could answer the first question definitively myself.
Thanks in advance
GriffIt probably timed out before it could allocate the new space for the file.
You should never rely on autogrow and always ensure you have plenty of free
space in the database and log files. If you know your going to do a large
load you should check beforehand and manually grow the files before you
attempt the load. I would increase it an try again.
Andrew J. Kelly
SQL Server MVP
"GriffithsJ" <GriffithsJ_520@.hotmail.com> wrote in message
news:OUSGyfO4DHA.2332@.TK2MSFTNGP10.phx.gbl...

quote:

> Hi
> I have a script that creates a table in a database and populates it using
> bulk copy from a comma-delimited file.
> The number of rows of data to be entered is fairly large (approximately 24
> million rows of data).
> However, last night this fell over with the error message:
>
> 'myDatabase'
> Using the Enterprise manager, I click on the database symbol and choose
> "properties". The size of the database is '8132 MB' and it claims the

space

quote:

> available is '0.00 MB'.
> However, on both the data file and the log file, I've got the following
> properties set:
> Automatically Grow File: YES
> By Percent: 10%
> Maximum file size: Unrestricted file growth
> I've checked the disk and there's ~50 GB of free disk space, and it's

fairly

quote:

> contiguous space too.
> Is my problem just that I need to increase the % growth from the current
> value of 10% to something higher? I ask only because I have another
> database that is smaller (but comparable in size) and this sort of data
> import works with a growth size set of just 5%.
> A second related question is whether there is a way to identify what % of
> the database size is taken up by one particular (existing) table? If I

knew

quote:

> this, I'm sure I could answer the first question definitively myself.
> Thanks in advance
> Griff
>
>

|||Andrew
Thanks for your response. Can I ask though why one should never rely on the
"auto-grow" feature? Is it one of those features that "does not always do
what it says on the tin"...
Cheers
Griff|||The reason is just what you (probably) have got -- in an application you
have too large a data load, that grows the db size for which it needs such a
long time that your application times out.
To look at the size of a table run
sp_spaceused TableName, true
"GriffithsJ" <GriffithsJ_520@.hotmail.com> wrote in message
news:u521Q9O4DHA.488@.TK2MSFTNGP12.phx.gbl...

quote:

> Andrew
> Thanks for your response. Can I ask though why one should never rely on

the

quote:

> "auto-grow" feature? Is it one of those features that "does not always do
> what it says on the tin"...
> Cheers
> Griff
>
>

|||Quentin is correct. Also growing the db is an expensive process and
something you don't want to happen when the users are making updates in the
db if you can help it. It is better to manually (or schedule it) grow the
db during off peak times so as not to impact the users.
Andrew J. Kelly
SQL Server MVP
"Quentin Ran" <ab@.who.com> wrote in message
news:%236Wzg7Q4DHA.1704@.tk2msftngp13.phx.gbl...

quote:

> The reason is just what you (probably) have got -- in an application you
> have too large a data load, that grows the db size for which it needs such

quote:

> long time that your application times out.
> To look at the size of a table run
> sp_spaceused TableName, true
> "GriffithsJ" <GriffithsJ_520@.hotmail.com> wrote in message
> news:u521Q9O4DHA.488@.TK2MSFTNGP12.phx.gbl...
> the
do[QUOTE]
>

'PRIMARY' filegroup is full problem

Hi
I have a script that creates a table in a database and populates it using
bulk copy from a comma-delimited file.
The number of rows of data to be entered is fairly large (approximately 24
million rows of data).
However, last night this fell over with the error message:
>Could not allocate space for object 'myTableName' in database
'myDatabase'
>because the 'PRIMARY' filegroup is full.
Using the Enterprise manager, I click on the database symbol and choose
"properties". The size of the database is '8132 MB' and it claims the space
available is '0.00 MB'.
However, on both the data file and the log file, I've got the following
properties set:
Automatically Grow File: YES
By Percent: 10%
Maximum file size: Unrestricted file growth
I've checked the disk and there's ~50 GB of free disk space, and it's fairly
contiguous space too.
Is my problem just that I need to increase the % growth from the current
value of 10% to something higher? I ask only because I have another
database that is smaller (but comparable in size) and this sort of data
import works with a growth size set of just 5%.
A second related question is whether there is a way to identify what % of
the database size is taken up by one particular (existing) table? If I knew
this, I'm sure I could answer the first question definitively myself.
Thanks in advance
GriffIt probably timed out before it could allocate the new space for the file.
You should never rely on autogrow and always ensure you have plenty of free
space in the database and log files. If you know your going to do a large
load you should check beforehand and manually grow the files before you
attempt the load. I would increase it an try again.
--
Andrew J. Kelly
SQL Server MVP
"GriffithsJ" <GriffithsJ_520@.hotmail.com> wrote in message
news:OUSGyfO4DHA.2332@.TK2MSFTNGP10.phx.gbl...
> Hi
> I have a script that creates a table in a database and populates it using
> bulk copy from a comma-delimited file.
> The number of rows of data to be entered is fairly large (approximately 24
> million rows of data).
> However, last night this fell over with the error message:
> >Could not allocate space for object 'myTableName' in database
> 'myDatabase'
> >because the 'PRIMARY' filegroup is full.
> Using the Enterprise manager, I click on the database symbol and choose
> "properties". The size of the database is '8132 MB' and it claims the
space
> available is '0.00 MB'.
> However, on both the data file and the log file, I've got the following
> properties set:
> Automatically Grow File: YES
> By Percent: 10%
> Maximum file size: Unrestricted file growth
> I've checked the disk and there's ~50 GB of free disk space, and it's
fairly
> contiguous space too.
> Is my problem just that I need to increase the % growth from the current
> value of 10% to something higher? I ask only because I have another
> database that is smaller (but comparable in size) and this sort of data
> import works with a growth size set of just 5%.
> A second related question is whether there is a way to identify what % of
> the database size is taken up by one particular (existing) table? If I
knew
> this, I'm sure I could answer the first question definitively myself.
> Thanks in advance
> Griff
>
>|||Andrew
Thanks for your response. Can I ask though why one should never rely on the
"auto-grow" feature? Is it one of those features that "does not always do
what it says on the tin"...
Cheers
Griff|||The reason is just what you (probably) have got -- in an application you
have too large a data load, that grows the db size for which it needs such a
long time that your application times out.
To look at the size of a table run
sp_spaceused TableName, true
"GriffithsJ" <GriffithsJ_520@.hotmail.com> wrote in message
news:u521Q9O4DHA.488@.TK2MSFTNGP12.phx.gbl...
> Andrew
> Thanks for your response. Can I ask though why one should never rely on
the
> "auto-grow" feature? Is it one of those features that "does not always do
> what it says on the tin"...
> Cheers
> Griff
>
>|||Quentin is correct. Also growing the db is an expensive process and
something you don't want to happen when the users are making updates in the
db if you can help it. It is better to manually (or schedule it) grow the
db during off peak times so as not to impact the users.
--
Andrew J. Kelly
SQL Server MVP
"Quentin Ran" <ab@.who.com> wrote in message
news:%236Wzg7Q4DHA.1704@.tk2msftngp13.phx.gbl...
> The reason is just what you (probably) have got -- in an application you
> have too large a data load, that grows the db size for which it needs such
a
> long time that your application times out.
> To look at the size of a table run
> sp_spaceused TableName, true
> "GriffithsJ" <GriffithsJ_520@.hotmail.com> wrote in message
> news:u521Q9O4DHA.488@.TK2MSFTNGP12.phx.gbl...
> > Andrew
> >
> > Thanks for your response. Can I ask though why one should never rely on
> the
> > "auto-grow" feature? Is it one of those features that "does not always
do
> > what it says on the tin"...
> >
> > Cheers
> >
> > Griff
> >
> >
> >
>

'primary file was full' claimed by job when there is plenty space to grow

Hi,
Working on sql server 2000.
I have a job that pulls data from one server into this
server's database. It failed last time claiming the
primary file of the db was full while there were over 24
gig room to grow and the job will only pull in less than 2
gig data.
Then, I run it again serveral hours later, and everything
went through fine.
What happened? Ever encountered this wierd problem
yourself?
Many thanks.
JJCheck out below:
http://support.microsoft.com/default.aspx?scid=kb;en-us;305635
Tibor Karaszi
"JJ Wang" <anonymous@.discussions.microsoft.com> wrote in message
news:07ab01c3a258$9cf1a610$a301280a@.phx.gbl...
> Hi,
> Working on sql server 2000.
> I have a job that pulls data from one server into this
> server's database. It failed last time claiming the
> primary file of the db was full while there were over 24
> gig room to grow and the job will only pull in less than 2
> gig data.
> Then, I run it again serveral hours later, and everything
> went through fine.
> What happened? Ever encountered this wierd problem
> yourself?
> Many thanks.
> JJ

Primary file is full

We set the database to : automatically grow file, unstricted file growth, grow by 10%.
As I understand it will automatically grow, why we recieved error message like primary file full.Not enough disk to grow another ten percent?

-PatP|||Thanks, But we do have enough space.|||How big is the datafile now? And is it sitting on a volume that is formatted with FAT32 or NTFS?|||We set the database to : automatically grow file, unstricted file growth, grow by 10%.
As I understand it will automatically grow, why we recieved error message like primary file full.

How about, like, the actual error message...|||Thanks,

What I want to do now is to set an alert that when the database file is 90 % full, not log file, then send an email.

I didn't see there is an alert like this in the sql event alert, do I need to define it, can I do it in EM?

Also wondering when the system extended the database, when it's full or when it has some percent left?

Thanks|||Search on the term "autogrow" in Books Online, and you should find this in an article titled "Physical Database Files and Filegroups":

SQL Server 2000 files can grow automatically from their originally specified size. When you define a file, you can specify a growth increment. Each time the file fills, it increases its size by the growth increment. If there are multiple files in a filegroup, they do not autogrow until all the files are full. Growth then occurs using a round-robin algorithm.

primary file group run out of free space??

Hi all
I got the following error massage when tried to delete some 3 GB records
from a 26 GB records table - 'tblName':
'Could not allocate space for object 'tblName' in database 'dbName' because
the primary
filegroup is full'.
At the time of this error there were some 4 GB free disk space on the disk
where the datababse data and log file were.
Also these files were not limitted in grow size.
My questions are:
1) why does a 'delete' operation involves allocation of space for the table
that is being deleted'
Does this operation involves creating image data for the table that is being
deleted, in the transaction log, where the deletion actually occures and
than commited back to the original table'
So if i am deleting data from a 26GB table, there should be this amount of
free space on the disk where the log's file group is located?
2) Where can i see the state of the primary filegroup and how can i increase
its size?
Thanks for your attention
ReaRea
delete is a logged operation , so have you seen the log file during the
deletion?
SET ROWCOUNT 1000
WHILE 1 = 1
BEGIN
--Perfrom your DELETION (TRUNCATION would be more efficient)
IF @.@.ROWCOUNT = 0
BEGIN
BREAK
END
ELSE
BEGIN
CHECKPOINT
END
END
SET ROWCOUNT 0
"Rea Peleg" <rea_p@.afek.co.il> wrote in message
news:%23ZeKwl$YEHA.2016@.TK2MSFTNGP09.phx.gbl...
> Hi all
> I got the following error massage when tried to delete some 3 GB records
> from a 26 GB records table - 'tblName':
> 'Could not allocate space for object 'tblName' in database 'dbName'
because
> the primary
> filegroup is full'.
> At the time of this error there were some 4 GB free disk space on the disk
> where the datababse data and log file were.
> Also these files were not limitted in grow size.
> My questions are:
> 1) why does a 'delete' operation involves allocation of space for the
table
> that is being deleted'
> Does this operation involves creating image data for the table that is
being
> deleted, in the transaction log, where the deletion actually occures and
> than commited back to the original table'
> So if i am deleting data from a 26GB table, there should be this amount of
> free space on the disk where the log's file group is located?
> 2) Where can i see the state of the primary filegroup and how can i
increase
> its size?
>
> Thanks for your attention
> Rea
>|||Thanks alot!
So how much disk space should a deletion of 3 GB from a 26GB table consume'
Is there a way to estimate the amount of disk space deletion operations
consume from
the transaction log's disk'
2) in your code below: what is the edvantage of doing deletions this way'
Thanks again
Rea
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:e8FMLCAZEHA.3564@.TK2MSFTNGP11.phx.gbl...
> Rea
> delete is a logged operation , so have you seen the log file during the
> deletion?
> SET ROWCOUNT 1000
> WHILE 1 = 1
> BEGIN
> --Perfrom your DELETION (TRUNCATION would be more efficient)
> IF @.@.ROWCOUNT = 0
> BEGIN
> BREAK
> END
> ELSE
> BEGIN
> CHECKPOINT
> END
> END
> SET ROWCOUNT 0
> "Rea Peleg" <rea_p@.afek.co.il> wrote in message
> news:%23ZeKwl$YEHA.2016@.TK2MSFTNGP09.phx.gbl...
> > Hi all
> > I got the following error massage when tried to delete some 3 GB records
> > from a 26 GB records table - 'tblName':
> >
> > 'Could not allocate space for object 'tblName' in database 'dbName'
> because
> > the primary
> > filegroup is full'.
> >
> > At the time of this error there were some 4 GB free disk space on the
disk
> > where the datababse data and log file were.
> > Also these files were not limitted in grow size.
> >
> > My questions are:
> > 1) why does a 'delete' operation involves allocation of space for the
> table
> > that is being deleted'
> > Does this operation involves creating image data for the table that is
> being
> > deleted, in the transaction log, where the deletion actually occures and
> > than commited back to the original table'
> > So if i am deleting data from a 26GB table, there should be this amount
of
> > free space on the disk where the log's file group is located?
> >
> > 2) Where can i see the state of the primary filegroup and how can i
> increase
> > its size?
> >
> >
> > Thanks for your attention
> > Rea
> >
> >
>|||Rea
I divide a long/big transaction into a small one.
CHECKPOINT flows a data from transaction log into the disk to remove an
inactive portions (btw you can also perform BACKUP LOG operation)
With that way you don't lock others by running your big deletion and also
keep a log file with an appropriate size.
"Rea Peleg" <rea_p@.afek.co.il> wrote in message
news:OPOU01AZEHA.3716@.TK2MSFTNGP11.phx.gbl...
> Thanks alot!
> So how much disk space should a deletion of 3 GB from a 26GB table
consume'
> Is there a way to estimate the amount of disk space deletion operations
> consume from
> the transaction log's disk'
> 2) in your code below: what is the edvantage of doing deletions this way'
> Thanks again
> Rea
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:e8FMLCAZEHA.3564@.TK2MSFTNGP11.phx.gbl...
> > Rea
> > delete is a logged operation , so have you seen the log file during the
> > deletion?
> >
> > SET ROWCOUNT 1000
> > WHILE 1 = 1
> > BEGIN
> > --Perfrom your DELETION (TRUNCATION would be more efficient)
> > IF @.@.ROWCOUNT = 0
> > BEGIN
> > BREAK
> > END
> > ELSE
> > BEGIN
> >
> > CHECKPOINT
> > END
> > END
> >
> > SET ROWCOUNT 0
> > "Rea Peleg" <rea_p@.afek.co.il> wrote in message
> > news:%23ZeKwl$YEHA.2016@.TK2MSFTNGP09.phx.gbl...
> > > Hi all
> > > I got the following error massage when tried to delete some 3 GB
records
> > > from a 26 GB records table - 'tblName':
> > >
> > > 'Could not allocate space for object 'tblName' in database 'dbName'
> > because
> > > the primary
> > > filegroup is full'.
> > >
> > > At the time of this error there were some 4 GB free disk space on the
> disk
> > > where the datababse data and log file were.
> > > Also these files were not limitted in grow size.
> > >
> > > My questions are:
> > > 1) why does a 'delete' operation involves allocation of space for the
> > table
> > > that is being deleted'
> > > Does this operation involves creating image data for the table that is
> > being
> > > deleted, in the transaction log, where the deletion actually occures
and
> > > than commited back to the original table'
> > > So if i am deleting data from a 26GB table, there should be this
amount
> of
> > > free space on the disk where the log's file group is located?
> > >
> > > 2) Where can i see the state of the primary filegroup and how can i
> > increase
> > > its size?
> > >
> > >
> > > Thanks for your attention
> > > Rea
> > >
> > >
> >
> >
>

PRIMARY file group is full

Hi there,

I've just run some DTS packages on my test sqlserver (Which has limited
hard disk space and memory) and all the tasks have failed, due to
'PRIMARY' file group is full

Is there a query or script I can run to resolve this problem??

M3ckon

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!m3ckon (anonymous@.devdex.com) writes:
> I've just run some DTS packages on my test sqlserver (Which has limited
> hard disk space and memory) and all the tasks have failed, due to
> 'PRIMARY' file group is full
> Is there a query or script I can run to resolve this problem??

Could send a query to whomeever holds you money to get more hardware.

The message says that SQL Server cannot autogrow the database, because
there is not space on the disk. By default SQL Server grows by 10%, so
if your database is 20 GB, SQL Server tries to grow 2 GB. If you think
you can fit your data into these 2 GB, then you lower that number to
squeeze out the rest from your disk.

Else you will have to try to free up some disk space. If the log for
the database is on the same disk, and you could live with simple
recovery, you could change to simple recovery, and then issue
BACKUP LOG db WITH TRUNCATE_ONLY. You have also have to do a DBCC
SHRINKFILE on the log. But before you do any of this, check how big
your log is.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Primary File Group Full?

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
>
>

Friday, March 30, 2012

Print File Size

Monday, March 26, 2012

PrimaryKey consisting of two PKs with autoincrement?

PrimaryKey consisting of two PKs with autoincrement?

PrimaryKey consisting of two PKs with autoincrement?

Primary versus unique keys

Tuesday, March 20, 2012

Primary Key Constraint Violation

Monday, March 12, 2012

primary filegroup is full?

Friday, March 9, 2012

'PRIMARY' filegroup is full problem

'PRIMARY' filegroup is full problem

'primary file was full' claimed by job when there is plenty space to grow

Primary file is full

primary file group run out of free space??

primary file group run out of free space??

PRIMARY file group is full

Primary File Group Full?

Primary File Group Full?

Primary File Group Full?

Preventing Deadlock

Blog Archive

About Me