Last post Sep 15, 2008 06:12 PM by Bruce L
Sep 14, 2008 02:29 PM|oleksandr|LINK
I'm using SQL 2005 (not Express edition) to store ASP.NET session state in web application (SQLServer sessionState mode). To set up the state database the following command is used:
aspnet_regsql -sqlexportonly d:\InstallSqlState.sql -d my_aspnet_state_DB -sstype c -ssadd
my_aspnet_state_DB database already exists and is supposed to contain not only ASP.NET state data.
My intention is to include generated script into bunch of database deployment scripts (which are executed also at development server during every application build).
But there's a line in generated InstallSqlState.sql script saying
"Do not run this file manually.
You should use aspnet_regsql.exe to install
and uninstall SQL session state."
So, my question is, why shouln't I run the SQL script manually? Should I instead include "aspnet_regsql -ssadd ..." command into build sequence?
Sep 14, 2008 04:40 PM|etariq|LINK
intrsting i wanna know to?!
Sep 15, 2008 06:12 PM|Bruce L|LINK
There's no technical reason why you can't run this script manually, we've been doing this for our customers for several years and have not had problems.I think this is just one of those "disclaimer" to scare people off from running the script manually.