re:
You could aim to different instances
Not needed.
re:
or different databases (not sure how to do the later).
It's easily done by using the -d parameter when you run aspnet_regsql.exe
for ASP.NET 2.0, or modify installsqlstate.sql for the 1.1 version.
You need to modify the other two install*.sql files if you change the default name for 1.1:
installpersistsqlstate.sql and installsqlstatetemplate.sql ( as opposed to changing the
database name for 2.0 )
For ASP.NET 2.0, run ''aspnet_regsql.exe -?'' for details.
You will need to change one or the other, since the default name for both is "ASPState"
The databases are quite different, and pointing each ASP.NET
version to a differently-named database will work fine.
Juan T. Llibre, asp.net MVP
aspnetfaq.com :
http://www.aspnetfaq.com/
asp.net faq :
http://asp.net.do/faq/
foros de asp.net, en español :
http://asp.net.do/foros/
===================================
"Cowboy (Gregory A. Beamer)" <No************@comcast.netNoSpamMwrote in message
news:%2****************@TK2MSFTNGP06.phx.gbl...
The session state should be the same, but I would not feel comfortable using the same exact SLQ
Server database for session state for both, making me inclined to say no.
You could aim to different instances or different databases (not sure how to do the later).
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com
*************************************************
Think outside of the box!
*************************************************
"jnick" <jn***@discussions.microsoft.comwrote in message
news:43**********************************@microsof t.com...
>Can both ASP.NET 2.0 Session State and ASP.NET 1.1 co-exist in SQL Server?
