Showing posts with label security. Show all posts
Showing posts with label security. Show all posts

Monday, March 26, 2012

How can i change security mode of SQL Server Express 2005

Hello,
I have created one application in visual studio 2005 and also created setup project of that application. now i want to install SQL Server Express edition with my application. so i have checked SQL Server Express 2005 in Setup Project Properities(Prerequisites...). now i want to change SQL Secirty Mode during setup. and i don't know how can we do this?

Any idia?

Thread moved to the appropriate forum|||

hi,

SQLExpress setup boostrapper accept "parameters" to define the "final" settings of the installed instance at install time..

the parameter you are looking for is SECURITYMODE=SQL to enable standard SQL Server authenticated connections..

please have a look at http://msdn2.microsoft.com/en-us/library/ms144259.aspx for all supported parameters..

regards

|||

Thank for sujession, but still it is not work.
i have entered following line for change SQL Server Security Mode Windows Auth. To SQL Auth.

Start /wait setup.exe /qb INSTANCENAME=SQLEXPRESS SECURITYMODE=SQL SAPWD=pwd12345

i have also tried this :

Start /wait setup.exe /qb UPGRADE=Client_Components INSTANCENAME=SQLEXPRESS SECURITYMODE=SQL SAPWD=pwd12345

but still it is not work. i got the same error when i run my program "Login fail for user sa. The user is not associated with a trusted SQL Server connection.

|||

hi,

the exception is correctly related to not enabled SQL Server authenticated connections..

but the SECURITYMODE=SQL parameter is there for the case, and it "must" work as expected, as it really does since MSDE 2000 installer...

please pardon me, but are you sure you are later connecting to the correct SQLExpress instance?

regards

|||

Yes i connecting to correct SQLExpress instance.

but don't warry, it's solve now bcoz i directly change parameter in package.xml(Program Files\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\SqlExpress\en) file.

How can i change security mode of SQL Server Express 2005

Hello,
I have created one application in visual studio 2005 and also created setup project of that application. now i want to install SQL Server Express edition with my application. so i have checked SQL Server Express 2005 in Setup Project Properities(Prerequisites...). now i want to change SQL Secirty Mode during setup. and i don't know how can we do this?

Any idia?

Thread moved to the appropriate forum|||

hi,

SQLExpress setup boostrapper accept "parameters" to define the "final" settings of the installed instance at install time..

the parameter you are looking for is SECURITYMODE=SQL to enable standard SQL Server authenticated connections..

please have a look at http://msdn2.microsoft.com/en-us/library/ms144259.aspx for all supported parameters..

regards

|||

Thank for sujession, but still it is not work.
i have entered following line for change SQL Server Security Mode Windows Auth. To SQL Auth.

Start /wait setup.exe /qb INSTANCENAME=SQLEXPRESS SECURITYMODE=SQL SAPWD=pwd12345

i have also tried this :

Start /wait setup.exe /qb UPGRADE=Client_Components INSTANCENAME=SQLEXPRESS SECURITYMODE=SQL SAPWD=pwd12345

but still it is not work. i got the same error when i run my program "Login fail for user sa. The user is not associated with a trusted SQL Server connection.

|||

hi,

the exception is correctly related to not enabled SQL Server authenticated connections..

but the SECURITYMODE=SQL parameter is there for the case, and it "must" work as expected, as it really does since MSDE 2000 installer...

please pardon me, but are you sure you are later connecting to the correct SQLExpress instance?

regards

|||

Yes i connecting to correct SQLExpress instance.

but don't warry, it's solve now bcoz i directly change parameter in package.xml(Program Files\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\SqlExpress\en) file.

Sunday, February 19, 2012

Hot Fix 826161

After applied this hot fix (SQL2000Tools-KB826161-8.00.0819) on the server t
hat has the security patch MS-031 installed, the version number remains at 8
.00.818. Is it supposed to change to 8.00.819?
Do we have the hot fix for SQL 7? Same problem in SQL 7 as it described for
SQL 2000.The build number in the filename of the patch is not necessarily the level
that the file patches sqlservr.exe to... if you re-read the article, it
clearly shows that sqlservr.exe becomes 2000.80.818.0 ... this is what
@.@.VERSION returns.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"RC5640808" <anonymous@.discussions.microsoft.com> wrote in message
news:AF037BF8-210D-40D6-A797-8C783AF17425@.microsoft.com...
> After applied this hot fix (SQL2000Tools-KB826161-8.00.0819) on the server
that has the security patch MS-031 installed, the version number remains at
8.00.818. Is it supposed to change to 8.00.819?
> Do we have the hot fix for SQL 7? Same problem in SQL 7 as it described
for SQL 2000.
>|||Hi
As this fix does not contain a new version of SQLServr.exe the version
number will not change. The hotfix for machines that do not have MS-031 does
have a version of the file which is labelled 818. I am not sure about SQL
Server 7.
John
"RC5640808" <anonymous@.discussions.microsoft.com> wrote in message
news:AF037BF8-210D-40D6-A797-8C783AF17425@.microsoft.com...
> After applied this hot fix (SQL2000Tools-KB826161-8.00.0819) on the server
that has the security patch MS-031 installed, the version number remains at
8.00.818. Is it supposed to change to 8.00.819?
> Do we have the hot fix for SQL 7? Same problem in SQL 7 as it described
for SQL 2000.
>|||I found that once this hot fix is applied, it also fixes the problem for SQL
7.
I think probably is only a bug in the EM and only one copy of EM for the ser
ver that has both SQL 7 and 2000 instances.
Thanks.|||This is correct. The problem is in Enterprise Manager for SQL Server 2000.
It does not affect SQL Server 2000 or SQL Server 7.0 from the server side,
on ly the client side. This is why the problem does not occur for SQL
Server 7.0 after you applied the fix.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Hot Fix 826161

After applied this hot fix (SQL2000Tools-KB826161-8.00.0819) on the server that has the security patch MS-031 installed, the version number remains at 8.00.818. Is it supposed to change to 8.00.819?
Do we have the hot fix for SQL 7? Same problem in SQL 7 as it described for SQL 2000.
The build number in the filename of the patch is not necessarily the level
that the file patches sqlservr.exe to... if you re-read the article, it
clearly shows that sqlservr.exe becomes 2000.80.818.0 ... this is what
@.@.VERSION returns.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"RC5640808" <anonymous@.discussions.microsoft.com> wrote in message
news:AF037BF8-210D-40D6-A797-8C783AF17425@.microsoft.com...
> After applied this hot fix (SQL2000Tools-KB826161-8.00.0819) on the server
that has the security patch MS-031 installed, the version number remains at
8.00.818. Is it supposed to change to 8.00.819?
> Do we have the hot fix for SQL 7? Same problem in SQL 7 as it described
for SQL 2000.
>
|||Hi
As this fix does not contain a new version of SQLServr.exe the version
number will not change. The hotfix for machines that do not have MS-031 does
have a version of the file which is labelled 818. I am not sure about SQL
Server 7.
John
"RC5640808" <anonymous@.discussions.microsoft.com> wrote in message
news:AF037BF8-210D-40D6-A797-8C783AF17425@.microsoft.com...
> After applied this hot fix (SQL2000Tools-KB826161-8.00.0819) on the server
that has the security patch MS-031 installed, the version number remains at
8.00.818. Is it supposed to change to 8.00.819?
> Do we have the hot fix for SQL 7? Same problem in SQL 7 as it described
for SQL 2000.
>
|||I found that once this hot fix is applied, it also fixes the problem for SQL 7.
I think probably is only a bug in the EM and only one copy of EM for the server that has both SQL 7 and 2000 instances.
Thanks.
|||This is correct. The problem is in Enterprise Manager for SQL Server 2000.
It does not affect SQL Server 2000 or SQL Server 7.0 from the server side,
on ly the client side. This is why the problem does not occur for SQL
Server 7.0 after you applied the fix.
Rand
This posting is provided "as is" with no warranties and confers no rights.