My bad....you can only see it via dbcc pss(suid,spid) - look for pisolation=# ....should be about line 196 in the output....to see the output, you will need to do dbcc traceon(3604) first..... For example:
dbcc traceon(3604)
go
dbcc pss(1,24)
go
dbcc traceoff(3604)
go
....obviously you will need to look up both the suid and spid before execution. Area of interest will be:
pstringsize=50 pbulkbatchsize=0 pbulkarraysize=50
pretstat=0 pexecstep=0x0000000000000000 pcurstmt=0x000000008007F000 prepxdes=0x0000000000000000
psqlstatus=0 pfetchstatus=-1 pcursorrows=0
pplocks.lcstmtlocks=0x0000000031F13B10 pplocks.lcstmtl3locks=0x0000000031F13B20
pxlocks.lcstmtlocks=0x0000000031F13B30 pxlocks.lcstmtl3locks=0x0000000031F13B40
prepthreshold=0
ppllcfg_stat=0 pisolation=1
pexec_maxthread=1 pexec_maxthread_ext=0
pexec_maxscanthread=1 pexec_maxscanthread_ext=0
....vs. with isolation level three:
pstringsize=50 pbulkbatchsize=0 pbulkarraysize=50
pretstat=0 pexecstep=0x0000000000000000 pcurstmt=0x0000000080081000 prepxdes=0x0000000000000000
psqlstatus=0 pfetchstatus=-1 pcursorrows=0
pplocks.lcstmtlocks=0x0000000031F13B10 pplocks.lcstmtl3locks=0x0000000031F13B20
pxlocks.lcstmtlocks=0x0000000031F13B30 pxlocks.lcstmtl3locks=0x0000000031F13B40
prepthreshold=0
ppllcfg_stat=0 pisolation=3
pexec_maxthread=1 pexec_maxthread_ext=0
pexec_maxscanthread=1 pexec_maxscanthread_ext=0
I will check with engineering/support if our current ADO drivers have sp_reset_connection....don't see it in my default server build, but then I don't use ADO much.