What you're doing, the file utilization. Although, that's the size of the files, not the size of the data. A simple way to get a view of this is to...

Extended events filter at the point of capture. That means they radically reduce their footprint as they will only capture the events you're interested in. Trace captures every event first,...

Mind you, tracking backup size is important too, but for managing the backups and their drives, not for maintaining the database size tracking.

Fair warning, filtering in trace occurs after the trace event is captured. Filtering only really helps with the data you're storing from the capture. Extended events work much better.

I wouldn't use the backups to estimate database size. Instead I'd monitor the size and growth the database itself.

Show what you've done so far. The T-SQL syntax you're looking for is JOIN.

You really shouldn't have anything in a trial environment that you're not ready to throw away. After all, the tests could have just failed.

But as others have said, export/import is...

Steve Jones - SSC Editor (4/14/2015)

---

Ed Wagner (4/14/2015)

---

Well done, Grant. I'd say you've earned a victory beer, so enjoy...

And this makes 14,001 posts. My fingers are tired.

It's not in the system_health extended events session. I know that.

xsevensinzx (4/14/2015)

---

Grant Fritchey (4/14/2015)

---

All this "never use public WIFI" and "never work in public" might be viable when you have a job that requires you to show up in an...

t.pinder (4/14/2015)

---

Grant Fritchey (4/14/2015)

---

All this "never use public WIFI" and "never work in public" might be viable when you have a job that requires you to show up in an...

Yeah, it's all largely still applicable. Having more than one disk helps I/O. Further, having more than one file/filegroup helps too. You do have to take into account the number...

Ville-Pekka Vahteala (4/14/2015)

---

These did not have those numbers what I asked, but they...

Ah, true. Hadn't thought that...