'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

Installing/Deploying Windows App with SQL Server 2005 CE

I am a little bit confused about making an installer/deployer.

I have an application using SQL Server 2005 CE (I have just updated to the most recent version Jan 2007). It will run on a new desktop PC (windows XP) if I install the SQL CE runtime and then copy the .EXE and the .SDF database file. This is great but my client wants the whole thing to install as one operation. I thought click once could do this but it seems that is only for Pocket PC targets? Can anyone point me to a method to make an appropriate installer please?

Pete

I am using the following:
SQLServerCE31-EN.msi - installer for SQL CE server runtime
SSCE31VSTools-ENU.exe - installed over VS 2005 SP1.Have you tried publishing it? - I have no problem doing this for standard apps.

In Brian Noyes' book "Smart Client Deployment with ClickOnce' there are several small sections on how to deploy CE

P235 "An example is the SQL Server 2005 CE CTP that is available at the time of this writing. You can download the .msi file to do and install of SQL Compact and you can also download the Bootstrapper Manifest needed to add SQL Compact to your Bootstrapper. If you are provided the Bootstrapper files, all you need to do is place the files in the right location."

I can recommend this book - written in a logical straightforward manner. Also covered is Deploying a (sic CE) Client Database with your Application (starting P 167)

Here is the video link from Steve Lasker's blog on CE deployment http://blogs.msdn.com/stevelasker/archive/2006/07/06/SQLServerEverywhereDeploymentOptions.aspx|||If you use something like Inno Setup you can just have the installer copy the SQL Server Compact Edition dll files to the application's folder. Then you won't have to worry about using the MSI file. Check the SQL Server Compact Edition Books Online for more.

Or, (still using Inno Setup) add the MSI file to the setup project and run it with the necessary options to install it right before the installation ends.
|||Great responses guys! I'll try everything you suggest and feed back here.

Pete|||Ok, thanks for the references to Steve Laskers blog. The screencast of deployment options gave me the information I needed. I have ended up using the VS Setup project to install the SQL CE dlls into the app folder and the GAC. That is great for me (I didn't want publish/deploy). I am sure Inno would have done the same but I don't have time to learn another setup app now (I've used NCIS as well in the past). Anyway, kudos to all of you and Steve Lasker and the MS Virtual PC people without which I would need 2 PCs to test all this...

Pete|||I should mention that it looks like just copying SQL Server Compact Edition's DLLs is not a way to do it anymore. I remember seeing it in the SQL Server Everywhere Edition Books Online but it seems to have been removed from the SQL Server Compact Edition Books Online. Just thought I shouldd mention this for anyone else who reads this thread.

Installing sqlxml for a .NET app

Hi,
I have created a .NET client application that uses the managed SQLXML
components. I now need to create a installer for my app. I wnat to a void
having to run sqlxml.msi separatly. Is there an easy way to avoid this?
Is there a merge module I can use? if not what files ect. do I need to
include?
Thanks
Steven EvansWe only package SqlXml in msi's and there are no seperatate mergeable
installers.
"Steven Evans" <Steven Evans@.discussions.microsoft.com> wrote in message
news:348E0FD8-3158-4AD8-A577-EF7F4E872D06@.microsoft.com...
> Hi,
> I have created a .NET client application that uses the managed SQLXML
> components. I now need to create a installer for my app. I wnat to a
> void
> having to run sqlxml.msi separatly. Is there an easy way to avoid this?
> Is there a merge module I can use? if not what files ect. do I need to
> include?
> Thanks
> Steven Evans

Installing sqlxml for a .NET app

Hi,
I have created a .NET client application that uses the managed SQLXML
components. I now need to create a installer for my app. I wnat to a void
having to run sqlxml.msi separatly. Is there an easy way to avoid this?
Is there a merge module I can use? if not what files ect. do I need to
include?
Thanks
Steven Evans
We only package SqlXml in msi's and there are no seperatate mergeable
installers.
"Steven Evans" <Steven Evans@.discussions.microsoft.com> wrote in message
news:348E0FD8-3158-4AD8-A577-EF7F4E872D06@.microsoft.com...
> Hi,
> I have created a .NET client application that uses the managed SQLXML
> components. I now need to create a installer for my app. I wnat to a
> void
> having to run sqlxml.msi separatly. Is there an easy way to avoid this?
> Is there a merge module I can use? if not what files ect. do I need to
> include?
> Thanks
> Steven Evans
sql

Integrated Security in a Forms asp.net App

Hi
We have a problem which I can see has been encountered by others in the past.
However, even after reading many threads on this subject it is not entirely
clear what thesolution is. I would like advice on how best to proceed.
We have an asp.net application which uses Forms authentication. Some pages
have frames which contain RS reports. The reports are called by URL. It
works great except for the security...
The application is to be used by several hundred users from outside our
organisation. The reports used within the application will also be accessed
by users on our own domain via report manager.
We have SQL Server 2000 standard edition.
I have read that I cannot configure for forms authentication because we do
not have SQL Enterprise edition. It seems that this would mess up our
authentication for internal users anyway. If I configure Report Server for
anonymous access I lose control over who sees what within our company & the
world at large can get at the reports if they figure out the URL.
What are my options for a workable integrated security solution?
Thanks
WayneWe recently had the same type of requirements. We did have to move to
Enterprise and additionally, we had to create a custom security
extension (similiar to a custom reporting extension) to handle our
special needs. Microsoft may have some examples of doing this.
This was the only solution we found.
Ken Foust|||Thanks for the reply Ken.
I've seen some examples of custom extensions, I was hoping I could avoid it
as it looks difficult & time consuming to set up. I may have to avoid it
anyway as I'm not convinced I will get approval for an upgrade to Enterprise
edition. If you are using forms authentication now, how has this affected
usage of internal reports? I've seen someone tout the idea of having
separate Forms & Windows security Report Servers, did you try this perhaps?
What a shame that RS does not cater for this common scenario straight out of
the box.
Thanks
Wayne
ken_foust@.hotmail.com wrote:
>We recently had the same type of requirements. We did have to move to
>Enterprise and additionally, we had to create a custom security
>extension (similiar to a custom reporting extension) to handle our
>special needs. Microsoft may have some examples of doing this.
>This was the only solution we found.
>Ken Foust
--
Message posted via http://www.sqlmonster.com

Integrate my app

I wish sqlserver can send me a mail automatically after completing one job,there are alerts and notifications in job properties,which can perform my need? Previously,i defined database mail,but failed

who can tell me which is appropriate way?

TIA

I saw your different threads in the groups, did you manage to setup database mail, this should be the first point where we should start.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Installing Sql Mobile via CAB file

Hi guys,

wonder if someone can help? I have written an app the runs on PocketPC 2003 and uses CF 2 and Sql Mobile 2005. I need to be able to install my application and Sql Mobile from within a desktop app. This is what I am doing, but I have a few questions:

Using RAPI I copy over to the device; myApp.CAB and sqlce30.ppc.wce4.armv4.CAB.
Using RAPI I then run wceload on these two CAB files.

This works a treat, both application install properly and work!!

But, in the same directory as the sqlce30.ppc.wce4.armv4.CAB (in C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SQL Server\Mobile\v3.0\wce400\armv4) there are two other CAB files:

sqlce30.dev.ENU.ppc.wce4.armv4.CAB
sqlce30.repl.ppc.wce4.armv4.CAB

My application doesn't use replication so I didn't copy over the second file. But what is the first one, and do I need it installed on the device?

Thanks for your help
Graham

Hi

I installed

sqlce30.dev.ENU.ppc.wce4.armv4.CAB

from C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SQL Server\Mobile\v3.0\wce400\armv4

and

sql.dev.ENU.ppc.wce4.armv4.CAB

from C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SQL Server\Client\v2.0\wce400\armv4

and

Installing Sql Mobile via CAB file

Hi guys,

wonder if someone can help? I have written an app the runs on PocketPC 2003 and uses CF 2 and Sql Mobile 2005. I need to be able to install my application and Sql Mobile from within a desktop app. This is what I am doing, but I have a few questions:

Using RAPI I copy over to the device; myApp.CAB and sqlce30.ppc.wce4.armv4.CAB.
Using RAPI I then run wceload on these two CAB files.

This works a treat, both application install properly and work!!

But, in the same directory as the sqlce30.ppc.wce4.armv4.CAB (in C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SQL Server\Mobile\v3.0\wce400\armv4) there are two other CAB files:

sqlce30.dev.ENU.ppc.wce4.armv4.CAB
sqlce30.repl.ppc.wce4.armv4.CAB

My application doesn't use replication so I didn't copy over the second file. But what is the first one, and do I need it installed on the device?

Thanks for your help
Graham

Hi

I installed

sqlce30.dev.ENU.ppc.wce4.armv4.CAB

from C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SQL Server\Mobile\v3.0\wce400\armv4

and

sql.dev.ENU.ppc.wce4.armv4.CAB

from C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\SQL Server\Client\v2.0\wce400\armv4

and