Correct way of unistalling MSDE instance

Hi,
I am installing an MSDE instance using Setup ... call using a bat file.
I know the name of the instance (its a Given).
How do I uninstall automatically using a similar call?
I cannot afford to ask the user to uninstall it manually by using 'Add
remove programs'.
Also I would like to know if what I want to do is the correct way
or
Is there a standard way to uninstall (but not manually)?
In anycase I need to know how to uninstall an MSDE instance (Not MANUALLY) ?
Thanks
Subhojit
You can follow the following steps to uninstall manually.
Remove Files and Folders
Remove the MSDE 2000 instance data and program installation folders. You
can find the root folder information for the default instance data folder
in the SQLDataRoot registry key value under this registry key path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Setup
For example, remove the MSDE 2000 data folder for a default instance:
\Program Files\Microsoft SQL Server\MSSQL\Data
For example, remove the MSDE 2000 data folder for a named instance:
\Program Files\Microsoft SQL Server\MSSQL$<INSTANCENAME>\Data
For example, remove the MSDE 2000 program folder for a default instance:
\Program Files\Microsoft SQL Server\MSSQL\Binn
For example, remove the MSDE 2000 program folder for a named instance:
\Program Files\Microsoft SQL Server\MSSQL$<INSTANCENAME>\Binn
back to the top
Clean Up the Registry
WARNING : If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using
Registry Editor incorrectly. Use Registry Editor at your own risk.
The Msizap.exe tool removes only Windows Installer specific keys or data
for the ProductCode . It is best to manually remove the MSDE 2000 registry
keys. Use Registry Editor to remove the following MSDE 2000 registry keys:
For an MSDE 2000 default instance, remove the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
For an MSDE 2000 named instance, remove the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<INSTANCENAME>
If the following registry key points to the MSDE 2000 instance ProductCode
, remove the value InstanceComponentSet.x . For example,
InstanceComponentSet.1 has a value that matches the ProductCode of
Sqlrun01.msi:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Component
Set\InstanceComponentSet.1
Remove the SQLServer Service registry key.
For an MSDE 2000 default instance, remove the following:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQLServer
For an MSDE 2000 named instance, remove the following:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQL$<INSTANCENAME>
Remove the SQLServerAgent Service registry key:
For an MSDE 2000 default instance, remove the following:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLServerAgent
For an MSDE 2000 named instance, remove the following:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLAgent$<INSTANCENAME>
Girish Sundaram
Microsoft SQL Server Support Engineer
E-mail: girishs@.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Girish,
Thanks for replying.
**** "Just a request. Please read the posting before replying." ****
I really need to know how to uninstall MSDE instance "programatically" and
"not Manually".
Regards
"Girish Sundaram" wrote:

> You can follow the following steps to uninstall manually.
> Remove Files and Folders
> Remove the MSDE 2000 instance data and program installation folders. You
> can find the root folder information for the default instance data folder
> in the SQLDataRoot registry key value under this registry key path:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Setup
> For example, remove the MSDE 2000 data folder for a default instance:
> \Program Files\Microsoft SQL Server\MSSQL\Data
> For example, remove the MSDE 2000 data folder for a named instance:
> \Program Files\Microsoft SQL Server\MSSQL$<INSTANCENAME>\Data
> For example, remove the MSDE 2000 program folder for a default instance:
> \Program Files\Microsoft SQL Server\MSSQL\Binn
> For example, remove the MSDE 2000 program folder for a named instance:
> \Program Files\Microsoft SQL Server\MSSQL$<INSTANCENAME>\Binn
> back to the top
> Clean Up the Registry
> WARNING : If you use Registry Editor incorrectly, you may cause serious
> problems that may require you to reinstall your operating system. Microsoft
> cannot guarantee that you can solve problems that result from using
> Registry Editor incorrectly. Use Registry Editor at your own risk.
> The Msizap.exe tool removes only Windows Installer specific keys or data
> for the ProductCode . It is best to manually remove the MSDE 2000 registry
> keys. Use Registry Editor to remove the following MSDE 2000 registry keys:
> For an MSDE 2000 default instance, remove the following key:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
> For an MSDE 2000 named instance, remove the following key:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<INSTANCENAME>
> If the following registry key points to the MSDE 2000 instance ProductCode
> , remove the value InstanceComponentSet.x . For example,
> InstanceComponentSet.1 has a value that matches the ProductCode of
> Sqlrun01.msi:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Component
> Set\InstanceComponentSet.1
>
> Remove the SQLServer Service registry key.
> For an MSDE 2000 default instance, remove the following:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQLServer
> For an MSDE 2000 named instance, remove the following:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQL$<INSTANCENAME>
>
> Remove the SQLServerAgent Service registry key:
> For an MSDE 2000 default instance, remove the following:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLServerAgent
> For an MSDE 2000 named instance, remove the following:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLAgent$<INSTANCENAME>
>
> Girish Sundaram
> Microsoft SQL Server Support Engineer
> E-mail: girishs@.microsoft.com
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Possibly you can use a batch file to delete the folders from the drives.
You can use a script to delete the registry entries. The command to do so
is shown below.
The command that you can use to remove registry entries is
xp_deletevalue
Syntax:
xp_deletevalue hive, key, value
Example:
EXEC master..xp_regdeletevalue 'HKEY_LOCAL_MACHINE',
'Software\Clients', 'PaulWehland'
Hope this answers your query
Girish Sundaram
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi -
As you probably know, you can manually remove an MSDE instance using the
add/remove programs in the Control Panel. While that doesn't 'completely'
remove MSDE, you can do the same thing programmatically:
1. Read the MSDE GUID value from the Registry Key:
<MSDEGUID> = HKLM\SOFTWARE\Microsoft\Microsoft SQL
Server\<YourInstanceName>\Setup\ProductCode
2. Execute: msiexec.exe /x "<MSDEGUID>"
I've not found a way to _completely_ remove MSDE programmatically, but the
above may do what you need. Hope it helps.
- Jeff
"Subhojit Banerjee" <SubhojitBanerjee@.discussions.microsoft.com> wrote in
message news:A60CFD94-FC3F-4EA0-BDC1-3D490579BA7C@.microsoft.com...[vbcol=seagreen]
> Hi Girish,
> Thanks for replying.
> **** "Just a request. Please read the posting before replying." ****
> I really need to know how to uninstall MSDE instance "programatically" and
> "not Manually".
> Regards
>
> "Girish Sundaram" wrote:
folder[vbcol=seagreen]
Microsoft[vbcol=seagreen]
registry[vbcol=seagreen]
keys:[vbcol=seagreen]
Server\<INSTANCENAME>[vbcol=seagreen]
ProductCode[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQL$<INSTANCENAME>[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLAgent$<INSTANCENAME>[vbcol=seagreen]
rights.[vbcol=seagreen]

Correct term for SQL-server..?

Hi all,
Some people say: 'sequelserver' about SQL-server.
I suppose that comes from the Sybase days before Microsoft.
Is it correct to call SQL-server for 'sequelserver'?
No big issue - i know.
/Kent J.I think "sequel" is common currency just because S-Q-L is a bit of a
mouthful. In speech (but never in writing) "sequel" is synonymous with the
general term "SQL", it doesn't just refer to Microsoft SQL Server.
David Portas
SQL Server MVP
--|||Either 'S'-'Q'-"L' or sequel pronunciation is correct. I usually use the
latter. Most people don't care. Those that do have way too much free time
on their hands.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Kent Johnson" <08.6044303@.telia.com> wrote in message
news:g1Cad.105856$dP1.393062@.newsc.telia.net...
> Hi all,
> Some people say: 'sequelserver' about SQL-server.
> I suppose that comes from the Sybase days before Microsoft.
> Is it correct to call SQL-server for 'sequelserver'?
> No big issue - i know.
> /Kent J.
>|||Kent Johnson wrote:
> Hi all,
> Some people say: 'sequelserver' about SQL-server.
> I suppose that comes from the Sybase days before Microsoft.
> Is it correct to call SQL-server for 'sequelserver'?
> No big issue - i know.
> /Kent J.
I say "sequel"-Server when referring to the program "SQL Server" and
normally say "S-Q-L" when referring to the language... Monday through
Thursday. On Friday it's just "sequel".
David Gugick
Imceda Software
www.imceda.com|||The SQL Server development team at Microsoft generally use the "sequel
server" pronunciation.
Alan Brewer [MSFT]
Lead programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights|||The SQL language originated from a prototype language named SEQUEL. They (Or
acle, IBM) couldn't use
that name in their products as it was already registered. That, in combinati
on with that it is
easier to pronounce, is probably why a lot of us say "sequel" instead of "S-
Q-L".
I prefer to say "sequel" in English and "S-Q-L" in Swedish. :-)
And I agree that it doesn't really matter. Use what feels best for you.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Kent Johnson" <08.6044303@.telia.com> wrote in message
news:g1Cad.105856$dP1.393062@.newsc.telia.net...
> Hi all,
> Some people say: 'sequelserver' about SQL-server.
> I suppose that comes from the Sybase days before Microsoft.
> Is it correct to call SQL-server for 'sequelserver'?
> No big issue - i know.
> /Kent J.
>

Correct term for SQL-server..?

Hi all,
Some people say: 'sequelserver' about SQL-server.
I suppose that comes from the Sybase days before Microsoft.
Is it correct to call SQL-server for 'sequelserver'?
No big issue - i know.
/Kent J.I think "sequel" is common currency just because S-Q-L is a bit of a
mouthful. In speech (but never in writing) "sequel" is synonymous with the
general term "SQL", it doesn't just refer to Microsoft SQL Server.
--
David Portas
SQL Server MVP
--|||Either 'S'-'Q'-"L' or sequel pronunciation is correct. I usually use the
latter. Most people don't care. Those that do have way too much free time
on their hands. :)
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Kent Johnson" <08.6044303@.telia.com> wrote in message
news:g1Cad.105856$dP1.393062@.newsc.telia.net...
> Hi all,
> Some people say: 'sequelserver' about SQL-server.
> I suppose that comes from the Sybase days before Microsoft.
> Is it correct to call SQL-server for 'sequelserver'?
> No big issue - i know.
> /Kent J.
>|||Kent Johnson wrote:
> Hi all,
> Some people say: 'sequelserver' about SQL-server.
> I suppose that comes from the Sybase days before Microsoft.
> Is it correct to call SQL-server for 'sequelserver'?
> No big issue - i know.
> /Kent J.
I say "sequel"-Server when referring to the program "SQL Server" and
normally say "S-Q-L" when referring to the language... Monday through
Thursday. On Friday it's just "sequel".
--
David Gugick
Imceda Software
www.imceda.com|||The SQL Server development team at Microsoft generally use the "sequel
server" pronunciation.
--
Alan Brewer [MSFT]
Lead Programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights|||The SQL language originated from a prototype language named SEQUEL. They (Oracle, IBM) couldn't use
that name in their products as it was already registered. That, in combination with that it is
easier to pronounce, is probably why a lot of us say "sequel" instead of "S-Q-L".
I prefer to say "sequel" in English and "S-Q-L" in Swedish. :-)
And I agree that it doesn't really matter. Use what feels best for you.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Kent Johnson" <08.6044303@.telia.com> wrote in message
news:g1Cad.105856$dP1.393062@.newsc.telia.net...
> Hi all,
> Some people say: 'sequelserver' about SQL-server.
> I suppose that comes from the Sybase days before Microsoft.
> Is it correct to call SQL-server for 'sequelserver'?
> No big issue - i know.
> /Kent J.
>sql

Correct term for SQL-server..?

Hi all,
Some people say: 'sequelserver' about SQL-server.
I suppose that comes from the Sybase days before Microsoft.
Is it correct to call SQL-server for 'sequelserver'?
No big issue - i know.
/Kent J.
I think "sequel" is common currency just because S-Q-L is a bit of a
mouthful. In speech (but never in writing) "sequel" is synonymous with the
general term "SQL", it doesn't just refer to Microsoft SQL Server.
David Portas
SQL Server MVP
|||Either 'S'-'Q'-"L' or sequel pronunciation is correct. I usually use the
latter. Most people don't care. Those that do have way too much free time
on their hands.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Kent Johnson" <08.6044303@.telia.com> wrote in message
news:g1Cad.105856$dP1.393062@.newsc.telia.net...
> Hi all,
> Some people say: 'sequelserver' about SQL-server.
> I suppose that comes from the Sybase days before Microsoft.
> Is it correct to call SQL-server for 'sequelserver'?
> No big issue - i know.
> /Kent J.
>
|||Kent Johnson wrote:
> Hi all,
> Some people say: 'sequelserver' about SQL-server.
> I suppose that comes from the Sybase days before Microsoft.
> Is it correct to call SQL-server for 'sequelserver'?
> No big issue - i know.
> /Kent J.
I say "sequel"-Server when referring to the program "SQL Server" and
normally say "S-Q-L" when referring to the language... Monday through
Thursday. On Friday it's just "sequel".
David Gugick
Imceda Software
www.imceda.com
|||The SQL Server development team at Microsoft generally use the "sequel
server" pronunciation.
Alan Brewer [MSFT]
Lead Programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
|||The SQL language originated from a prototype language named SEQUEL. They (Oracle, IBM) couldn't use
that name in their products as it was already registered. That, in combination with that it is
easier to pronounce, is probably why a lot of us say "sequel" instead of "S-Q-L".
I prefer to say "sequel" in English and "S-Q-L" in Swedish. :-)
And I agree that it doesn't really matter. Use what feels best for you.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Kent Johnson" <08.6044303@.telia.com> wrote in message
news:g1Cad.105856$dP1.393062@.newsc.telia.net...
> Hi all,
> Some people say: 'sequelserver' about SQL-server.
> I suppose that comes from the Sybase days before Microsoft.
> Is it correct to call SQL-server for 'sequelserver'?
> No big issue - i know.
> /Kent J.
>

Copying a full-text index from 1 DB to another...

Hi everyone,
I noticed that when I did an export on a database (lets call it DB_a)
to another one (lets call it DB_b) it did not copy over the full text
index (FTI) that was on DB_a.
Is there anyway I can get the FTI from DB_a to be copied over to DB_b
without having to rebuild the FTI on DB_b'
Would appreciate any comments/hints/user-experience that you may like
to share.
Thanking you,
Al.What version of SQL Server are you using. If both servers are SQL Server
2005 then detach/attach should work fine.
almurph@.altavista.com wrote in
news:1153478984.289344.12530@.i3g2000cwc.googlegroups.com:

> I noticed that when I did an export on a database (lets call it
> DB_a)
> to another one (lets call it DB_b) it did not copy over the full text
> index (FTI) that was on DB_a.
> Is there anyway I can get the FTI from DB_a to be copied over to
> DB_b
> without having to rebuild the FTI on DB_b'
> Would appreciate any comments/hints/user-experience that you may
> like
> to share.
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||HI
For SQL 2000 you may want to look at http://support.microsoft.com/kb/240867/
and other methods and useful information about moving/copying databases may
be found at http://support.microsoft.com/kb/314546
John
"almurph@.altavista.com" wrote:

> Hi everyone,
>
> I noticed that when I did an export on a database (lets call it DB_a)
> to another one (lets call it DB_b) it did not copy over the full text
> index (FTI) that was on DB_a.
> Is there anyway I can get the FTI from DB_a to be copied over to DB_b
> without having to rebuild the FTI on DB_b'
> Would appreciate any comments/hints/user-experience that you may like
> to share.
> Thanking you,
> Al.
>

Copying a full-text index from 1 DB to another...

Hi everyone,
I noticed that when I did an export on a database (lets call it DB_a)
to another one (lets call it DB_b) it did not copy over the full text
index (FTI) that was on DB_a.
Is there anyway I can get the FTI from DB_a to be copied over to DB_b
without having to rebuild the FTI on DB_b'
Would appreciate any comments/hints/user-experience that you may like
to share.
Thanking you,
Al.What version of SQL Server are you using. If both servers are SQL Server
2005 then detach/attach should work fine.
almurph@.altavista.com wrote in
news:1153478984.289344.12530@.i3g2000cwc.googlegroups.com:
> I noticed that when I did an export on a database (lets call it
> DB_a)
> to another one (lets call it DB_b) it did not copy over the full text
> index (FTI) that was on DB_a.
> Is there anyway I can get the FTI from DB_a to be copied over to
> DB_b
> without having to rebuild the FTI on DB_b'
> Would appreciate any comments/hints/user-experience that you may
> like
> to share.
--
Ole Kristian Bangås
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging, MCTS, MCITP|||HI
For SQL 2000 you may want to look at http://support.microsoft.com/kb/240867/
and other methods and useful information about moving/copying databases may
be found at http://support.microsoft.com/kb/314546
John
"almurph@.altavista.com" wrote:
> Hi everyone,
>
> I noticed that when I did an export on a database (lets call it DB_a)
> to another one (lets call it DB_b) it did not copy over the full text
> index (FTI) that was on DB_a.
> Is there anyway I can get the FTI from DB_a to be copied over to DB_b
> without having to rebuild the FTI on DB_b'
> Would appreciate any comments/hints/user-experience that you may like
> to share.
> Thanking you,
> Al.
>

Copy Tables in SQL 2k5 - Need Help

I have a database - we can call it DatabaseX and I want to copy the tables, keys and indexes to DatabaseY. I tried doing and export/import and it worked for the data but the identity settings were lost. How can I maintain the integrity of the tables and copy the data at the same time?

The Copy Database Wizard is an option when Service Pack 2 is released. Currently Service Pack 2 is available as a CTP http://www.microsoft.com/sql/ctp.mspx|||

simple way is to follow conventional Backup/Resotre method... if it is on the same machine there is no issue.. otherwise u may need to transfer the logins also....

Refer

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlbackuprest.mspx

also in BOL Backup database /restore database

Madhu

|||

If you want to copy objects into database X which already exists and has objects you can use bcp with the -E switch to keep identity values.

See SQL Server 2005 Books Online topic:
bcp Utility
http://msdn2.microsoft.com/en-US/library/ms162802.aspx

You can also use the SSIS Transfer Objects task.