Ya I am more concerned about the time involved here. We don't have the space for alot of full's or differentials. So I was wondering about applying alot ot t-logs...

not a nested stored procedure.

ya it is a 7.0 database.

I issue a dbcc shrinkfile for the log and I have truncate log on checkpoint enabled. After the dbcc shrinkfile is ran I issue a...

isolated environment for testing purposes maybe.

This is the way I see it,

1. A Client connection to SQL Server

2. SQL Server assigns one of the available threads it has assuming there are free ones(MAX WORKER THREADS)

3....

BOL:

Threads allow complex applications to make more effective use of a CPU even on computers with a single CPU. With one CPU, only one thread can execute at a time....

also, why is it some log file will shrink right away and others won't at all or take time to shrink?

how does an EMC SAN work with this?

I think we have 16GB of cache on the SAN here.

Write-through?

Write-back?

AH,

this is kinda tricky.

In 2000 profiler, you have to wait for all the rows to be put in Profiler(no indicator) before the greyed out save as will be...

ya you must be using 7.0 profiler. I just got the same result are you.

you using 2000 profiler?

when I open an existing .trc file,

the SAVE AS options are greyed out.

that won't work.

This did:

fn_trace_gettable

ex.

USE PERFORMANCEDB

SELECT * INTO globexSTR50b

FROM ::fn_trace_gettable('G:\Perf_Logs\Globex_STR_Oct29\globexSTR50b.trc', default)

comments Steve?

no sorry.

I want a book on distributed transactions.

More of an architectural book on transactions.