Multiple instances of MSDE on same server?

can I install 2 separate apps from 2 separate vendors on the same machine,
if they both use MSDE? If so, is it simply installing a separate instance
for the 2nd install? Thanks.
Greg.
r3gbrewer@.health.nb.ca
Yes, that's usually what happens. Though different vendors do it
differently. Some will detect existing instances and ask if you want to use
one of them. I also remember seeing apps that just picked an arbitrary
existing instance if it found one.
http://www.aspfaq.com/
(Reverse address to reply.)
"Greg Brewer" <r3gbrewer@.xspamhealth.nb.ca> wrote in message
news:u5kQehx1EHA.3120@.TK2MSFTNGP12.phx.gbl...
> can I install 2 separate apps from 2 separate vendors on the same machine,
> if they both use MSDE? If so, is it simply installing a separate instance
> for the 2nd install? Thanks.
> Greg.
> r3gbrewer@.health.nb.ca
>
sql

Multiple Instances - Properties tuning

Hope you don't mind another few questions about tuning this multiple
instances server.
When installing 2 separate instances on MS SQL server 2000 Sp3a, would
I best leave the configurationof server Memory to SQL server
(dynamically), or should I allocate manually say 300 MB for each
instance (Total MB RAM = 1 GB). The applications will not be heavily
used.
If I were to audit, would I benefit from only auditing failure, or
would you yourself choose to audit All or None ? Do I audit only when
necessary or all the time ?
The BOL say that this file will grow max to 200 MB and that I should
specify immediately during setup a new directory for these audit
files. I can't see where I should enter this new directory.
Is this the SQL server error log ? BOL suggests making a directory
like MSSQL$instance\audit. That would be in the data directory right ?
Where do I register this directory in SQL server as the audit
directory? Do I need to use profiler to set auditing on and off ?
In the Remote Server connections, would you deny remote RPC
connections to your SQL server or not? Why ?
For your first question, checkout the page titled "Multiple Instance
Recommendations" in SQL Server 2000 Books Online.
Regarding auting, I generally look for failures, in the SQL Errorlog.
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Citizen" <citizen_NOSPAM@.hotmail.com> wrote in message
news:ogaie0tdj18cb194ubpp7vm971obqsva1j@.4ax.com...
Hope you don't mind another few questions about tuning this multiple
instances server.
When installing 2 separate instances on MS SQL server 2000 Sp3a, would
I best leave the configurationof server Memory to SQL server
(dynamically), or should I allocate manually say 300 MB for each
instance (Total MB RAM = 1 GB). The applications will not be heavily
used.
If I were to audit, would I benefit from only auditing failure, or
would you yourself choose to audit All or None ? Do I audit only when
necessary or all the time ?
The BOL say that this file will grow max to 200 MB and that I should
specify immediately during setup a new directory for these audit
files. I can't see where I should enter this new directory.
Is this the SQL server error log ? BOL suggests making a directory
like MSSQL$instance\audit. That would be in the data directory right ?
Where do I register this directory in SQL server as the audit
directory? Do I need to use profiler to set auditing on and off ?
In the Remote Server connections, would you deny remote RPC
connections to your SQL server or not? Why ?
|||Hi,
Why do you want to install mutiple instances of SQL Server since you have
only 1 GB of physical
memory in machine.
Better option will be create 2 databases and allocate 1 db for each
application.
If you need to install multiple instances of SQL Server always it is
recommended to fix the
memory usage for each instance of SQL Server. If you do not have any other
application other than
SQL Server in your machine then you can go for even 400 MB for each
instamce. THis memory parameter
should be changed based on usage of each instance. You can use Performance
monitor to identify the usage.
If I were to audit, would I benefit from only auditing failure, or
would you yourself choose to audit All or None ? Do I audit only when
necessary or all the time ?
I recommend you to audit only the failure, Otherwise you need to enable the
c2 Audit mode
which will audit all the activity. SO it uses more resources. During the
requirement stages
you can use Profiler to trace the activity.
Do I need to use profiler to set auditing on and off ?
No need, From Query Analyser execute
sp_configure 'c2 audit mode',1
To diable to audit
sp_configure 'c2 audit mode',0
(restart SQL Server service)
I can't see where I should enter this new directory.Is this the SQL server
error log ?
As far as i know,You have to change the default data directory
Thanks
Hari
MCDBA
"Citizen" <citizen_NOSPAM@.hotmail.com> wrote in message
news:ogaie0tdj18cb194ubpp7vm971obqsva1j@.4ax.com...
> Hope you don't mind another few questions about tuning this multiple
> instances server.
> When installing 2 separate instances on MS SQL server 2000 Sp3a, would
> I best leave the configurationof server Memory to SQL server
> (dynamically), or should I allocate manually say 300 MB for each
> instance (Total MB RAM = 1 GB). The applications will not be heavily
> used.
> If I were to audit, would I benefit from only auditing failure, or
> would you yourself choose to audit All or None ? Do I audit only when
> necessary or all the time ?
> The BOL say that this file will grow max to 200 MB and that I should
> specify immediately during setup a new directory for these audit
> files. I can't see where I should enter this new directory.
> Is this the SQL server error log ? BOL suggests making a directory
> like MSSQL$instance\audit. That would be in the data directory right ?
> Where do I register this directory in SQL server as the audit
> directory? Do I need to use profiler to set auditing on and off ?
> In the Remote Server connections, would you deny remote RPC
> connections to your SQL server or not? Why ?
>
|||Hi,
Why do you want to install mutiple instances of SQL Server since you have only 1 GB of physical
memory in machine.
Better option will be create 2 databases and allocate 1 db for each application.
If you need to install multiple instances of SQL Server always it is recommended to fix the
memory usage for each instance of SQL Server. If you do not have any other application other than
SQL Server in your machine then you can go for even 400 MB for each instamce. THis memory parameter
should be changed based on usage of each instance. You can use Performance monitor to identify the usage.
If I were to audit, would I benefit from only auditing failure, or
would you yourself choose to audit All or None ? Do I audit only when
necessary or all the time ?
I recommend you to audit only the failure, Otherwise you need to enable the c2 Audit mode
which will audit all the activity. SO it uses more resources. During the requirement stages
you can use Profiler to trace the activity.
Do I need to use profiler to set auditing on and off ?
No need, From Query Analyser execute
sp_configure 'c2 audit mode',1
To diable to audit
sp_configure 'c2 audit mode',0
(restart SQL Server service)
I can't see where I should enter this new directory.Is this the SQL server error log ?
As far as i know,You have to change the default data directory
Thanks
Hari
MCDBA
"Citizen" wrote:

> Hope you don't mind another few questions about tuning this multiple
> instances server.
> When installing 2 separate instances on MS SQL server 2000 Sp3a, would
> I best leave the configurationof server Memory to SQL server
> (dynamically), or should I allocate manually say 300 MB for each
> instance (Total MB RAM = 1 GB). The applications will not be heavily
> used.
> If I were to audit, would I benefit from only auditing failure, or
> would you yourself choose to audit All or None ? Do I audit only when
> necessary or all the time ?
> The BOL say that this file will grow max to 200 MB and that I should
> specify immediately during setup a new directory for these audit
> files. I can't see where I should enter this new directory.
> Is this the SQL server error log ? BOL suggests making a directory
> like MSSQL$instance\audit. That would be in the data directory right ?
> Where do I register this directory in SQL server as the audit
> directory? Do I need to use profiler to set auditing on and off ?
> In the Remote Server connections, would you deny remote RPC
> connections to your SQL server or not? Why ?
>
>
|||On Mon, 5 Jul 2004 12:03:07 +0100, "Narayana Vyas Kondreddi"
<answer_me@.hotmail.com> wrote:

>For your first question, checkout the page titled "Multiple Instance
>Recommendations" in SQL Server 2000 Books Online.
>Regarding auting, I generally look for failures, in the SQL Errorlog.
Thanks,
Just one little question : In the database settings tab from the SQL
Server Properties, you can see New databases location.
Do they mean transaction log or error log or audit log when they ask
the default log directory ? I think transaction log (LDF), is that
correct ?
|||You see two text boxes there, one for database and the other for transaction
log files.
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Citizen" <citizen_NOSPAM@.hotmail.com> wrote in message
news:emlie0dba1fo913c3d1m0rrhifj12frvlv@.4ax.com...
On Mon, 5 Jul 2004 12:03:07 +0100, "Narayana Vyas Kondreddi"
<answer_me@.hotmail.com> wrote:

>For your first question, checkout the page titled "Multiple Instance
>Recommendations" in SQL Server 2000 Books Online.
>Regarding auting, I generally look for failures, in the SQL Errorlog.
Thanks,
Just one little question : In the database settings tab from the SQL
Server Properties, you can see New databases location.
Do they mean transaction log or error log or audit log when they ask
the default log directory ? I think transaction log (LDF), is that
correct ?
|||On Mon, 5 Jul 2004 14:37:13 +0100, "Narayana Vyas Kondreddi"
<answer_me@.hotmail.com> wrote:

>You see two text boxes there, one for database and the other for transaction
>log files.
thanks a million
sql

Multiple Instances - Properties tuning

Hope you don't mind another few questions about tuning this multiple
instances server.
When installing 2 separate instances on MS SQL server 2000 Sp3a, would
I best leave the configurationof server Memory to SQL server
(dynamically), or should I allocate manually say 300 MB for each
instance (Total MB RAM = 1 GB). The applications will not be heavily
used.
If I were to audit, would I benefit from only auditing failure, or
would you yourself choose to audit All or None ? Do I audit only when
necessary or all the time ?
The BOL say that this file will grow max to 200 MB and that I should
specify immediately during setup a new directory for these audit
files. I can't see where I should enter this new directory.
Is this the SQL server error log ? BOL suggests making a directory
like MSSQL$instance\audit. That would be in the data directory right ?
Where do I register this directory in SQL server as the audit
directory? Do I need to use profiler to set auditing on and off ?
In the Remote Server connections, would you deny remote RPC
connections to your SQL server or not? Why ?For your first question, checkout the page titled "Multiple Instance
Recommendations" in SQL Server 2000 Books Online.
Regarding auting, I generally look for failures, in the SQL Errorlog.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Citizen" <citizen_NOSPAM@.hotmail.com> wrote in message
news:ogaie0tdj18cb194ubpp7vm971obqsva1j@.
4ax.com...
Hope you don't mind another few questions about tuning this multiple
instances server.
When installing 2 separate instances on MS SQL server 2000 Sp3a, would
I best leave the configurationof server Memory to SQL server
(dynamically), or should I allocate manually say 300 MB for each
instance (Total MB RAM = 1 GB). The applications will not be heavily
used.
If I were to audit, would I benefit from only auditing failure, or
would you yourself choose to audit All or None ? Do I audit only when
necessary or all the time ?
The BOL say that this file will grow max to 200 MB and that I should
specify immediately during setup a new directory for these audit
files. I can't see where I should enter this new directory.
Is this the SQL server error log ? BOL suggests making a directory
like MSSQL$instance\audit. That would be in the data directory right ?
Where do I register this directory in SQL server as the audit
directory? Do I need to use profiler to set auditing on and off ?
In the Remote Server connections, would you deny remote RPC
connections to your SQL server or not? Why ?|||Hi,
Why do you want to install mutiple instances of SQL Server since you have
only 1 GB of physical
memory in machine.
Better option will be create 2 databases and allocate 1 db for each
application.
If you need to install multiple instances of SQL Server always it is
recommended to fix the
memory usage for each instance of SQL Server. If you do not have any other
application other than
SQL Server in your machine then you can go for even 400 MB for each
instamce. THis memory parameter
should be changed based on usage of each instance. You can use Performance
monitor to identify the usage.
If I were to audit, would I benefit from only auditing failure, or
would you yourself choose to audit All or None ? Do I audit only when
necessary or all the time ?
I recommend you to audit only the failure, Otherwise you need to enable the
c2 Audit mode
which will audit all the activity. SO it uses more resources. During the
requirement stages
you can use Profiler to trace the activity.
Do I need to use profiler to set auditing on and off ?
No need, From Query Analyser execute
sp_configure 'c2 audit mode',1
To diable to audit
sp_configure 'c2 audit mode',0
(restart SQL Server service)
I can't see where I should enter this new directory.Is this the SQL server
error log ?
As far as i know,You have to change the default data directory
Thanks
Hari
MCDBA
"Citizen" <citizen_NOSPAM@.hotmail.com> wrote in message
news:ogaie0tdj18cb194ubpp7vm971obqsva1j@.
4ax.com...
> Hope you don't mind another few questions about tuning this multiple
> instances server.
> When installing 2 separate instances on MS SQL server 2000 Sp3a, would
> I best leave the configurationof server Memory to SQL server
> (dynamically), or should I allocate manually say 300 MB for each
> instance (Total MB RAM = 1 GB). The applications will not be heavily
> used.
> If I were to audit, would I benefit from only auditing failure, or
> would you yourself choose to audit All or None ? Do I audit only when
> necessary or all the time ?
> The BOL say that this file will grow max to 200 MB and that I should
> specify immediately during setup a new directory for these audit
> files. I can't see where I should enter this new directory.
> Is this the SQL server error log ? BOL suggests making a directory
> like MSSQL$instance\audit. That would be in the data directory right ?
> Where do I register this directory in SQL server as the audit
> directory? Do I need to use profiler to set auditing on and off ?
> In the Remote Server connections, would you deny remote RPC
> connections to your SQL server or not? Why ?
>|||Hi,
Why do you want to install mutiple instances of SQL Server since you have on
ly 1 GB of physical
memory in machine.
Better option will be create 2 databases and allocate 1 db for each applicat
ion.
If you need to install multiple instances of SQL Server always it is recomme
nded to fix the
memory usage for each instance of SQL Server. If you do not have any other a
pplication other than
SQL Server in your machine then you can go for even 400 MB for each instamce
. THis memory parameter
should be changed based on usage of each instance. You can use Performance m
onitor to identify the usage.
If I were to audit, would I benefit from only auditing failure, or
would you yourself choose to audit All or None ? Do I audit only when
necessary or all the time ?
I recommend you to audit only the failure, Otherwise you need to enable the
c2 Audit mode
which will audit all the activity. SO it uses more resources. During the req
uirement stages
you can use Profiler to trace the activity.
Do I need to use profiler to set auditing on and off ?
No need, From Query Analyser execute
sp_configure 'c2 audit mode',1
To diable to audit
sp_configure 'c2 audit mode',0
(restart SQL Server service)
I can't see where I should enter this new directory.Is this the SQL server e
rror log ?
As far as i know,You have to change the default data directory
Thanks
Hari
MCDBA
"Citizen" wrote:

> Hope you don't mind another few questions about tuning this multiple
> instances server.
> When installing 2 separate instances on MS SQL server 2000 Sp3a, would
> I best leave the configurationof server Memory to SQL server
> (dynamically), or should I allocate manually say 300 MB for each
> instance (Total MB RAM = 1 GB). The applications will not be heavily
> used.
> If I were to audit, would I benefit from only auditing failure, or
> would you yourself choose to audit All or None ? Do I audit only when
> necessary or all the time ?
> The BOL say that this file will grow max to 200 MB and that I should
> specify immediately during setup a new directory for these audit
> files. I can't see where I should enter this new directory.
> Is this the SQL server error log ? BOL suggests making a directory
> like MSSQL$instance\audit. That would be in the data directory right ?
> Where do I register this directory in SQL server as the audit
> directory? Do I need to use profiler to set auditing on and off ?
> In the Remote Server connections, would you deny remote RPC
> connections to your SQL server or not? Why ?
>
>|||On Mon, 5 Jul 2004 12:03:07 +0100, "Narayana Vyas Kondreddi"
<answer_me@.hotmail.com> wrote:

>For your first question, checkout the page titled "Multiple Instance
>Recommendations" in SQL Server 2000 Books Online.
>Regarding auting, I generally look for failures, in the SQL Errorlog.
Thanks,
Just one little question : In the database settings tab from the SQL
Server Properties, you can see New databases location.
Do they mean transaction log or error log or audit log when they ask
the default log directory ? I think transaction log (LDF), is that
correct ?|||You see two text boxes there, one for database and the other for transaction
log files.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Citizen" <citizen_NOSPAM@.hotmail.com> wrote in message
news:emlie0dba1fo913c3d1m0rrhifj12frvlv@.
4ax.com...
On Mon, 5 Jul 2004 12:03:07 +0100, "Narayana Vyas Kondreddi"
<answer_me@.hotmail.com> wrote:

>For your first question, checkout the page titled "Multiple Instance
>Recommendations" in SQL Server 2000 Books Online.
>Regarding auting, I generally look for failures, in the SQL Errorlog.
Thanks,
Just one little question : In the database settings tab from the SQL
Server Properties, you can see New databases location.
Do they mean transaction log or error log or audit log when they ask
the default log directory ? I think transaction log (LDF), is that
correct ?|||On Mon, 5 Jul 2004 14:37:13 +0100, "Narayana Vyas Kondreddi"
<answer_me@.hotmail.com> wrote:

>You see two text boxes there, one for database and the other for transactio
n
>log files.
thanks a million

Multiple Instances - Properties tuning

Hope you don't mind another few questions about tuning this multiple
instances server.
When installing 2 separate instances on MS SQL server 2000 Sp3a, would
I best leave the configurationof server Memory to SQL server
(dynamically), or should I allocate manually say 300 MB for each
instance (Total MB RAM = 1 GB). The applications will not be heavily
used.
If I were to audit, would I benefit from only auditing failure, or
would you yourself choose to audit All or None ? Do I audit only when
necessary or all the time ?
The BOL say that this file will grow max to 200 MB and that I should
specify immediately during setup a new directory for these audit
files. I can't see where I should enter this new directory.
Is this the SQL server error log ? BOL suggests making a directory
like MSSQL$instance\audit. That would be in the data directory right ?
Where do I register this directory in SQL server as the audit
directory? Do I need to use profiler to set auditing on and off ?
In the Remote Server connections, would you deny remote RPC
connections to your SQL server or not? Why ?For your first question, checkout the page titled "Multiple Instance
Recommendations" in SQL Server 2000 Books Online.
Regarding auting, I generally look for failures, in the SQL Errorlog.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Citizen" <citizen_NOSPAM@.hotmail.com> wrote in message
news:ogaie0tdj18cb194ubpp7vm971obqsva1j@.4ax.com...
Hope you don't mind another few questions about tuning this multiple
instances server.
When installing 2 separate instances on MS SQL server 2000 Sp3a, would
I best leave the configurationof server Memory to SQL server
(dynamically), or should I allocate manually say 300 MB for each
instance (Total MB RAM = 1 GB). The applications will not be heavily
used.
If I were to audit, would I benefit from only auditing failure, or
would you yourself choose to audit All or None ? Do I audit only when
necessary or all the time ?
The BOL say that this file will grow max to 200 MB and that I should
specify immediately during setup a new directory for these audit
files. I can't see where I should enter this new directory.
Is this the SQL server error log ? BOL suggests making a directory
like MSSQL$instance\audit. That would be in the data directory right ?
Where do I register this directory in SQL server as the audit
directory? Do I need to use profiler to set auditing on and off ?
In the Remote Server connections, would you deny remote RPC
connections to your SQL server or not? Why ?|||Hi,
Why do you want to install mutiple instances of SQL Server since you have
only 1 GB of physical
memory in machine.
Better option will be create 2 databases and allocate 1 db for each
application.
If you need to install multiple instances of SQL Server always it is
recommended to fix the
memory usage for each instance of SQL Server. If you do not have any other
application other than
SQL Server in your machine then you can go for even 400 MB for each
instamce. THis memory parameter
should be changed based on usage of each instance. You can use Performance
monitor to identify the usage.
If I were to audit, would I benefit from only auditing failure, or
would you yourself choose to audit All or None ? Do I audit only when
necessary or all the time ?
I recommend you to audit only the failure, Otherwise you need to enable the
c2 Audit mode
which will audit all the activity. SO it uses more resources. During the
requirement stages
you can use Profiler to trace the activity.
Do I need to use profiler to set auditing on and off ?
No need, From Query Analyser execute
sp_configure 'c2 audit mode',1
To diable to audit
sp_configure 'c2 audit mode',0
(restart SQL Server service)
I can't see where I should enter this new directory.Is this the SQL server
error log ?
As far as i know,You have to change the default data directory
--
Thanks
Hari
MCDBA
"Citizen" <citizen_NOSPAM@.hotmail.com> wrote in message
news:ogaie0tdj18cb194ubpp7vm971obqsva1j@.4ax.com...
> Hope you don't mind another few questions about tuning this multiple
> instances server.
> When installing 2 separate instances on MS SQL server 2000 Sp3a, would
> I best leave the configurationof server Memory to SQL server
> (dynamically), or should I allocate manually say 300 MB for each
> instance (Total MB RAM = 1 GB). The applications will not be heavily
> used.
> If I were to audit, would I benefit from only auditing failure, or
> would you yourself choose to audit All or None ? Do I audit only when
> necessary or all the time ?
> The BOL say that this file will grow max to 200 MB and that I should
> specify immediately during setup a new directory for these audit
> files. I can't see where I should enter this new directory.
> Is this the SQL server error log ? BOL suggests making a directory
> like MSSQL$instance\audit. That would be in the data directory right ?
> Where do I register this directory in SQL server as the audit
> directory? Do I need to use profiler to set auditing on and off ?
> In the Remote Server connections, would you deny remote RPC
> connections to your SQL server or not? Why ?
>|||Hi,
Why do you want to install mutiple instances of SQL Server since you have only 1 GB of physical
memory in machine.
Better option will be create 2 databases and allocate 1 db for each application.
If you need to install multiple instances of SQL Server always it is recommended to fix the
memory usage for each instance of SQL Server. If you do not have any other application other than
SQL Server in your machine then you can go for even 400 MB for each instamce. THis memory parameter
should be changed based on usage of each instance. You can use Performance monitor to identify the usage.
If I were to audit, would I benefit from only auditing failure, or
would you yourself choose to audit All or None ? Do I audit only when
necessary or all the time ?
I recommend you to audit only the failure, Otherwise you need to enable the c2 Audit mode
which will audit all the activity. SO it uses more resources. During the requirement stages
you can use Profiler to trace the activity.
Do I need to use profiler to set auditing on and off ?
No need, From Query Analyser execute
sp_configure 'c2 audit mode',1
To diable to audit
sp_configure 'c2 audit mode',0
(restart SQL Server service)
I can't see where I should enter this new directory.Is this the SQL server error log ?
As far as i know,You have to change the default data directory
Thanks
Hari
MCDBA
"Citizen" wrote:
> Hope you don't mind another few questions about tuning this multiple
> instances server.
> When installing 2 separate instances on MS SQL server 2000 Sp3a, would
> I best leave the configurationof server Memory to SQL server
> (dynamically), or should I allocate manually say 300 MB for each
> instance (Total MB RAM = 1 GB). The applications will not be heavily
> used.
> If I were to audit, would I benefit from only auditing failure, or
> would you yourself choose to audit All or None ? Do I audit only when
> necessary or all the time ?
> The BOL say that this file will grow max to 200 MB and that I should
> specify immediately during setup a new directory for these audit
> files. I can't see where I should enter this new directory.
> Is this the SQL server error log ? BOL suggests making a directory
> like MSSQL$instance\audit. That would be in the data directory right ?
> Where do I register this directory in SQL server as the audit
> directory? Do I need to use profiler to set auditing on and off ?
> In the Remote Server connections, would you deny remote RPC
> connections to your SQL server or not? Why ?
>
>|||On Mon, 5 Jul 2004 12:03:07 +0100, "Narayana Vyas Kondreddi"
<answer_me@.hotmail.com> wrote:
>For your first question, checkout the page titled "Multiple Instance
>Recommendations" in SQL Server 2000 Books Online.
>Regarding auting, I generally look for failures, in the SQL Errorlog.
Thanks,
Just one little question : In the database settings tab from the SQL
Server Properties, you can see New databases location.
Do they mean transaction log or error log or audit log when they ask
the default log directory ? I think transaction log (LDF), is that
correct ?|||You see two text boxes there, one for database and the other for transaction
log files.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Citizen" <citizen_NOSPAM@.hotmail.com> wrote in message
news:emlie0dba1fo913c3d1m0rrhifj12frvlv@.4ax.com...
On Mon, 5 Jul 2004 12:03:07 +0100, "Narayana Vyas Kondreddi"
<answer_me@.hotmail.com> wrote:
>For your first question, checkout the page titled "Multiple Instance
>Recommendations" in SQL Server 2000 Books Online.
>Regarding auting, I generally look for failures, in the SQL Errorlog.
Thanks,
Just one little question : In the database settings tab from the SQL
Server Properties, you can see New databases location.
Do they mean transaction log or error log or audit log when they ask
the default log directory ? I think transaction log (LDF), is that
correct ?|||On Mon, 5 Jul 2004 14:37:13 +0100, "Narayana Vyas Kondreddi"
<answer_me@.hotmail.com> wrote:
>You see two text boxes there, one for database and the other for transaction
>log files.
thanks a million :)

Multiple installations of SqlServer on same server.

Hi all,
Can anyone advise on installing multiple versions of
SqlServer 2000 (ver 8) on the same server whilst
maintaining the integrity of previous installations of
SqlServer ?
Thanks in advance.
jTHere are no integrity issues involving multiple instances on the same box,
one instance is independent of the other, with one exception... - they both
will compete for memory. So unless you will be running only one at a time, I
would advise you to set max memory for each instance, assigning the
appropriate memory, so the instances do not compete in this regard...
"jimA" <jima@.pt.lu> wrote in message
news:075a01c35cc1$b7c0df60$a601280a@.phx.gbl...
> Hi all,
> Can anyone advise on installing multiple versions of
> SqlServer 2000 (ver 8) on the same server whilst
> maintaining the integrity of previous installations of
> SqlServer ?
> Thanks in advance.
> j|||You can install multiple instance of SQL 2000 on the same server. Each
is independent and can be at different service pack levels. Only the
tools are shared.
It's generally best to deploy a single instance unless you have a
specific reason to do otherwise, such as special security isolation
requirements or independent test environments. See the Books Online
<architec.chm::/8_ar_cs_5upf.htm> for recommendations. Also note that
licensing restrictions vary by edition.
--
Hope this helps.
Dan Guzman
SQL Server MVP
--
SQL FAQ links (courtesy Neil Pike):
http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
--
"jimA" <jima@.pt.lu> wrote in message
news:075a01c35cc1$b7c0df60$a601280a@.phx.gbl...
> Hi all,
> Can anyone advise on installing multiple versions of
> SqlServer 2000 (ver 8) on the same server whilst
> maintaining the integrity of previous installations of
> SqlServer ?
> Thanks in advance.
> j|||Guys,
Many thanks, your comments were much appreciated.
j
>--Original Message--
>Hi all,
>Can anyone advise on installing multiple versions of
>SqlServer 2000 (ver 8) on the same server whilst
>maintaining the integrity of previous installations of
>SqlServer ?
>Thanks in advance.
>j
>.
>

Multiple Apps on Single SQL Server?

Question for the SQL experts.
We are installing new 2 - BL20p 3.6Xeon 1 - BL40p 3.0Xeon servers and
I wanted to know others opinions as to how to configure the SQL
databases.
Here are the applications that we will be loading. Sharepoint Portal
(125 users), Project Server (50 users) and SQL 2000.
The usage on these apps will not be heavy so can I consolidate all
databases to 1 server without any negative performance? Or should I
install SQL on BL40p and Sharepoint Portal and Project on another
server?
I am fairly new at SQL and I wanted to try and consolidate if possible.
Will a single instance be fine for all 3 apps?
Your thoughts?? I got confused by your question.
Yes, you can consolidate all databases (at least those you mentioned)
to one MSSQL backend (whether you like to set it as one instance or
multiple instances).
No, it is better to have a dedicated server as a sorely Database Server
(MSSQL in this case), which separate from the application server(s).
It will be better to have Portal and Project install on its own server
as a application server but the databases stores in a separate
dedicated MSSQL Server.
Hope it helps.
Mel