Database growth and Replication

We have two database instances replicating between them.
We are currently trying to manually grow the database files, when we
do they are reverting back to the original size.
Using Enterprise Manager we enter the properties and insert the new
file size. When we come out SQL pauses and when the screen refreshes
shows the new size.
If we exit enterprise manager and then go back in the original size is
being used.
We have tried ammending the publisher then the subscriber and vice
versa.
Do we need to stop merge replication prior to a database file growth?
Thanks
Graz"graz79" <graz79@.yahoo.co.uk> wrote in message
news:1178020439.331730.41150@.l77g2000hsb.googlegroups.com...
> We have two database instances replicating between them.
> We are currently trying to manually grow the database files, when we
> do they are reverting back to the original size.
> Using Enterprise Manager we enter the properties and insert the new
> file size. When we come out SQL pauses and when the screen refreshes
> shows the new size.
> If we exit enterprise manager and then go back in the original size is
> being used.
> We have tried ammending the publisher then the subscriber and vice
> versa.
> Do we need to stop merge replication prior to a database file growth?
>
Not that I'm aware.
But it almost always sounds like you have auto-shrink enabled.

> Thanks
> Graz
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||That was it. Missed the autoshrink option.
Thanks|||"graz79" <graz79@.yahoo.co.uk> wrote in message
news:1178110568.993714.26180@.o5g2000hsb.googlegroups.com...
> That was it. Missed the autoshrink option.
> Thanks
>
You're welcome.
And yet another reason to avoid auto-shrink ;-)
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html

Database growth and Replication

We have two database instances replicating between them.
We are currently trying to manually grow the database files, when we
do they are reverting back to the original size.
Using Enterprise Manager we enter the properties and insert the new
file size. When we come out SQL pauses and when the screen refreshes
shows the new size.
If we exit enterprise manager and then go back in the original size is
being used.
We have tried ammending the publisher then the subscriber and vice
versa.
Do we need to stop merge replication prior to a database file growth?
Thanks
Graz
"graz79" <graz79@.yahoo.co.uk> wrote in message
news:1178020439.331730.41150@.l77g2000hsb.googlegro ups.com...
> We have two database instances replicating between them.
> We are currently trying to manually grow the database files, when we
> do they are reverting back to the original size.
> Using Enterprise Manager we enter the properties and insert the new
> file size. When we come out SQL pauses and when the screen refreshes
> shows the new size.
> If we exit enterprise manager and then go back in the original size is
> being used.
> We have tried ammending the publisher then the subscriber and vice
> versa.
> Do we need to stop merge replication prior to a database file growth?
>
Not that I'm aware.
But it almost always sounds like you have auto-shrink enabled.

> Thanks
> Graz
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||That was it. Missed the autoshrink option.
Thanks
|||"graz79" <graz79@.yahoo.co.uk> wrote in message
news:1178110568.993714.26180@.o5g2000hsb.googlegrou ps.com...
> That was it. Missed the autoshrink option.
> Thanks
>
You're welcome.
And yet another reason to avoid auto-shrink ;-)
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html

Database growth and Replication

We have two database instances replicating between them.
We are currently trying to manually grow the database files, when we
do they are reverting back to the original size.
Using Enterprise Manager we enter the properties and insert the new
file size. When we come out SQL pauses and when the screen refreshes
shows the new size.
If we exit enterprise manager and then go back in the original size is
being used.
We have tried ammending the publisher then the subscriber and vice
versa.
Do we need to stop merge replication prior to a database file growth?
Thanks
Graz"graz79" <graz79@.yahoo.co.uk> wrote in message
news:1178020439.331730.41150@.l77g2000hsb.googlegroups.com...
> We have two database instances replicating between them.
> We are currently trying to manually grow the database files, when we
> do they are reverting back to the original size.
> Using Enterprise Manager we enter the properties and insert the new
> file size. When we come out SQL pauses and when the screen refreshes
> shows the new size.
> If we exit enterprise manager and then go back in the original size is
> being used.
> We have tried ammending the publisher then the subscriber and vice
> versa.
> Do we need to stop merge replication prior to a database file growth?
>
Not that I'm aware.
But it almost always sounds like you have auto-shrink enabled.
> Thanks
> Graz
>
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||That was it. Missed the autoshrink option.
Thanks|||"graz79" <graz79@.yahoo.co.uk> wrote in message
news:1178110568.993714.26180@.o5g2000hsb.googlegroups.com...
> That was it. Missed the autoshrink option.
> Thanks
>
You're welcome.
And yet another reason to avoid auto-shrink ;-)
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html

Database free space: big discrepancy between sp_spaceused and EM taskpad view

I am monitoring free space in my database so I can manually grow the
data file rather than relying on autogrow. I get the free space by
using the 'unallocated space' value returned by sp_spaceused.
Today I was alerted that there was less than 2% free space remaining
in my database. I verified with sp_spaceused and it was reporting ~8GB
unallocated space in a ~500GB database. Then I checked the free space
by looking at the taskpad view for my database in Enterprise Manager.
This showed ~60GB free. I ran a profiler trace to see what EM is doing
to calculate free space but I can't tell what calculations it does,
other than to see that in addition to sp_spaceused it uses the
following two commands:
select sum(convert(float,size)) * (8192.0/1024.0) from dbo.sysfiles
and
DBCC showfilestats
Am I wrong in thinking that the 'unallocated space' and free space
reported by EM should be similar? Is one a more reliable indicator
than the other?
ThanksHi
Before using sp_spaceused run DBCC UPDATEUSAGE command
<pshroads@.gmail.com> wrote in message
news:1184779707.553225.56190@.d30g2000prg.googlegroups.com...
>I am monitoring free space in my database so I can manually grow the
> data file rather than relying on autogrow. I get the free space by
> using the 'unallocated space' value returned by sp_spaceused.
> Today I was alerted that there was less than 2% free space remaining
> in my database. I verified with sp_spaceused and it was reporting ~8GB
> unallocated space in a ~500GB database. Then I checked the free space
> by looking at the taskpad view for my database in Enterprise Manager.
> This showed ~60GB free. I ran a profiler trace to see what EM is doing
> to calculate free space but I can't tell what calculations it does,
> other than to see that in addition to sp_spaceused it uses the
> following two commands:
> select sum(convert(float,size)) * (8192.0/1024.0) from dbo.sysfiles
> and
> DBCC showfilestats
> Am I wrong in thinking that the 'unallocated space' and free space
> reported by EM should be similar? Is one a more reliable indicator
> than the other?
> Thanks
>

Database free space: big discrepancy between sp_spaceused and EM taskpad view

I am monitoring free space in my database so I can manually grow the
data file rather than relying on autogrow. I get the free space by
using the 'unallocated space' value returned by sp_spaceused.
Today I was alerted that there was less than 2% free space remaining
in my database. I verified with sp_spaceused and it was reporting ~8GB
unallocated space in a ~500GB database. Then I checked the free space
by looking at the taskpad view for my database in Enterprise Manager.
This showed ~60GB free. I ran a profiler trace to see what EM is doing
to calculate free space but I can't tell what calculations it does,
other than to see that in addition to sp_spaceused it uses the
following two commands:
select sum(convert(float,size)) * (8192.0/1024.0) from dbo.sysfiles
and
DBCC showfilestats
Am I wrong in thinking that the 'unallocated space' and free space
reported by EM should be similar? Is one a more reliable indicator
than the other?
ThanksHi
Before using sp_spaceused run DBCC UPDATEUSAGE command
<pshroads@.gmail.com> wrote in message
news:1184779707.553225.56190@.d30g2000prg.googlegroups.com...
>I am monitoring free space in my database so I can manually grow the
> data file rather than relying on autogrow. I get the free space by
> using the 'unallocated space' value returned by sp_spaceused.
> Today I was alerted that there was less than 2% free space remaining
> in my database. I verified with sp_spaceused and it was reporting ~8GB
> unallocated space in a ~500GB database. Then I checked the free space
> by looking at the taskpad view for my database in Enterprise Manager.
> This showed ~60GB free. I ran a profiler trace to see what EM is doing
> to calculate free space but I can't tell what calculations it does,
> other than to see that in addition to sp_spaceused it uses the
> following two commands:
> select sum(convert(float,size)) * (8192.0/1024.0) from dbo.sysfiles
> and
> DBCC showfilestats
> Am I wrong in thinking that the 'unallocated space' and free space
> reported by EM should be similar? Is one a more reliable indicator
> than the other?
> Thanks
>