sjimmo (1/15/2013)

---

Lynn

To restore to 1/13 4:00 AM you will need the previous days (1/12) full backup file plus all the t-log backups since that backup up to the t-log backup...

not directly, but you could move them to a separate filegroup and make that read only, or do it via permissions (only select granted or only access via stored procs)

If you are talking about a sql native backup it is definitely consistent at the point the backup completed

read this[/url]

there would normally not be enough activity against the model database to cause log growth so something is running against the model database that probably should not be, you need...

easily done, I only noticed because the post just duplicated an earlier one.

And its later in the day here.............:-)

SQLSACT (1/12/2013)

---

Thanks

I've checked the highest averaging IO queries in cache and there are definately some serious scans happening against the top tables

Also, do you think that the low Buffer cache...

10 month old thread (originally) but if samindapawar is asking about consistency checking you should run this

use yourdb

go

DBCC CHECKDB

WITH ALL_ERRORMSGS, NO_INFOMSGS

firstly check the SQL errorlog for error messages - next steps depend on the errors.

just look at the largest tables, you'll get an idea very quickly if any will grab your space back. Make sure the growth factor on the data and log files...

it will work and the metadata will be updated. The owner of the database will change which might not be what you want.

alter database is the accepted best method for...

offline the database

use alter database...move file to change the metadata for the file location

physically COPY the file to the new location specified in the alter database command

bring the database online.

No...

I work in a large shop with separate teams for DBA, sysadmins, network etc, and our sysadmins support the OS, which includes the windows cluster, and DBA support the SQL...

MSSQL_NOOB (12/31/2012)

---

Here are the numbers after today's 12:00pm transaction log backup. Missed the pre-backup numbers.

VLFs or dbcc loginfo(yourdb) returns 288 rows.

dbcc sqlperf(logspace) returns Log Size of 1588 MB (or the...

your log file has grown larger than your data file because it was not being backed up often enough, therefore at some point it has had to grow to accommodate...

is the msdb large? I would first of all look to see if any data can be purged from it, in particular backup\restore history, job history, SSIS information, those are...