There are a number of stored procedures involved in sql server based session
maintenance:
- TempUpdateStateItemShort
- TempResetTimeout
- TempUpdateStateItemLong
etc. These stored procs are executed by the framework, e.g.,
exec TempResetTimeout @id = '1iucllii0f42ksvfg4zsajae00000001'
Performing a trace shows many SP:CacheMiss (indicating perhaps that the
stored proc is recompiling everytime).
According to Q263889
( http://support.microsoft.com/default...;en-us;263889), the stored
proc owner (e.g., "dbo") should be specified in the call to avoid this
recompilation (or at least the cache miss).
Can anyone tell me if my assessment is correct? Will this optimization be
included in future .NET (1.1) Service Packs?
Thanks,
Jason Collins 5 2803
Frank gave you all the details... You just need to call the procedure as
owner.sp, in your case (probably) as dbo.TempResetTimeout instead of just
simply TempResetTimeout. This has absolutely nothing to do with .NET, unless
you want it to be magically guessing and changing your SQL statements when
it feels like you didn't really mean them...
Jerry
"MS News (MS ILM)" <sq**********@hotmail.com> wrote in message
news:ee**************@TK2MSFTNGP09.phx.gbl... What does that mean please give us more details
"Frank Drebin" <no*****@imsickofspam.com> wrote in message news:1Q**********************@newssvr28.news.prodi gy.com... That's a general SQL thing.. technically you should always reference as dbo.StoredProcName
"Jason Collins" <jc*************@point2.com> wrote in message news:uc**************@TK2MSFTNGP09.phx.gbl... There are a number of stored procedures involved in sql server based session maintenance:
- TempUpdateStateItemShort - TempResetTimeout - TempUpdateStateItemLong
etc. These stored procs are executed by the framework, e.g.,
exec TempResetTimeout @id = '1iucllii0f42ksvfg4zsajae00000001'
Performing a trace shows many SP:CacheMiss (indicating perhaps that
the stored proc is recompiling everytime).
According to Q263889 (http://support.microsoft.com/default...;en-us;263889), the stored proc owner (e.g., "dbo") should be specified in the call to avoid this recompilation (or at least the cache miss).
Can anyone tell me if my assessment is correct? Will this optimization be included in future .NET (1.1) Service Packs?
Thanks, Jason Collins
Except that the TempResetTimeout, etc. methods are .NET methods for session
maintenance; i.e., I have nothing to do with them, and can't alter them.
j
"Jerry III" <je******@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl... Frank gave you all the details... You just need to call the procedure as owner.sp, in your case (probably) as dbo.TempResetTimeout instead of just simply TempResetTimeout. This has absolutely nothing to do with .NET,
unless you want it to be magically guessing and changing your SQL statements when it feels like you didn't really mean them...
Jerry
"MS News (MS ILM)" <sq**********@hotmail.com> wrote in message news:ee**************@TK2MSFTNGP09.phx.gbl... What does that mean please give us more details
"Frank Drebin" <no*****@imsickofspam.com> wrote in message news:1Q**********************@newssvr28.news.prodi gy.com... That's a general SQL thing.. technically you should always reference
as dbo.StoredProcName
"Jason Collins" <jc*************@point2.com> wrote in message news:uc**************@TK2MSFTNGP09.phx.gbl... > There are a number of stored procedures involved in sql server based session > maintenance: > > - TempUpdateStateItemShort > - TempResetTimeout > - TempUpdateStateItemLong > > etc. These stored procs are executed by the framework, e.g., > > exec TempResetTimeout @id = '1iucllii0f42ksvfg4zsajae00000001' > > Performing a trace shows many SP:CacheMiss (indicating perhaps that the > stored proc is recompiling everytime). > > According to Q263889 > (http://support.microsoft.com/default...;en-us;263889),
the stored > proc owner (e.g., "dbo") should be specified in the call to avoid
this > recompilation (or at least the cache miss). > > Can anyone tell me if my assessment is correct? Will this
optimization be > included in future .NET (1.1) Service Packs? > > Thanks, > Jason Collins > >
You should do both, create it with a fully qualified name and call it with
one too. As for the tracing - I don't know, try using the SQL Server
profiler and look around. And if you can't figure it out ask in a SQL Server
newsgroup.
Jerry
"MS News (MS ILM)" <sq***********@hotmail.com> wrote in message
news:u7*************@TK2MSFTNGP09.phx.gbl... Jerry,
Couple of questions: call the procedure: is it like "create procedure dbo.AddModuleDefinition" and not as "create procedure AddModuleDefinition" OR when you actually invoke it? via exec or from Code?
How do you Performing a trace in SQL to show SP:CacheMiss
Thank you.
"Jerry III" <je******@hotmail.com> wrote in message news:%2****************@TK2MSFTNGP09.phx.gbl... Frank gave you all the details... You just need to call the procedure as owner.sp, in your case (probably) as dbo.TempResetTimeout instead of
just simply TempResetTimeout. This has absolutely nothing to do with .NET, unless you want it to be magically guessing and changing your SQL statements
when it feels like you didn't really mean them...
Jerry
"MS News (MS ILM)" <sq**********@hotmail.com> wrote in message news:ee**************@TK2MSFTNGP09.phx.gbl... What does that mean please give us more details
"Frank Drebin" <no*****@imsickofspam.com> wrote in message news:1Q**********************@newssvr28.news.prodi gy.com... > That's a general SQL thing.. technically you should always reference as > dbo.StoredProcName > > "Jason Collins" <jc*************@point2.com> wrote in message > news:uc**************@TK2MSFTNGP09.phx.gbl... > > There are a number of stored procedures involved in sql server
based > session > > maintenance: > > > > - TempUpdateStateItemShort > > - TempResetTimeout > > - TempUpdateStateItemLong > > > > etc. These stored procs are executed by the framework, e.g., > > > > exec TempResetTimeout @id = '1iucllii0f42ksvfg4zsajae00000001' > > > > Performing a trace shows many SP:CacheMiss (indicating perhaps
that the > > stored proc is recompiling everytime). > > > > According to Q263889 > > (http://support.microsoft.com/default...;en-us;263889), the > stored > > proc owner (e.g., "dbo") should be specified in the call to avoid this > > recompilation (or at least the cache miss). > > > > Can anyone tell me if my assessment is correct? Will this optimization be > > included in future .NET (1.1) Service Packs? > > > > Thanks, > > Jason Collins > > > > > >
Jerry,
Thank you for your answer(s)
"Jerry III" <je******@hotmail.com> wrote in message
news:O4**************@TK2MSFTNGP10.phx.gbl... You should do both, create it with a fully qualified name and call it with one too. As for the tracing - I don't know, try using the SQL Server profiler and look around. And if you can't figure it out ask in a SQL
Server newsgroup.
Jerry
"MS News (MS ILM)" <sq***********@hotmail.com> wrote in message news:u7*************@TK2MSFTNGP09.phx.gbl... Jerry,
Couple of questions: call the procedure: is it like "create procedure
dbo.AddModuleDefinition" and not as "create procedure AddModuleDefinition" OR when you
actually invoke it? via exec or from Code?
How do you Performing a trace in SQL to show SP:CacheMiss
Thank you.
"Jerry III" <je******@hotmail.com> wrote in message news:%2****************@TK2MSFTNGP09.phx.gbl... Frank gave you all the details... You just need to call the procedure
as owner.sp, in your case (probably) as dbo.TempResetTimeout instead of just simply TempResetTimeout. This has absolutely nothing to do with .NET, unless you want it to be magically guessing and changing your SQL statements when it feels like you didn't really mean them...
Jerry
"MS News (MS ILM)" <sq**********@hotmail.com> wrote in message news:ee**************@TK2MSFTNGP09.phx.gbl... > What does that mean please give us more details > > > "Frank Drebin" <no*****@imsickofspam.com> wrote in message > news:1Q**********************@newssvr28.news.prodi gy.com... > > That's a general SQL thing.. technically you should always
reference as > > dbo.StoredProcName > > > > "Jason Collins" <jc*************@point2.com> wrote in message > > news:uc**************@TK2MSFTNGP09.phx.gbl... > > > There are a number of stored procedures involved in sql server based > > session > > > maintenance: > > > > > > - TempUpdateStateItemShort > > > - TempResetTimeout > > > - TempUpdateStateItemLong > > > > > > etc. These stored procs are executed by the framework, e.g., > > > > > > exec TempResetTimeout @id = '1iucllii0f42ksvfg4zsajae00000001' > > > > > > Performing a trace shows many SP:CacheMiss (indicating perhaps that the > > > stored proc is recompiling everytime). > > > > > > According to Q263889 > > >
(http://support.microsoft.com/default...;en-us;263889), the > > stored > > > proc owner (e.g., "dbo") should be specified in the call to
avoid this > > > recompilation (or at least the cache miss). > > > > > > Can anyone tell me if my assessment is correct? Will this optimization > be > > > included in future .NET (1.1) Service Packs? > > > > > > Thanks, > > > Jason Collins > > > > > > > > > > > >
Yes, basically, I was posting here to bring it to someone at MS's
attention...
j
"Jerry III" <je******@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl... I see... Well, not much you can do unless you want to create your own session management. Maybe Microsoft will start following their own advice sometime in the future...
Jerry
"Jason Collins" <jc*************@point2.com> wrote in message news:%2****************@tk2msftngp13.phx.gbl... Except that the TempResetTimeout, etc. methods are .NET methods for
session maintenance; i.e., I have nothing to do with them, and can't alter them.
j
"Jerry III" <je******@hotmail.com> wrote in message news:%2****************@TK2MSFTNGP09.phx.gbl... Frank gave you all the details... You just need to call the procedure
as owner.sp, in your case (probably) as dbo.TempResetTimeout instead of just simply TempResetTimeout. This has absolutely nothing to do with .NET, unless you want it to be magically guessing and changing your SQL statements when it feels like you didn't really mean them...
Jerry
"MS News (MS ILM)" <sq**********@hotmail.com> wrote in message news:ee**************@TK2MSFTNGP09.phx.gbl... > What does that mean please give us more details > > > "Frank Drebin" <no*****@imsickofspam.com> wrote in message > news:1Q**********************@newssvr28.news.prodi gy.com... > > That's a general SQL thing.. technically you should always
reference as > > dbo.StoredProcName > > > > "Jason Collins" <jc*************@point2.com> wrote in message > > news:uc**************@TK2MSFTNGP09.phx.gbl... > > > There are a number of stored procedures involved in sql server based > > session > > > maintenance: > > > > > > - TempUpdateStateItemShort > > > - TempResetTimeout > > > - TempUpdateStateItemLong > > > > > > etc. These stored procs are executed by the framework, e.g., > > > > > > exec TempResetTimeout @id = '1iucllii0f42ksvfg4zsajae00000001' > > > > > > Performing a trace shows many SP:CacheMiss (indicating perhaps that the > > > stored proc is recompiling everytime). > > > > > > According to Q263889 > > >
(http://support.microsoft.com/default...;en-us;263889), the > > stored > > > proc owner (e.g., "dbo") should be specified in the call to
avoid this > > > recompilation (or at least the cache miss). > > > > > > Can anyone tell me if my assessment is correct? Will this optimization > be > > > included in future .NET (1.1) Service Packs? > > > > > > Thanks, > > > Jason Collins > > > > > > > > > > > >
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Jeager |
last post by:
Why is it, Microsoft manage to write operating systems and office
applications with every bell and whistle facility known to man. Yet,
even after years and years of development they still cannot...
|
by: steve |
last post by:
This event does not fire when session is stored in SQL or
in the SessionState service, this is documented. If you
think about, it has to be this way, because these
implementations are able to...
|
by: Abhilash.k.m |
last post by:
This is regarding the session management using Out of
proc session management(SQL SERVER). Among the samples
below which one is better to set the session?
1. There are 20 session...
|
by: jakk |
last post by:
Iam storing the session state in SQL Server. The Session gets stored in
the SQL Server temp tables ( I can see some values in the two tables),
but the session doesnt seem to timeout.
We have a...
|
by: |
last post by:
Simple question, I think...
I'm storing an object in the Session object.
In the code behind I read that object: trx = CType(Session("Transaction"), BOCSTransaction)
If I change any...
|
by: codegreen9 |
last post by:
Hi,
My understanding is that session info must be stored using
Session, which means text data. What I'd like to be able to do,
is keep an object alive throughout a user's session, without...
|
by: Jobs |
last post by:
Download the JAVA , .NET and SQL Server interview with answers
Download the JAVA , .NET and SQL Server interview sheet and rate
yourself. This will help you judge yourself are you really worth of...
|
by: raghav |
last post by:
Hi all
I am having a SP which is returning a value......Now I have to store
that value
in session...I saw some examples in msdn lib ---->
string Name=string.Empty;
Session=Name.ToString();
...
|
by: CloudSolutions |
last post by:
Introduction:
For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
|
by: Faith0G |
last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome former...
|
by: ryjfgjl |
last post by:
In our work, we often need to import Excel data into databases (such as MySQL, SQL Server, Oracle) for data analysis and processing. Usually, we use database tools like Navicat or the Excel import...
|
by: taylorcarr |
last post by:
A Canon printer is a smart device known for being advanced, efficient, and reliable. It is designed for home, office, and hybrid workspace use and can also be used for a variety of purposes. However,...
|
by: aa123db |
last post by:
Variable and constants
Use var or let for variables and const fror constants.
Var foo ='bar';
Let foo ='bar';const baz ='bar';
Functions
function $name$ ($parameters$) {
}
...
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
| |