it is transactional publication, but multiple publishers pushing to a single subscriber database (not a single table). no merge replication at all.

i'm not interested in replication topology or which initialization...

microsoft documentation states that it is linear fill for log files ....

we can't do initialise from backup as there are multiple publications replicating to the subscriber database - restoring from...

I'm sorry , but I can't even begin to describe how much I disagree with this article

my main gripe is the fact that the author has not realised that a...

that 100% categorically does not give you internal fragmentation, external fragmentation or any other kind of fragmentation.....

While this is a great innovation, i can see it potentially causing more issues than it actually fixes...

if you've ever tried using an XL amazon instance to run a DB...

is auto shrink turned on ? is there a dbcc shrinkfile/shrinkdb command being issues?

yes all of them - originally i posted 6 servers, but it's actually 18.. the other 50 or so servers (all win 2008 datacentre with sql 2008 sp3) seem...

exactly!!!

what if you only needed to delete 1%... i was just wondering if there was any specific Windowing issue that you know of (like Jeff's stuff about recursive CTE)

Eugene Elutin (9/6/2012)

---

Are you serious? :w00t:

It is just an EXAMPLE 🙂

So, I've named the table in...

hmmm.... yes, but also alternate solutions might use other resources...

Luis Cazares (9/6/2012)

---

That might be because Eugene already had a #demo table and didn't want to drop ti and create a new one.

You can change the name to #demo.

If you...

a couple of options then

.. is the field in the database a date or datetime field?

.. is your report passing dates in the wrong format ... easy to test...

example 2 wont work -you'll end up with a table called demo1 not demo

eugene... just out of interest... why avoid the windowing???

+1 gail ---- READ THE ARTICLE