I guess rebuilding "can't hurt" - in any case (performance aside)....

Thanks for sharing that info! I'll check it out.

Thanks all -

I will check that page out...

But for clarification, is "rebuilding" an index better than reorganizing? I know I read somewhere that it was overkill to do both...

Thanks Ed...makes sense.

Gotcha - thanks...

For the SQL databases I "watch over" I do the backups (with Red-Gate, full & transaction logs), and monitor for performance issues (to the extent I know how...

John,

Here's a dumb question - some of the DB's of "vendor provided" - they just live on our server, and we do the backups, etc...

Is it part of a DBA's...

I think it's time I go for my MCSA 😉

Recently got my MTA in SQL, but I'm sure I would learn a lot more of this in the MCSA courses...

Gotcha...I'm ignoring tables less than 1meg.

For instance, here's one that is probably not a problem:

TABLE SIZE FRAG%

table1 1512K...

Yep - I can see where the rowcount and disk space is...just didn't know how to see page count...

Either way, yes, most of these are very small tables.

What would be...

I know you can check page size with TSQL - is the page information anywhere in Management Studio?

The 4 hour response time I mentioned was actually for the hardware support to respond with new hardware if needed, to get the server operational. Restore times/recovery would be on...

Hi Brandie -

The initial backups are done with Red-Gate SQL Backup, and are on the server drive, but copied off to a different server...I'll have to ask the network...

Thanks everyone - unfortunately, we don't have a DR site, or even a DR server...we have a 4 hour response time support to get the server fixed if it crashes...

Ahhh...thanks Luis!

Duh....forgot WHERE...

I got it - thanks!

Thanks for the quick response! But when I add additional AND's to the query, it doesn't seem to work:

select t.*, m1.lastname, m1.firstname, m2.lastname, m2.firstname

from tickets t

LEFT OUTER JOIN members...