--=_NextPart_000_0039_01C61CD7.AAB6F060
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
Hi,
I have SQLExpress database under App_Data folder of my ASP.NET = application, can I just deploy this to production (where SQL 2005) is = running and it'll still work?
--=_NextPart_000_0039_01C61CD7.AAB6F060
Content-Type: text/html;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hi,
I have SQLExpress database under = App_Data folder of my ASP.NET application, can I just deploy this to production (where SQL = 2005) is running and it'll still work?
--=_NextPart_000_0039_01C61CD7.AAB6F060--This is a multi-part message in MIME format.
--=_NextPart_000_01DC_01C61CE6.488EED20
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
Probably. You may have to deal with some user mapping and permissions =issue because your production system will have different logins than =your SQL Express instance.
-- This posting is provided "AS IS" with no warranties, and confers no =rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"GS" <nospam@.nowhere.com> wrote in message =news:uLSg2nQHGHA.2948@.TK2MSFTNGP10.phx.gbl...
Hi,
I have SQLExpress database under App_Data folder of my ASP.NET =application, can I just deploy this to production (where SQL 2005) is =running and it'll still work?
--=_NextPart_000_01DC_01C61CE6.488EED20
Content-Type: text/html;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Probably. You may have to deal =with some user mapping and permissions issue because your production system will have =different logins than your SQL Express instance.
-- This posting is provided "AS IS" with no warranties, and =confers no rights.Use of included script samples are subject to the terms =specified athttp://www.microsoft.com/info/cpyright.htm">http://www.microsoft.=com/info/cpyright.htm
"GS"
Hi,
I have SQLExpress database under =App_Data folder of my ASP.NET application, can I just deploy this to production (where =SQL 2005) is running and it'll still =work?
--=_NextPart_000_01DC_01C61CE6.488EED20--|||This is a multi-part message in MIME format.
--=_NextPart_000_0065_01C61CFC.A6F072B0
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
It does not work saying "The user instance login flag is not supported =on this version of SQL Server'
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message =news:eYNBXlSHGHA.3056@.TK2MSFTNGP09.phx.gbl...
Probably. You may have to deal with some user mapping and permissions =issue because your production system will have different logins than =your SQL Express instance.
-- This posting is provided "AS IS" with no warranties, and confers no =rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"GS" <nospam@.nowhere.com> wrote in message =news:uLSg2nQHGHA.2948@.TK2MSFTNGP10.phx.gbl...
Hi,
I have SQLExpress database under App_Data folder of my ASP.NET =application, can I just deploy this to production (where SQL 2005) is =running and it'll still work?
--=_NextPart_000_0065_01C61CFC.A6F072B0
Content-Type: text/html;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
It does not work saying "The user =instance login flag is not supported on this version of SQL Server'
"Roger Wolter[MSFT]"
Probably. You may have to deal =with some user mapping and permissions issue because your production system will =have different logins than your SQL Express instance.
-- This posting is provided "AS IS" with no warranties, =and confers no rights.Use of included script samples are subject to =the terms specified athttp://www.microsoft.com/info/cpyright.htm">http://www.microsoft.=com/info/cpyright.htm
"GS"
Hi,
I have SQLExpress database under =App_Data folder of my ASP.NET application, can I just deploy this to =production (where SQL 2005) is running and it'll still work?
--=_NextPart_000_0065_01C61CFC.A6F072B0--|||This is a multi-part message in MIME format.
--=_NextPart_000_0205_01C61CEE.968B17D0
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
You will have to take the User Instance flag out of your connections =strings, attach the database to the production system and then establish =users and permissions in the production system.
There's some discussion of converting to User Instance to normal =connections here:
http://msdn.microsoft.com/sql/express/default.aspx?pull=3D/library/en-us/=
dnsse/html/sqlexpuserinst.asp
-- This posting is provided "AS IS" with no warranties, and confers no =rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"GS" <nospam@.nowhere.com> wrote in message =news:ucH0y7SHGHA.3916@.TK2MSFTNGP10.phx.gbl...
It does not work saying "The user instance login flag is not supported =on this version of SQL Server'
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message =news:eYNBXlSHGHA.3056@.TK2MSFTNGP09.phx.gbl...
Probably. You may have to deal with some user mapping and =permissions issue because your production system will have different =logins than your SQL Express instance.
-- This posting is provided "AS IS" with no warranties, and confers no =rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"GS" <nospam@.nowhere.com> wrote in message =news:uLSg2nQHGHA.2948@.TK2MSFTNGP10.phx.gbl...
Hi,
I have SQLExpress database under App_Data folder of my ASP.NET =application, can I just deploy this to production (where SQL 2005) is =running and it'll still work?
--=_NextPart_000_0205_01C61CEE.968B17D0
Content-Type: text/html;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
You will have to take the User Instance =flag out of your connections strings, attach the database to the production =system and then establish users and permissions in the production =system.
There's some discussion of converting =to User Instance to normal connections here:
http://msdn.microsoft.com/sql/expr=ess/default.aspx?pull=3D/library/en-us/dnsse/html/sqlexpuserinst.asp
-- This posting is provided "AS IS" with no warranties, and =confers no rights.Use of included script samples are subject to the terms =specified athttp://www.microsoft.com/info/cpyright.htm">http://www.microsoft.=com/info/cpyright.htm
"GS"
It does not work saying "The user =instance login flag is not supported on this version of SQL Server'
"Roger Wolter[MSFT]"
Probably. You may have to =deal with some user mapping and permissions issue because your production system =will have different logins than your SQL Express instance.
-- This posting is provided "AS IS" with no warranties, =and confers no rights.Use of included script samples are subject to =the terms specified athttp://www.microsoft.com/info/cpyright.htm">http://www.microsoft.=com/info/cpyright.htm
"GS"
Hi,
I have SQLExpress database under =App_Data folder of my ASP.NET application, can I just deploy this to =production (where SQL 2005) is running and it'll still =work?
--=_NextPart_000_0205_01C61CEE.968B17D0--
No comments:
Post a Comment