That's 200 MB, not the issue.

What ahve you done so far?

Restricted to what?

sqlgreg (9/7/2011)

---

Anakin,

Yes, I just created a smaller version of the same database, same kind of data, just 1000 rows instead of 10 million.

No problems, I can back it up ok....

Thanks Lutz. A couple more "me toos" here should be enough to make sure they consider it correctly. Sounds like they "over simplified" their version of...

Try creating a new user db and doing the select into with 10 000 rows.

See if that reproduces the issue.

If you create a new db in the same folder(s). Can you read / write from it?

Not long.

Are you sure you are looking at the right file? Did you refresh after running the command?

COALESCE returns the FIRST non-null it finds (doesn't matter if you don't feed any nulls). If you need more complex logic than this then you can use a case...

If you think this is a fluke you can shrink it.

But if it grows again then you know this is what the system needs to have.

As a first round of...

Add a comma before MAXSIZE

Anything else that fails?

How did you load that db?

Have you tried running the same script with encryption off?

Marios Philippopoulos (9/7/2011)

---

Ninja's_RGR'us (9/7/2011)

---

Subscriptions are...

Subscriptions are setup as jobs,...

Just a guess but cancelling the job could do it...