if you perform a profile of the database and username you are using, the resulting output in the trace will usually list it right up the top. (run some sql statments via CF).
PS, use select db_id() against your database to get its ID, to put into the profile filters. PPS, I am referring to MS SQL Profiler in case you didn't know... ala >>> "Taco Fleur" <[EMAIL PROTECTED]> 06/07/2007 1:35 pm >>> maybe a stupid question, how do I find out whether the datasource is using one of the isolation levels? On 7/6/07, Scott Thornton <[EMAIL PROTECTED]> wrote: > > > It will apply as long as the datasources' connection isolation level you > are using is one of the ones it likes (READ COMMITTED, REPEATABLE READ). > > > >>> "Taco Fleur" <[EMAIL PROTECTED]> 06/07/2007 12:36 pm >>> > Hi Scott, > > > The readpast statement will apply to the query with the hint applied. > The above makes it sound like it will apply no matter what, as long as I > have it within the SELECT statement > > > Every query executed will be within the same Isolation level on your > database. > Then the above makes it sound like I need to do or check something? > > > So, the isolation level on your database will have to be one of the two > mentioned for it to work I imagine. > You're not completely sure either? ;-) > > >>> "Taco Fleur" <[EMAIL PROTECTED]> 06/07/2007 11:18 am >>> > I'm using the READPAST hint in MS SQL 2005, to allow select statements to > read data in a lock without waiting for it to be released. I think I > understand it, but need a bit of clarification on the following in red; > > Specifies that the Database Engine not read rows and pages that are locked > by other transactions. The Database Engine skips past the rows or pages > instead of blocking the current transaction until the locks are released. > READPAST can only be specified in transactions operating at the READ > COMMITTED or REPEATABLE READ isolation levels. When READPAST is specified > both row-level and page-level locks are skipped. READPAST can be specified > for any table referenced in an UPDATE or DELETE statement, and any table > referenced in a FROM clause. When specified in an UPDATE statement, > READPASTis applied only when reading data to identify which records to > update, > regardless of where in the statement it is specified. READPAST cannot be > specified for tables in the INTO clause of an INSERT statement. > > Read operations that use READPAST do not block. Update or delete > operations > that use READPAST may block when reading foreign keys or indexed views, or > when modifying secondary indexes. > -------------------------------------------- > can only be specified in transactions operating at the READ COMMITTED or > REPEATABLE READ isolation levels > > I'm not quite sure what that means, does it refer to the SELECT statement > using the READPAST hint or the statement using the locks? > any help much appreciated. > > -- > http://www.clickfind.com.au > The new Australian search engine for businesses, products and services > > > > > > > > > > -- > *** { . } { . } **** > http://www.clickfind.com.au > The new Australian search engine for businesses, products and services > > > > > > > -- *** { . } { . } **** http://www.clickfind.com.au The new Australian search engine for businesses, products and services --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
