Installing named instance with sample.msi

I need to install a named instance of the Desktop Engine, so I followed the directions at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_74qd.asp
which has instructions on using Orca to modify sample.msi. I also followed the instructions found at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_8yeq.asp
on how to edit the msi file to create a named instance.
YET, when used, this altered msi installs a DEFAULT instance.
Am I missing something? If so, what?

Thanks for any help,
Allan Sorenson
Crossroads technologyOriginally posted by B1ueboy
I need to install a named instance of the Desktop Engine, so I followed the directions at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_74qd.asp
which has instructions on using Orca to modify sample.msi. I also followed the instructions found at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_8yeq.asp
on how to edit the msi file to create a named instance.
YET, when used, this altered msi installs a DEFAULT instance.
Am I missing something? If so, what?

Thanks for any help,
Allan Sorenson
Crossroads technology

A little more info on the last edit:
Using Orca I added the row named 'SqlInstanceName' with the desired instance name as the value to the 'Property' table.

installing MSDE and instance name

Hi Joe,
The little server icon is called Service Manager and it does not list the
named instances.
To check the status of the named instance that you have installed, you can
type the server name in the Severbox. It is a dropdown cum text box. So you
will be able to type the SQL Server Name.
For a named instance, the SQL Server name would be
<computername>\<Instancename>.
In your case it would be <computername>\JoesDB01.
After typing the server name, click on Refresh Services button and it
should show you the state of the different services, like the SQL Server,
SQL Server Agent, Distributed Transaction Coordinator.
You can control the state of each Service,
1. Start - Click on this to start/Continue the service, if it is Stopped or
Paused
2. Stop - Click on this to stop the Service.
3. Pause - Click on this to pause the service. Pausing, will allow the
current users to work and will not allow new users to connect to the SQL
Server.
You can also installed the SQL Web Data Administrator, to create and manage
Database from
http://www.microsoft.com/downloads/d...798-C57A-419E-
ACBC-2A332CB7F959&displaylang=en
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
Great! This helped a lot. Things seem to be working fine now
Thanks Ashish!
-- Joe
sql

installing anther sql2005 instance

Hi,
I have installed sql2005 default instance, and I need to install anther named instance. but when I tried to install the s/w it does not give option for new instance instead, it shows only uninstall option.
How can I install anther nameds instance;
thanks in advance.Did you do an upgrade of an existing SQL 2000 instance?

There are a considerable number of factors that would prevent this;
http://support.microsoft.com/kb/910228/en-us?spid=2855&sid=312

Installing a Named SQL Instance

I am migrating a SQL Instance to an existing SQL 2000 cluster that already
has the default instance installed. There is a large user community that
will be accessing the databases in the 2nd instance and I am trying to find a
way to configure the installation so that they can continue to use the same
ODBC connections. Today, they are configured using a single name (such as
RAVEN). Is it possible to configure the 2nd instance using this single name?
Thanks in advance.
You should be able to create a DNS SRV record to point to the named
instance.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Brian" <Brian@.discussions.microsoft.com> wrote in message
news:9FC76909-7CB6-48E2-A5E5-236F7665A150@.microsoft.com...
I am migrating a SQL Instance to an existing SQL 2000 cluster that already
has the default instance installed. There is a large user community that
will be accessing the databases in the 2nd instance and I am trying to find
a
way to configure the installation so that they can continue to use the same
ODBC connections. Today, they are configured using a single name (such as
RAVEN). Is it possible to configure the 2nd instance using this single
name?
Thanks in advance.
|||I remember doing this on a migration, and i had issues with some clients
trying to access using the new DNS record, it ws solved applying MDAC 2.8.
I hope you don't run in this error but try to check this is you experience
any problem.
"Tom Moreau" wrote:

> You should be able to create a DNS SRV record to point to the named
> instance.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Brian" <Brian@.discussions.microsoft.com> wrote in message
> news:9FC76909-7CB6-48E2-A5E5-236F7665A150@.microsoft.com...
> I am migrating a SQL Instance to an existing SQL 2000 cluster that already
> has the default instance installed. There is a large user community that
> will be accessing the databases in the 2nd instance and I am trying to find
> a
> way to configure the installation so that they can continue to use the same
> ODBC connections. Today, they are configured using a single name (such as
> RAVEN). Is it possible to configure the 2nd instance using this single
> name?
> Thanks in advance.
>
|||I assumed he was using current MDAC, but that's a good point.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Frivas" <Frivas@.discussions.microsoft.com> wrote in message
news:3DFCE095-1AD3-42E5-B97B-D38570E13B8D@.microsoft.com...
I remember doing this on a migration, and i had issues with some clients
trying to access using the new DNS record, it ws solved applying MDAC 2.8.
I hope you don't run in this error but try to check this is you experience
any problem.
"Tom Moreau" wrote:

> You should be able to create a DNS SRV record to point to the named
> instance.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Brian" <Brian@.discussions.microsoft.com> wrote in message
> news:9FC76909-7CB6-48E2-A5E5-236F7665A150@.microsoft.com...
> I am migrating a SQL Instance to an existing SQL 2000 cluster that already
> has the default instance installed. There is a large user community that
> will be accessing the databases in the 2nd instance and I am trying to
> find
> a
> way to configure the installation so that they can continue to use the
> same
> ODBC connections. Today, they are configured using a single name (such as
> RAVEN). Is it possible to configure the 2nd instance using this single
> name?
> Thanks in advance.
>
|||Named Instance support was introduced in MDAC 2.6. If you have to use an
earlier MDAC stack, you must alias the named instance using the client
network utility on each client.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Frivas" <Frivas@.discussions.microsoft.com> wrote in message
news:3DFCE095-1AD3-42E5-B97B-D38570E13B8D@.microsoft.com...[vbcol=seagreen]
>I remember doing this on a migration, and i had issues with some clients
> trying to access using the new DNS record, it ws solved applying MDAC 2.8.
> I hope you don't run in this error but try to check this is you experience
> any problem.
> "Tom Moreau" wrote:

Installing A Default Instance AFTER a Named Instance??

I have SQL Server 2000 Standard Edition (sp3a) running on a windows 2003 (sp4) Server.

It is a Production Server with 3 NAMED Instances and NO Default Instance.

Does anyone know if I can rerun the SQL Server Install and add a DEFAULT Instance to this box without disrupting the other Named Instances?Except for a reboot after the install, you should have no problems installing a default instance.|||Thank you : )|||Will the default instance automatically have the name of the Server - or is there a way to give it name - like you would a named instance.. sorry if the question sounds stupid.. : )|||The default instance will have the name of the server. The only way around this that I can think of off the top of my head is to give the machine a DNS alias.|||Thanks !!! I'm not so much worried about the name as I am Blowing up the Server by installing a Default Instance AFTER it has already been populated with Named Instances.

Installing 2nd (Named) Instance of SQL Server 2005 EE

When installing a 2nd instance of SQL Server 2005 EE on a server, is it
necessary to install Reporting Services, SSIS, and Analysis Services again?
Does anyone know of any good documentation that discusses this subject?
Thanks.
No, if you need just an OLTP and / or olap named instance, you don't have to
reinstall RS or AS; you cannot install a second instance of SSIS because SSIS
is a stand alone service and you cannot have two SSIS on the same server.
The first documentation you have to read is the setup documentation;
Gilberto
"MACason" wrote:

> When installing a 2nd instance of SQL Server 2005 EE on a server, is it
> necessary to install Reporting Services, SSIS, and Analysis Services again?
> Does anyone know of any good documentation that discusses this subject?
> Thanks.

Installing 2nd (Named) Instance of SQL Server 2005 EE

When installing a 2nd instance of SQL Server 2005 EE on a server, is it
necessary to install Reporting Services, SSIS, and Analysis Services again?
Does anyone know of any good documentation that discusses this subject?
Thanks.Thanks. Appreciate the prompt reply.
"Gilberto Zampatti" wrote:
> No, if you need just an OLTP and / or olap named instance, you don't have to
> reinstall RS or AS; you cannot install a second instance of SSIS because SSIS
> is a stand alone service and you cannot have two SSIS on the same server.
> The first documentation you have to read is the setup documentation;
> Gilberto
> "MACason" wrote:
> > When installing a 2nd instance of SQL Server 2005 EE on a server, is it
> > necessary to install Reporting Services, SSIS, and Analysis Services again?
> > Does anyone know of any good documentation that discusses this subject?
> >
> > Thanks.|||No, if you need just an OLTP and / or olap named instance, you don't have to
reinstall RS or AS; you cannot install a second instance of SSIS because SSIS
is a stand alone service and you cannot have two SSIS on the same server.
The first documentation you have to read is the setup documentation;
Gilberto
"MACason" wrote:
> When installing a 2nd instance of SQL Server 2005 EE on a server, is it
> necessary to install Reporting Services, SSIS, and Analysis Services again?
> Does anyone know of any good documentation that discusses this subject?
> Thanks.sql

Installed SQLServer 2005 TrialEdition

Hi Fellows,

I am really in a fix.I have downloaded the trial version from MIcrosoft site and run setup with named instance. But I cannot find my management console link anywhere. Can anyone help me here .

My site is : Windows XP Professional SP2

Installed : SQLServer 2005 180Day Trial Pack downloaded from Microsoft Network.

I ran setup from : server directory and also from tools directory.

In my programes menu I can only see Configuration Toolsunder which there are three options :

1) SQL Server Configuration Tool

2) SQL Server Surface Configuration Tool and

3) SQL Server Error and Usage Reporting

Is it SQL Server 2005 Enterprise edition? XP SP2 does not support Enterprise edition. You need server operating systems to support Enterprise edition such as W2K SP4, W2K3 EE SP2, Longhorn Server.

|||

I dont know . I just downloaded the server from MSDN site it was an x86 executable file . My PC is a Win XP Professional on our internal Domain .

|||What does the Splash screen tell you ? After calling the installer you should get the splah screen showing the dition type you are trying to install.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||

Hi

I just uninstalled everything and run the installer again . It says SQL 2005 Server but does not give anytype of edition. However now I find that the Management Console is appearing in the program menu.

Thanks to all . But I am still mystified as to why it should do like this .

Regards

|||Strange thing, I just started my ISO and it directly gives me the edition type as of [1]

[1] http://www.sqlserver2005.de/SharedFiles/SplashScreen.jpg

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||Two questions:

1/How did you uninstall everything? I uninstalled in the wrong order from add/remove programs now I am in three quarters installed limbo. [Ghosting the machine seems the simplest way out].

2/I did not get the tools setup to work, or the sample database install in the server directory, the error message was (in both cases)
"The following components that you chose to install are already installed on the machine. To view a report of available options and alternatives click on Details."
Clicking on details was unhelpful (said to maintain components from add/remove programs)
[The components that were already installed did not mention the sample databases]

This is on Windows 2000 SP4, with sqlserver 2005 evaluation edition.

Thank you for your time,
Turloch|||

Hi

I simply went to the Add/remove programs and selected the Microsoft SQL Server 2005 , clicked remove . It asked and it simply removed it clean including the native client etc. Although the Add/Remove page still shows the name it has actually removed the product. To remove the name from the list you will have to select them one by one and click remove. It will prompt you with something like 'This program can only be used for removing installed options' Just click Ok and the entry will go away .

For the tools setup to work when you install you will get a page after the SQL support files and Native client are installed wherein you are asked to choose what you wish to install . Select both the SQL database services as well as the Client tools ( Last option on the page ) then click next .

Regards

|||Thanks...

I went add/remove [the wrong sql server component first] and the computer removed the entry in add/remove programs but left the program (mostly) intact [I had to repair .net from the add/remove programs section]

>For

the tools setup to work when you install you will get a page after the

SQL support files and Native client are installed wherein you are asked

to choose what you wish to install . Select both the SQL database

services as well as the Client tools ( Last option on the page ) then

click next .

I still get the error/warning:

"The following

components that you chose to install are already installed on the

machine. To view a report of available options and alternatives click

on Details."

[Component is:

Workstation components, Books Online and development tools 9:00.1399.06]

Maybe I was just unlucky not to choose the databases on my first install.

I can install the sample databases that have there own msi, I suppose I can create a test

database and or try to attach those database files for now, thanks.

Thank you for your time,

Turloch

|||[FYI: I attached the demo databases installed as .msi files into my limping sql server install]|||I didn′t understand your last reply, is the problem solved ?

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||

Yes I managed to resolve the problem . Here is what I did

1) Went to Add/Remove programs

2) Select MS SQL Server 2005

3) Clicked on Remove ( It asked me what components I want to remove so I checked Both Database Server and Workgroup Client )

4) Then removed everything else that was MS SQL

5) Re-ran the setup file

Wala .. I had the SQL Server Management Console in the Program List.

Thanks all

Regards

Installation of the SQL 2000 after SQL 2005

Hello,

We got a problem, we have default instance of the SQL 2005, and it owns 1433 port. We need to install named instance of the SQL 2000, problem that it installs using port 1304, that is not default. Of course we can use this port in the connection string, but may be some sort of the solution exists?

Bydefault default instance uses 1433. So next instance has to have someother port. WHat is the problem in using 1304. If you want to use 1433 for SQL Server 2000, then you can change the port of default instance manually to someother port and you can use 1433 for sql server 2000

Madhu

Installation of Multiple named instances in Cluster environment

Hi All..

We are planning to build a cluster environment on MS SQL 2005. We want to install multiple named instances in a single database server and use cluster for that database server.

Is this option possible ? Any relevant documentation would be helpful

Thanks in advance

Regards

Madhav

Yes, you can install multiple instances of SQL Server into a cluster. All of the relevant information can be found in Books Online.|||

here is some supplemental information to Books Online that was recently published:

SQL Server Failover Clustering White Paper
http://www.microsoft.com/downloads/details.aspx?FamilyID=818234dc-a17b-4f09-b282-c6830fead499&DisplayLang=en

Installation HELP please

I am trying to install MSDERelA on two machines one with SQL Server installed
(default) as a named instance and one without SQL Server (default). The OS is
XP Pro. The installation stops and logs the following error at the bottom of
the log:
DATABASE = C:\Docume~1\JIMHOP~1\Temp\f0ed6.msi
OriginalDatabase = C:\MSDERelA\setup\Run01.msi
UILevel = 3
ACTION = Install
====Logging Stopped===
Note: 1: 1708
Product: Microsoft SQL Server Desktop Engine -- Installation operation failed
I have no clue what this means or how to fix it. Any ideas? It won't install
at all.
Jim
Look for "Return value 3", and try to figure out from there why it failed.
When MSDE installation fails, it rollbacks every thing, so make sure you
check for the message before you click on 'Ok' Button when you get a error.
You can alternatively use DISSABLEROLLBACK=1 to stop installer from
rollback and /L*v <Log file name and path> to have a log file at a given
path.