Tag Info

New answers tagged

-1

Further to Sporri's answer - you can check this if you are using SSMS. To view a database snapshot on a server: In Object Explorer, connect to the instance of the Microsoft SQL Server >Database Engine and then expand that instance. Expand Databases. Expand Database Snapshots, and select the snapshot you want to view. When you do this, ...


1

Yes you would: The original source database is overwritten by the reverted database, so any updates to the database since the snapshot's creation are lost. and The metadata of a reverted database is the same as the metadata at the time of the snapshot. Quotes from Revert a Database to a Database Snapshot in the MSDN Library.


12

You can use a query like this to calculate read/write rates and latency (though due to my laziness these figures are not in units that match Activity Monitor). SELECT d.name, f.name, f.type_desc, f.physical_name, [read b/ms] = num_of_bytes_read * 1.0/sample_ms, [avg read latency] = (1.0*s.io_stall_read_ms / (COALESCE(NULLIF(s.num_of_reads,0),1))), ...


1

You can run a query similar to the following that will show the number of reads and writes for files since SQL Server started. Change the number in line 6 to get stats for different databases. 1 = master, 2 = tempdb, 3 = model, etc. 5 and up will be for your user databases. SELECT files.physical_name, files.name, stats.num_of_writes, ...


0

If the crux of the question is, "How do I get correct data to size my storage subsystem?" and you want to it fairly repeatedly across many servers, use windows performance counters. Here is the list I would minimally have: Logical Disk(*)\Current Disk Queue Length Logical Disk(*)\Disk Read Bytes/Sec Logical Disk(*)\Disk Reads/Sec Logical Disk(*)\Disk Write ...


3

You need to use: DBMS_DATAPUMP.METADATA_FILTER(l_job_handle, 'EXCLUDE_PATH_EXPR', 'IN (''STATISTICS'')');


6

At least I think it is possible that the procedure gets a different plan and that way it doesn't touch the rows that have "invalid" data, for example numbers or dates stored as varchar that aren't correct and then conversion logic in the procedure. For example if you're fetching with both date range and customer code, and some of the data for that customer ...



Top 50 recent answers are included