'Instances' of SQL Server 2000?

Our application requires multiple instances of SQL Server 2000 in order to h
ave multiple databases, which the app clients use. Has something to do with
the name of the SQL Server instance; each instance needs to be named differe
ntly.
How does this work? Do I install SQL Server multiple times in different loca
tions, or is it simply a defined thing in SQL Server? Is there a 'per instan
ce' licensing issue, or will my one SQL Server license cover the multiple in
stances of SQL Server on on
e server system?
Thanks,
JohnI believe Standard edition is licensed per instance but Enterprise Edition
can be installed with multiple instances on a server. It's best to check
the EULA to be totally certain though. But having to buy one new copy of SE
could be worth looking at why this very odd requirement was "assumed" in the
application's design IMO.
hth
Eric
John wrote:
> Our application requires multiple instances of SQL Server 2000 in
> order to have multiple databases, which the app clients use. Has
> something to do with the name of the SQL Server instance; each
> instance needs to be named differently.
> How does this work? Do I install SQL Server multiple times in
> different locations, or is it simply a defined thing in SQL Server?
> Is there a 'per instance' licensing issue, or will my one SQL Server
> license cover the multiple instances of SQL Server on one server
> system?
> Thanks,
> John|||> Our application requires multiple instances of SQL Server 2000 in order to
have multiple databases
That's the part I don't get. Why can't the application use multiple
databases in a single instance?

> How does this work? Do I install SQL Server multiple times in different
locations
For multiple instances, yes.

> Is there a 'per instance' licensing issue
Depending on the edition of SQL Server, the licensing model you're using,
the OS, etc. You really should verify licensing compliance with a local
Microsoft rep. They can give you the legal answer as opposed to collating a
variety of opinions here.
http://www.aspfaq.com/
(Reverse address to reply.)|||It is poor design IMO, but I have to live with it. On the matter of the mult
iple instances, what is meant by 'instance'? multiple installations? multipl
e 'spawnings' of SQL Server under a parent 'SQL Server manager-like' server
process? does it end up loo
king like multiple servers systems each running a SQL Server, each with diff
erent names, data paths, etc, but actually all running on the same server sy
stem?
John
"Eric Sabine" wrote:

> I believe Standard edition is licensed per instance but Enterprise Edition
> can be installed with multiple instances on a server. It's best to check
> the EULA to be totally certain though. But having to buy one new copy of
SE
> could be worth looking at why this very odd requirement was "assumed" in t
he
> application's design IMO.
> hth
> Eric
> John wrote:
>
>|||Think of an instance of how many times you ran setup.exe through completion
of the wizard. Every instance after the default (if the default is taken
at first install) has the name of the server _and_ instance name as the name
of the sql server itself.
John wrote:[vbcol=seagreen]
> It is poor design IMO, but I have to live with it. On the matter of
> the multiple instances, what is meant by 'instance'? multiple
> installations? multiple 'spawnings' of SQL Server under a parent 'SQL
> Server manager-like' server process? does it end up looking like
> multiple servers systems each running a SQL Server, each with
> different names, data paths, etc, but actually all running on the
> same server system?
> John
> "Eric Sabine" wrote:
>

'Instances' of SQL Server 2000?

Our application requires multiple instances of SQL Server 2000 in order to have multiple databases, which the app clients use. Has something to do with the name of the SQL Server instance; each instance needs to be named differently.
How does this work? Do I install SQL Server multiple times in different locations, or is it simply a defined thing in SQL Server? Is there a 'per instance' licensing issue, or will my one SQL Server license cover the multiple instances of SQL Server on on
e server system?
Thanks,
John
I believe Standard edition is licensed per instance but Enterprise Edition
can be installed with multiple instances on a server. It's best to check
the EULA to be totally certain though. But having to buy one new copy of SE
could be worth looking at why this very odd requirement was "assumed" in the
application's design IMO.
hth
Eric
John wrote:
> Our application requires multiple instances of SQL Server 2000 in
> order to have multiple databases, which the app clients use. Has
> something to do with the name of the SQL Server instance; each
> instance needs to be named differently.
> How does this work? Do I install SQL Server multiple times in
> different locations, or is it simply a defined thing in SQL Server?
> Is there a 'per instance' licensing issue, or will my one SQL Server
> license cover the multiple instances of SQL Server on one server
> system?
> Thanks,
> John
|||> Our application requires multiple instances of SQL Server 2000 in order to
have multiple databases
That's the part I don't get. Why can't the application use multiple
databases in a single instance?

> How does this work? Do I install SQL Server multiple times in different
locations
For multiple instances, yes.

> Is there a 'per instance' licensing issue
Depending on the edition of SQL Server, the licensing model you're using,
the OS, etc. You really should verify licensing compliance with a local
Microsoft rep. They can give you the legal answer as opposed to collating a
variety of opinions here.
http://www.aspfaq.com/
(Reverse address to reply.)
|||It is poor design IMO, but I have to live with it. On the matter of the multiple instances, what is meant by 'instance'? multiple installations? multiple 'spawnings' of SQL Server under a parent 'SQL Server manager-like' server process? does it end up loo
king like multiple servers systems each running a SQL Server, each with different names, data paths, etc, but actually all running on the same server system?
John
"Eric Sabine" wrote:

> I believe Standard edition is licensed per instance but Enterprise Edition
> can be installed with multiple instances on a server. It's best to check
> the EULA to be totally certain though. But having to buy one new copy of SE
> could be worth looking at why this very odd requirement was "assumed" in the
> application's design IMO.
> hth
> Eric
> John wrote:
>
>
|||Think of an instance of how many times you ran setup.exe through completion
of the wizard. Every instance after the default (if the default is taken
at first install) has the name of the server _and_ instance name as the name
of the sql server itself.
John wrote:[vbcol=seagreen]
> It is poor design IMO, but I have to live with it. On the matter of
> the multiple instances, what is meant by 'instance'? multiple
> installations? multiple 'spawnings' of SQL Server under a parent 'SQL
> Server manager-like' server process? does it end up looking like
> multiple servers systems each running a SQL Server, each with
> different names, data paths, etc, but actually all running on the
> same server system?
> John
> "Eric Sabine" wrote:
sql

Instance and Application databases?

Hi... I came across the terms "instance database" and "application database" in a book "MCITP 70-444: Optimizing and Maintaining... SQL Server 2005".

Up until now, I thought there were "user databases" and "system databases."

I found an article about these new terms here: http://msdn2.microsoft.com/en-us/library/ms166482.aspx

Are these terms specific to Notification Services?

Hi,

Yes. It is.

Application database is a database like any other database that you might create and it holds subscriber and device information.

Instance database is again a database like any other database that you might create and it holds subscription, events and other information.

Note that both the above database are created by Notification Services based on the inforamition that you provide in Application Definition File and Instance Definiton File.

Shamir|||Thanks.... this book is talking about designing a database for the first time and giving consideration to long term growth. The "application-" and "instance databases" then came way out of left field and confused me. I have added this note about Notification Services to the book so I won't have to re-ask. Thanks!|||In SSNS 2005 the instance and application object may now be created in an existing database, however you'll still routinely see those objects collectively referred to as the instance and application databases.

I've described the process of creating those objects in an existing database here.

HTH..

Joe

installing the sample databases and documentation

There are two instances: SQL2005 and SQL2005Express on two different units. While there is Visual Studio 2005 Team Edition also installed on the units have not attempted these component installs through either yet. Have spent the better part of two days, following all the directions having searched help locally, online, technet,and applied their advice respectively. While I've taken out the old instances, downloaded updated ones in both my SQL Server instances they do not show as installed under Programs->SQL Server (whichever instance)->Tutorials ...However they do show installed in Control Panel and they can be found via Explorer (AdWorks DBCI+AdWorks BICI and Express instance on the other unit. Have also download SP2 and installed it, but this has proved of no help. @. My wits' end, any help will be appreciated.

Documentation and sample databases are an option during installation.

Books Online appears as an installed program in Add/Remove Programs but the sample databases do not.

If AdventureWorks was installed with 2005 but did not appear in Object Explorer you can attach it. Attach is on the right-click menu of Databases in Object Explorer.

|||

You can also find the SQL Server 2005 documentation available online at:

http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx

It has many great tutorials to get started.

Thanks,
Sam Lester (MSFT)

|||Thank you for your suggestion Lester, however before my initial post had already consulted books online, and downloaded the latest version to stay in sync with the software. Part of my frustration comes from following their directions but failing to achieve similar outcomes. Adventure Works databases are definitely resident on my computer, though not in the same directories in the Explorer file hierarchy indicated by the manuals/instructions. The directions have been exhaustively followed a number of times, replete with uninstalls then reinstalls - all to no avail. This is the case in both units, each with a different operating system and different version of SQL. Am still stymied.

Installing SSRS 2005 in web server and cluster environment.

Hi,

I am installing SSRS 2005 with the following scenario:

- Report Server and Report Manager will be installed on web server

- The repository databases (ReportServer and ReportServerTempDB) will be hosted in SQL2005 cluster server.

Both servers are running Win2003 SP1, SQL/SSRS 2005 SP1

When I try to browse the ReportServer virtual directory from IIS on the web server, the system keep asking username and password. After 3 times trials and it failed eventhough the username and password is correct.

The error message is:

HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials.
Internet Information Services (IIS)

I've been searching on the web and found couple of articles talking about this issue. I've tried some of them like: http://support.microsoft.com/kb/887993 or even this one: http://groups.google.ca/group/microsoft.public.sqlserver.reportingsvcs/browse_frm/thread/991c9178ceab8f58/8f1a447aa60ad837?lnk=st&q=reporting+services+the+server+is+not+responding&rnum=3&hl=en#8f1a447aa60ad837

But this doesn't work.

I've checked both event viewer both web server and SQL server, but I can't see any information that tell me what had happened.

I also look at BOL, but doesn't help much.

Is there anyone can help me or point me to the right direction? Is there any guide document that explains step-by-step how to install SSRS in my scenario or similiar?

Many Thanks,

Usman Tjiudri

I have the exact same issue in a identical envirnonment configuration. Did you get this resolved?

I`m looking at a few articles re Kerberos....

|||Hi,

Yes, finally I got this issue resolved.
After looking for answer almost everywhere, I finally turn to Microsoft Support and they gave me a very quick response (less than 24 hours).
Before I talk about the solution, I need to clarify something here - my environment is Win2003 Server R2 (not Win2003 SP1 as mentioned in previous email) - may be there's a SP1 for R2.
The issue is caused by IIS. Apparently R2 has different version of IIS with normal Win2003 Server.
You need to uninstall completely IIS on your server (may be you need to backup IIS metadata) and install IIS for R2. You can get the software from R2 disc.
If you still can't solve the issue, log it to Microsoft Support.

Let me know how it goes.

Hope This Help,
Usman Tjiudri