Preventing Deadlock: group

Showing posts with label group. Show all posts

Friday, March 30, 2012

print header on the first page only

I have a table grouped by id. The detail for a particular group can span
serveral pages.
I have 3 header lines for each group . I want to print all 3 header rows on
the first page of the group and only one of the header rows on the next pages
of the group.
Does any one know how to do this?
--
MarieI found a solution here.
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=150&messageid=227646
--
Marie
"Marie" wrote:
> I have a table grouped by id. The detail for a particular group can span
> serveral pages.
> I have 3 header lines for each group . I want to print all 3 header rows on
> the first page of the group and only one of the header rows on the next pages
> of the group.
> Does any one know how to do this?
> --
> Marie

Wednesday, March 28, 2012

Print Button

Print button is disabled for some users. Don't know why it is doing so? Works fine for most of the users in the same group.

Any help is much appreciated.

SQL SERVER Reporting Services 2000

Win XP

check whether any printer drivers are installed in the machine.

if no printers are installed, then print button gets disabled

suresh babu k

|||

Thank you much! I will check that.

|||Actually printer is installed. But still print button is greyed out.|||

Also check the RSPRINTCLIENT control in the C:\WINDOWS\Downloaded Program Files folder. I they ran on the beta then this dll could be very old. It doesn't seem to get updated when the server does. You can remove it and RS will download a new one.

Although I don't think this will cause the print button to be dimmed out. But if you have a printer installed and its a valid driver, you should get the button at least.

|||R U using rdl or rdlc files..... ?|||

We are using rdl files.

Thanks

|||

The print button is disabled if the users in question cannot download and install the RS Printing ActiveX control.

We have several users who run as non-admin accounts. You have to log onto their machines as an admin and then print the report once. After that the ActiveX control is installed and it works for them.

|||Is there anyway of removing the Print functionality of Report Manager i.e. disabling printing directly from Report Manager?
This in RS 2005
|||

The solution is documented here:

http://msdn2.microsoft.com/en-us/library/ms155874.aspx

-Lukasz

Print Button

Print button is disabled for some users. Don't know why it is doing so? Works fine for most of the users in the same group.

Any help is much appreciated.

SQL SERVER Reporting Services 2000

Win XP

check whether any printer drivers are installed in the machine.

if no printers are installed, then print button gets disabled

suresh babu k

|||

Thank you much! I will check that.

|||Actually printer is installed. But still print button is greyed out.|||

Although I don't think this will cause the print button to be dimmed out. But if you have a printer installed and its a valid driver, you should get the button at least.

|||R U using rdl or rdlc files..... ?|||

We are using rdl files.

Thanks

|||

The print button is disabled if the users in question cannot download and install the RS Printing ActiveX control.

We have several users who run as non-admin accounts. You have to log onto their machines as an admin and then print the report once. After that the ActiveX control is installed and it works for them.

|||Is there anyway of removing the Print functionality of Report Manager i.e. disabling printing directly from Report Manager?
This in RS 2005
|||

The solution is documented here:

http://msdn2.microsoft.com/en-us/library/ms155874.aspx

-Lukasz

sql

Monday, March 12, 2012

PRIMARY Files

Taking a course on SQL. They are saying you can get better performance by
having multiple files for a group.

They then graphically show an example of "Primary" with multiple data files.

I have tried altering PRIMARY to have multiple data files and I get and
error. I have tried creating a new database with multiple PRIMARY files and
get an error.

I can ALTER and CREATE secondary files with multiple data files with no
problem.

Am I mixing apples with oranges, does their "Primary" mean something
different then "PRIMARY"?

Looking at help it seems that you can only have one PRIMARY data file and I
am thinking their use of "Primary" means the primary group where you will
have your tables, not the PRIMARY group. Just don't want to lock onto the
wrong concept.

Thank you101 wrote:
> Taking a course on SQL. They are saying you can get better performance by
> having multiple files for a group.
> They then graphically show an example of "Primary" with multiple data files.
> I have tried altering PRIMARY to have multiple data files and I get and
> error. I have tried creating a new database with multiple PRIMARY files and
> get an error.
> I can ALTER and CREATE secondary files with multiple data files with no
> problem.
> Am I mixing apples with oranges, does their "Primary" mean something
> different then "PRIMARY"?
> Looking at help it seems that you can only have one PRIMARY data file and I
> am thinking their use of "Primary" means the primary group where you will
> have your tables, not the PRIMARY group. Just don't want to lock onto the
> wrong concept.

Read the BOL article "Creating Filegroups." There can be only ONE
Primary file group. There are 3 types of file groups: Primary, User
Defined, Default (usually the Primary file group).
--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)|||Oops, I think I got it. Each time you create a database you can specify the
location of it's PRIMARY file. Each database in an instance can have it's
PRIMARY data file pointing to a different data file. Therefore the PRIMARY
group can have multiple data files. But you can't have multiple data files
for a single database in the PRIMARY group.

Am I warm?
"101" <AceMagoo61@.yahoo.com> wrote in message
news:a9yce.11088$XF3.8443@.twister.nyroc.rr.com...
> Taking a course on SQL. They are saying you can get better performance by
> having multiple files for a group.
> They then graphically show an example of "Primary" with multiple data
> files.
> I have tried altering PRIMARY to have multiple data files and I get and
> error. I have tried creating a new database with multiple PRIMARY files
> and get an error.
> I can ALTER and CREATE secondary files with multiple data files with no
> problem.
> Am I mixing apples with oranges, does their "Primary" mean something
> different then "PRIMARY"?
> Looking at help it seems that you can only have one PRIMARY data file and
> I am thinking their use of "Primary" means the primary group where you
> will have your tables, not the PRIMARY group. Just don't want to lock onto
> the wrong concept.
> Thank you|||101 wrote:
> I understand that there can be only one PRIMARY group. Where I am getting confused is how many data files can there be for one database within the PRIMARY group.
> I am thinking I can have this:
> MyDb_Primary 1 d:\mssql\data\MyDB_Pri.mdf PRIMARY 640 KB Unlimited 10% data only
> MyDB_FG_Dat1 3 e:\mssql\data\MyDB_FG1_1.ndf MyDB_FG1 1024 KB Unlimited 10% data only
> MyDB_FG_Dat2 4 f:\mssql\data\MyDB_FG2_2.ndf MyDB_FG1 1024 KB Unlimited 10% data only
> But I can't have this:
> MyDb_Prim_1 1 d:\mssql\data\MyDB_Pri_1.mdf PRIMARY 640 KB Unlimited 10% data only
> MyDB_Prim_2 3 e:\mssql\data\MyDB_Pri_2.ndf PRIMARY 1024 KB Unlimited 10% data only
> MyDB_Prim_3 4 f:\mssql\data\MyDB_Pri_3.ndf PRIMARY 1024 KB Unlimited 10% data only

That is my understanding also.

--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)|||Hi,

I believe what you are looking for is the following command which adds
another file to the PRIMARY filegroup:

ALTER DATABASE FileGroupTest
ADD FILE
(
NAME = FileGroupTest2,
FILENAME = 'c:\FileGroupTestData2.ndf',
SIZE = 5MB,
MAXSIZE = 100MB,
FILEGROWTH = 5MB
)

This is a cut n paste from Books Online.|||101 (AceMagoo61@.yahoo.com) writes:
> Oops, I think I got it. Each time you create a database you can specify
> the location of it's PRIMARY file. Each database in an instance can have
> it's PRIMARY data file pointing to a different data file. Therefore the
> PRIMARY group can have multiple data files. But you can't have multiple
> data files for a single database in the PRIMARY group.

No, that's not correct. Filegroups do not span databases. In fact
there is no storage entity in SQL Server 7 and later which spans databases.
(In SQL 6.5 and earlier there was, as you always created databases on
devices.)

This is it: a database has one primary file and one primary file group.
The primary file group can contain several files, but only one is the
primary file. The primary file contains sysfiles, which holds information
about all other files and filegroups in the database. (At least this is
my understanding, after reading Kalen Delaney's "Inside SQL Server 2000".)

Here is an example that creates multiple files in the primary file group:

CREATE DATABASE multifile ON
(NAME = multifile_prim1,
filename = 'F:\mssql\data\multifile_1.mdf'),
(NAME = multifile_prim2,
filename = 'F:\mssql\data\multifile_2.mdf'),
FILEGROUP SECONDARY
(NAME = multifile_sec1,
filename = 'F:\mssql\data\multifile_1.ndf'),
(NAME = multifile_sec2,
filename = 'F:\mssql\data\multifile_2.ndf')
LOG ON
(NAME = multifile_log1,
filename = 'F:\mssql\data\multifile_1.ldf'),
(NAME = multifile_log2,
filename = 'F:\mssql\data\multifile_2.ldf')
go
exec sp_helpdb multifile

Note that the syntax in Books Online is apparently wrong. It goes:

CREATE DATABASE database_name
[ ON
[ < filespec > [ ,...n ] ]
[ , < filegroup > [ ,...n ] ]
]
[ LOG ON { < filespec > [ ,...n ] } ]
[ COLLATE collation_name ]
[ FOR LOAD | FOR ATTACH ]

< filespec > ::=
[ PRIMARY ]
( [ NAME = logical_file_name , ]
FILENAME = 'os_file_name'
[ , SIZE = size ]
[ , MAXSIZE = { max_size | UNLIMITED } ]
[ , FILEGROWTH = growth_increment ] ) [ ,...n ]

< filegroup > ::=

FILEGROUP filegroup_name < filespec > [ ,...n ]

But you cannot have FILEGROUP directly after ON. And you cannot use
PRIMARY in a <filespec> which is part of a FILEGROUP definition.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Ok,
I guess I was paying the learning sin-tax. I was trying this:
ALTER DATABASE FileGroupTest
ADD FILE
( NAME = FGT_Pri5,
FILENAME ='c:\mssql\data\FGT_Pri5.ndf'
)
TO FILEGROUP PRIMARY
Which of course errors. I guess the rule is if adding to the PRIMARY group
you don't use the FILEGROUP statement, it will default to the PRIMARY group.
You only use the FILEGROUP statement when adding a file to a user group.

Thank you
"Malcolm" <malcolm.leach@.innovartis.co.uk> wrote in message
news:1114849361.130062.105130@.g14g2000cwa.googlegr oups.com...
> Hi,
> I believe what you are looking for is the following command which adds
> another file to the PRIMARY filegroup:
> ALTER DATABASE FileGroupTest
> ADD FILE
> (
> NAME = FileGroupTest2,
> FILENAME = 'c:\FileGroupTestData2.ndf',
> SIZE = 5MB,
> MAXSIZE = 100MB,
> FILEGROWTH = 5MB
> )
> This is a cut n paste from Books Online.|||Ok, thank you. My problem was I had incorrect syntax trying to add files to
the PRIMARY group.

My understanding is one reason to have multiple files within a file group is
to allow SQL to stripe the data.

Now northwind has only one file (besides the log), northwind.mdf. So
sysfiles and along with everything else reside in that one file. What
happens when I add files to the PRIMARY group for the database?

a) sysfiles stay on northwind.mdf and the rest of the data is spread accross
northwind.mdf, northwind2.ndf, northwind3.ndf.

b) sysfiles stay on northwind.mdf and everything else is spread accross
northwind2.ndf and northwind3.ndf.

c) ??

Also

I notices that the second file you defined for primary had an extention of
..mdf, is that the common practice? .mdf files defined to the primary group
and .ndf files get defined in user groups?
I was defining the first file allocated to a group as .mdf and subsequent
files as .ndf regardless if they were in the PRIMARY group or a USER group.
It looks like you can do both, then again I haven't gone far enough to get
bitten. Even if you can get away with both practices, is there a common
practice for when you define a file with a .mdf extention and a .ndf
extention?

Don't mean to be a pain, just interested in the right way of doing things
and following good procedures.

"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns9648B2C5E59D8Yazorman@.127.0.0.1...
> 101 (AceMagoo61@.yahoo.com) writes:
>> Oops, I think I got it. Each time you create a database you can specify
>> the location of it's PRIMARY file. Each database in an instance can have
>> it's PRIMARY data file pointing to a different data file. Therefore the
>> PRIMARY group can have multiple data files. But you can't have multiple
>> data files for a single database in the PRIMARY group.
> No, that's not correct. Filegroups do not span databases. In fact
> there is no storage entity in SQL Server 7 and later which spans
> databases.
> (In SQL 6.5 and earlier there was, as you always created databases on
> devices.)
> This is it: a database has one primary file and one primary file group.
> The primary file group can contain several files, but only one is the
> primary file. The primary file contains sysfiles, which holds information
> about all other files and filegroups in the database. (At least this is
> my understanding, after reading Kalen Delaney's "Inside SQL Server 2000".)
> Here is an example that creates multiple files in the primary file group:
> CREATE DATABASE multifile ON
> (NAME = multifile_prim1,
> filename = 'F:\mssql\data\multifile_1.mdf'),
> (NAME = multifile_prim2,
> filename = 'F:\mssql\data\multifile_2.mdf'),
> FILEGROUP SECONDARY
> (NAME = multifile_sec1,
> filename = 'F:\mssql\data\multifile_1.ndf'),
> (NAME = multifile_sec2,
> filename = 'F:\mssql\data\multifile_2.ndf')
> LOG ON
> (NAME = multifile_log1,
> filename = 'F:\mssql\data\multifile_1.ldf'),
> (NAME = multifile_log2,
> filename = 'F:\mssql\data\multifile_2.ldf')
> go
> exec sp_helpdb multifile
> Note that the syntax in Books Online is apparently wrong. It goes:
> CREATE DATABASE database_name
> [ ON
> [ < filespec > [ ,...n ] ]
> [ , < filegroup > [ ,...n ] ]
> ]
> [ LOG ON { < filespec > [ ,...n ] } ]
> [ COLLATE collation_name ]
> [ FOR LOAD | FOR ATTACH ]
> < filespec > ::=
> [ PRIMARY ]
> ( [ NAME = logical_file_name , ]
> FILENAME = 'os_file_name'
> [ , SIZE = size ]
> [ , MAXSIZE = { max_size | UNLIMITED } ]
> [ , FILEGROWTH = growth_increment ] ) [ ,...n ]
> < filegroup > ::=
> FILEGROUP filegroup_name < filespec > [ ,...n ]
> But you cannot have FILEGROUP directly after ON. And you cannot use
> PRIMARY in a <filespec> which is part of a FILEGROUP definition.
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp|||101 (AceMagoo61@.yahoo.com) writes:
> My understanding is one reason to have multiple files within a file
> group is to allow SQL to stripe the data.

Hm, yes, but striping is probably best done by hardware.

Kalen Delaney discusses this in her book a bit, and she puts more
stress on flexibility. If you have a 60 GB database in one file and
you need to restore it, you need to find 60 GB of free space on one
disk. If you have three files, you can combine space on more than
one disk.

> Now northwind has only one file (besides the log), northwind.mdf. So
> sysfiles and along with everything else reside in that one file. What
> happens when I add files to the PRIMARY group for the database?
> a) sysfiles stay on northwind.mdf and the rest of the data is spread
> accross northwind.mdf, northwind2.ndf, northwind3.ndf.

As I understand it, all system tables are in the primary file. The
user table and indexes are spread over the other filers, including
northwind.mdf.

> I notices that the second file you defined for primary had an extention of
> .mdf, is that the common practice? .mdf files defined to the primary group
> and .ndf files get defined in user groups?

It appears that I've should have used .ndf for the second file, and
not .mdf. I rarely play with multiple files, so I just made a guess
that .ndf for files in other file groups, but I was wong.

In any case, that is just a convention and you can use .doc and .xls if
you feel like. (But I would not recommend using precisely those
exetentions!)

> Even if you can get away with both practices, is there a common
> practice for when you define a file with a .mdf extention and a .ndf
> extention?

The practice appears to be .mdf for primary files and .ndf for secondary.
And .ldf for log files. But I would not be surprised if there are shops
where they have multiple files and they use .mdf for all data files.
I would suggest that the main thing here is that you is consistent, and
don't mix different styles. (I actually had this database with a log
file with .mdf. It caused me some problems when I tried to restore
a backup of the database in the SQL 2005 GUI, and I submitted a bug
report, because the GUI used the same file name for both. I thought
the GUI was crappy because it used .mdf for the log file. It took me
quite some time, to see that it was my own mistake.)

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Thank you!
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns9648C89CCC942Yazorman@.127.0.0.1...
> 101 (AceMagoo61@.yahoo.com) writes:
>> My understanding is one reason to have multiple files within a file
>> group is to allow SQL to stripe the data.
> Hm, yes, but striping is probably best done by hardware.
> Kalen Delaney discusses this in her book a bit, and she puts more
> stress on flexibility. If you have a 60 GB database in one file and
> you need to restore it, you need to find 60 GB of free space on one
> disk. If you have three files, you can combine space on more than
> one disk.
>> Now northwind has only one file (besides the log), northwind.mdf. So
>> sysfiles and along with everything else reside in that one file. What
>> happens when I add files to the PRIMARY group for the database?
>>
>> a) sysfiles stay on northwind.mdf and the rest of the data is spread
>> accross northwind.mdf, northwind2.ndf, northwind3.ndf.
> As I understand it, all system tables are in the primary file. The
> user table and indexes are spread over the other filers, including
> northwind.mdf.
>> I notices that the second file you defined for primary had an extention
>> of
>> .mdf, is that the common practice? .mdf files defined to the primary
>> group
>> and .ndf files get defined in user groups?
> It appears that I've should have used .ndf for the second file, and
> not .mdf. I rarely play with multiple files, so I just made a guess
> that .ndf for files in other file groups, but I was wong.
> In any case, that is just a convention and you can use .doc and .xls if
> you feel like. (But I would not recommend using precisely those
> exetentions!)
>> Even if you can get away with both practices, is there a common
>> practice for when you define a file with a .mdf extention and a .ndf
>> extention?
> The practice appears to be .mdf for primary files and .ndf for secondary.
> And .ldf for log files. But I would not be surprised if there are shops
> where they have multiple files and they use .mdf for all data files.
> I would suggest that the main thing here is that you is consistent, and
> don't mix different styles. (I actually had this database with a log
> file with .mdf. It caused me some problems when I tried to restore
> a backup of the database in the SQL 2005 GUI, and I submitted a bug
> report, because the GUI used the same file name for both. I thought
> the GUI was crappy because it used .mdf for the log file. It took me
> quite some time, to see that it was my own mistake.)
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp

Friday, March 9, 2012

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 header on the first page only

Wednesday, March 28, 2012

Print Button

Print Button

Monday, March 12, 2012

PRIMARY Files

Friday, March 9, 2012

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