default isolation level

Hi all,
the default isolation level in sql 2k is read committed..
say incase i am connecting to the DB through a jdbc driver and the
application has a default isolation level of repeatable read...
when a transaction is opened from the application end...wat would be the
isolation level...
ll the db override or the application takes up priority..
any help on the context is appreciated..
thnks
anu
Application should override the default level.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Anuradha" <Anuradha@.discussions.microsoft.com> wrote in message
news:C46A6429-6D51-40BF-A4EE-9584224F3625@.microsoft.com...
> Hi all,
> the default isolation level in sql 2k is read committed..
> say incase i am connecting to the DB through a jdbc driver and the
> application has a default isolation level of repeatable read...
> when a transaction is opened from the application end...wat would be the
> isolation level...
> ll the db override or the application takes up priority..
> any help on the context is appreciated..
> thnks
> anu

default isolation level

Hi all,
the default isolation level in sql 2k is read committed..
say incase i am connecting to the DB through a jdbc driver and the
application has a default isolation level of repeatable read...
when a transaction is opened from the application end...wat would be the
isolation level...
ll the db override or the application takes up priority..
any help on the context is appreciated..
thnks
anuApplication should override the default level.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Anuradha" <Anuradha@.discussions.microsoft.com> wrote in message
news:C46A6429-6D51-40BF-A4EE-9584224F3625@.microsoft.com...
> Hi all,
> the default isolation level in sql 2k is read committed..
> say incase i am connecting to the DB through a jdbc driver and the
> application has a default isolation level of repeatable read...
> when a transaction is opened from the application end...wat would be the
> isolation level...
> ll the db override or the application takes up priority..
> any help on the context is appreciated..
> thnks
> anu

default database

Hi all,
I want to delete a particular database 'r3risk', But when I delete it, I
have problems when connecting via sqlmanager. It gives me an error about the
default database, which is set at 'r3risk', which I've deleted. I've had to
restore and reatach in order to connect via sql manager.
Where and how can I change what the default database is. SQL manager options
in the database properties is greyed out.
Thanks
RobertEasiest is to use sp_defaultdb.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Robert Bravery" <me@.u.com> wrote in message news:eKg6bNWPGHA.2696@.TK2MSFTNGP14.phx.gbl...[
color=darkred]
> Hi all,
> I want to delete a particular database 'r3risk', But when I delete it, I
> have problems when connecting via sqlmanager. It gives me an error about t
he
> default database, which is set at 'r3risk', which I've deleted. I've had t
o
> restore and reatach in order to connect via sql manager.
> Where and how can I change what the default database is. SQL manager optio
ns
> in the database properties is greyed out.
> Thanks
> Robert
>[/color]

Debugger on remote machine

Looks like a permission issue. Check the permission of the
user connecting locally vs the user connecting remotely.
This might give you some clue.
HTH.
Obaid.
>--Original Message--
>We have a remote server (w 2000, sql 2000) where we can
debug stored procedures locally but cannot debug stored
procedures remotely. Has anyone encountered this?
>.
>It's the same user.
What I'm noticing is that when debugging is done localy, the debugger pause
s on the first line. All of the debugging icons are active. In profler ther
e are two calls to sp_sdidebug (the first passes a 'check', parm the second
passes an 'on' parm) and s
et implicit transactions statement. If you then press F5 the code executes.
In profiler the procedure is executed and then there is a call to sp_sdide
bug (passes an 'off' parm).
When debugging locally, the code appears to immediately execute and the debu
gging icons are grayed out. This is confirmed in profiler where there are t
he two calls to sp_sdidebug, the procedure is executed and there is the call
to sp_sdidebug with the of
f parameter. So the code appears to execute immediately rather than being pa
used, and the debugger is disabled.|||KB article 328151 had the solution to our problem. The T-SQL Debugger is tu
rned off for non-sp3 clients after you install sp3. We're having our develo
pers upgrade their client tools to sp3. You can also run sp_sdidebug 'legacy
_on' each time you reboot t
he server.

Debugger on remote machine

Looks like a permission issue. Check the permission of the
user connecting locally vs the user connecting remotely.
This might give you some clue.
HTH.
Obaid.
>--Original Message--
>We have a remote server (w 2000, sql 2000) where we can
debug stored procedures locally but cannot debug stored
procedures remotely. Has anyone encountered this?
>.
>
It's the same user.
What I'm noticing is that when debugging is done localy, the debugger pauses on the first line. All of the debugging icons are active. In profler there are two calls to sp_sdidebug (the first passes a 'check', parm the second passes an 'on' parm) and s
et implicit transactions statement. If you then press F5 the code executes. In profiler the procedure is executed and then there is a call to sp_sdidebug (passes an 'off' parm).
When debugging locally, the code appears to immediately execute and the debugging icons are grayed out. This is confirmed in profiler where there are the two calls to sp_sdidebug, the procedure is executed and there is the call to sp_sdidebug with the of
f parameter. So the code appears to execute immediately rather than being paused, and the debugger is disabled.