Friday, March 30, 2012
instances of MSDE
for some reasons the password (or the instance) get
corrupted after I try to upsize a table from MS Access to
an existing database in MSDE (I'll stop doing this).
But now I have multiple instances which I would like to
clean up. Does anybody know how to uninstall them?
Thanks
Perry
Hi ,
You can use the following information to uninstall msde.
A)Remove the following registry:
1) Remove the following ID_Number from your MSDE 2.0 instance
HKEY_CLASSES_ROOT\Installer\Products\ID_Number
-- It has key value name 'ProductName' which displays the instance name.
For example, "ProductName" = Microsoft SQL Server Desktop Engine
(MYINSTANCE)
2)If you had patch applied on this MSDE 2.0 instance, you need to remove
ID_Number
for that MSDE 2.0 instance:
HKEY_CLASSES_ROOT\Installer\Patches\ID_Number
3) For MSDE 2.0 Default instance, remove
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
For MSDE 2.0 named instance, remove
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\Your_instance_name
4)If you have the following key points to MSDE 2.0 productGUID, then remove
the
InstanceComponentSet.x
For example, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\Component
SetInstanceComponentSet.x
-- For example, InstanceComponentSet.1 the has value matching the
productGUID of
sqlrun01.msi.
5)Remove :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Uninstall\Produ
ctGUID
-- the Product GUID which refers to your MSDE 2.0 instance.
6)Remove the Sql server service key:
For MSDE 2.0 default instance, remove
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQLServer
For MSDE 2.0 named instance, remove
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQL$Your_Instance_Nam
e
7)Remove the Sql server agent service key:
For MSDE 2.0 default instance, remove
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLServerAgent
For MSDE 2.0 named instance, remove
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLAgent$Your_Instance_
Name
B)Remove the MSDE 2.0 instance data and program install directory:
For example, G:\Program Files\Microsoft SQL
Server\MSSQL$Your_instanceName\data
For example, G:\Program Files\Microsoft SQL
Server\MSSQL$Your_instanceName\binn
Now rerun the msde setup from the command prompt
Girish Sundaram
This posting is provided "AS IS" with no warranties, and confers no rights.
Wednesday, March 28, 2012
Installing with MSDE on XP
to install it gave me an error A strong SA password is required for
security reasons. Please use SAPWD switch
I do not know how it handle this error if you can please let me how to
install in XP.
Step by Step process.
Thanking You
Your's Truly
Raj
hi Raj,
Raj wrote:
> I would like to install MSDE in Windows XP Professional. When I tried
> to install it gave me an error A strong SA password is required for
> security reasons. Please use SAPWD switch
> I do not know how it handle this error if you can please let me how to
> install in XP.
> Step by Step process.
Setup.exe is a boostrap intaller for MSDE and accepts parameters you can
provide at the command line as long as in a companion .Ini file..
at
http://msdn.microsoft.com/library/de...stsql_84xl.asp
you can find the list of all supported parameters...
please open a DOS command window and navigate to the folder hosting the
setup.exe file...
there you can run setup.exe with all the parameters of your choice..
- usually you have to provide the SAPWD parameter to specify a strong
password for the "sa" builtin login in order to protect it from both
internal and external attacks..
specify then
SAPWD=your_strong_password
- additional parameters let you specify if you want a named instance or a
default instance... specify
INSTANCENAME=your_instance_name
if you want a named instance...
- another parameter let you specify if you want to allow remote connections
from other PCs in your lan to your MSDE instance.. specify
DISABLENETWORKPROTOCOLS=0
if you need this feature...
- by default, MSDE is installed allowing only WindowsNT authenticated
connections and preventing standard SQL Server authenticated ones.. more on
this at http://support.microsoft.com/default...b;en-us;325022
you can specify
SECURITYMODE=SQL
to allow mixed mode security, thus allowing both WInNT integrated security
and standard SQL Server authenticated connections..
- the final important parameter is
/L*v "c:\msdelog.txt"
where you will allow verbose logging of the installation process, resulting
in a text file of about 2mb for a successfull installation you can inspect,
in case of problems, for
RETURN VALUE 3
entries... about 10 lines before each entry some (sometime cryptic)
description of the problwm will be reported..
so, if you like to install a "named instace" named "Raj" with mixed security
and enabled network protocols for remote connections you can run setup.exe
boostrap installer providing all parameters as
c:\..\>setup.exe /qb INSTANCENAME=Raj SECURITYMODE=SQL
DISABLENETWORKPROTOCOLS=0 SAPWD=your_strong_password /L*v "c:\msdelog.txt"
you can later manage your installed instance via the native character tool
oSql.exe as described at
http://support.microsoft.com/default...;EN-US;q325003 or use a
third party tool, both commercial or free, like the ones listed at
http://www.microsoft.com/sql/msde/partners/ or
http://www.aspfaq.com/show.asp?id=2442... google for further..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Wednesday, March 7, 2012
Installing Sql Express on a Peer to Peer Network Log in and Password problems
hi,
SQLExpress installs by default diabling standard SQL Server authenticated connections...
you can modify that behaviour at install time, specifying the SECURITYMODE=SQL parameter if you execute the setup wit command line parameters or setup.ini file, or in the installation wizard unchecking the "hide advanced features" check box.. a successive wizard task will enable you to define "Mixed mode" as connection option...
if you like to enable Mixed mode after installation, you can manually "hack" the Windows registry modifying the
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.3\MSSQLServer
LoginMode = 2
key, where MSSQL.3 identifies your SQLExpress database engine or, more user friendly, you can use the SQL Server Management Studio Express graphical tool to modify the setting..
log in as a member of system administrator, select the Database Engine node in the Object Browser.. rx click->Properties.. in the "Security" tab select "SQL Server and Windows Authentication mode"..
when you are finished, select the Security->Logins node.. select the "sa" login, rx click->Properties.. set a strong password for this special super account.. in the "Status" tab, set "Login: Enabled" property...
restart the SQLExpress instance..
you can now add your own standard SQL Server logins as desired..
regards
|||Thanks for your help up and running and testing.Installing Sql Express on a Peer to Peer Network Log in and Password problems
hi,
SQLExpress installs by default diabling standard SQL Server authenticated connections...
you can modify that behaviour at install time, specifying the SECURITYMODE=SQL parameter if you execute the setup wit command line parameters or setup.ini file, or in the installation wizard unchecking the "hide advanced features" check box.. a successive wizard task will enable you to define "Mixed mode" as connection option...
if you like to enable Mixed mode after installation, you can manually "hack" the Windows registry modifying the
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.3\MSSQLServer
LoginMode = 2
key, where MSSQL.3 identifies your SQLExpress database engine or, more user friendly, you can use the SQL Server Management Studio Express graphical tool to modify the setting..
log in as a member of system administrator, select the Database Engine node in the Object Browser.. rx click->Properties.. in the "Security" tab select "SQL Server and Windows Authentication mode"..
when you are finished, select the Security->Logins node.. select the "sa" login, rx click->Properties.. set a strong password for this special super account.. in the "Status" tab, set "Login: Enabled" property...
restart the SQLExpress instance..
you can now add your own standard SQL Server logins as desired..
regards
|||Thanks for your help up and running and testing.