Fillfactor at 10 took all my free space

I do a lot of bcping and was trying to speed it up by changing the
fillfactor on a clustered index, and now the database has doubled in size
from 200 to 400 gb and there is no free space left but the process keeps
running. Short of restore, what can I do to get the process to end?Have you tried killing the process from QA ? Find out the
spid of the running process and then open up another
window in QA and issue KILL <spid> command to end the
process.
hth.
>--Original Message--
>I do a lot of bcping and was trying to speed it up by
changing the
>fillfactor on a clustered index, and now the database has
doubled in size
>from 200 to 400 gb and there is no free space left but
the process keeps
>running. Short of restore, what can I do to get the
process to end?
>
>.
>

File replication via sattelite

Will data be changing at both Publisher and subscriber?
>--Original Message--
>Hello.
>I need to do replication via sattelite communication.
This means: Very high cost (7$/minute), low datarate (64
kbit), not reliable and long delay (up to 4 seconds from a
datapackage is sent until an ACK is returned.
>I would prefere to do this offline- that is by
transfering a file with replication data.
>The datavolume shuld be kept to the lowest possible.
>A high degree of data partioning is possible in the
application.
>High degree of autonomy is necessary- only replication
once a day.
>This suggests merge replication.
>But is it possible to that filebased: That is, transfer a
file (via e-mail) and then do the merge at the subscriber
totally offline?
>I would appriciate if anyone could lead me in the correct
direction on this. (Or stop me before I reach the edge..)
>.
>
Yes, data will change both sides. But the application will only allow Inserts both sides, Deletes and Modifies one side. (Hopefully)
"Kevin3NF" wrote:

> Will data be changing at both Publisher and subscriber?
> This means: Very high cost (7$/minute), low datarate (64
> kbit), not reliable and long delay (up to 4 seconds from a
> datapackage is sent until an ACK is returned.
> transfering a file with replication data.
> application.
> once a day.
> file (via e-mail) and then do the merge at the subscriber
> totally offline?
> direction on this. (Or stop me before I reach the edge..)
>