How to configure SQL server to use multiple processor

hi,
We have a system with two processors. What settings should we do in sql
server 2000 standard edition to use both the processors. Can anyone suggest?
Thanks
PremHello,
By itself SQL Server will use both processors. There is no change required.
Thanks
Hari
"Prem" <Prem_a20@.hotmail.com> wrote in message
news:uoDh1q8SHHA.4956@.TK2MSFTNGP04.phx.gbl...
> hi,
> We have a system with two processors. What settings should we do in sql
> server 2000 standard edition to use both the processors. Can anyone
> suggest?
> Thanks
> Prem
>
>|||underprocessable

How to configure SQL server to use multiple processor

hi,
We have a system with two processors. What settings should we do in sql
server 2000 standard edition to use both the processors. Can anyone suggest?
Thanks
PremHello,
By itself SQL Server will use both processors. There is no change required.
Thanks
Hari
"Prem" <Prem_a20@.hotmail.com> wrote in message
news:uoDh1q8SHHA.4956@.TK2MSFTNGP04.phx.gbl...
> hi,
> We have a system with two processors. What settings should we do in sql
> server 2000 standard edition to use both the processors. Can anyone
> suggest?
> Thanks
> Prem
>
>

how to configure SQL Server 7.x memory

Hi,
I am curious what the steps are to follow to configure the
SQL server memory settings please?
How do you tell what the current setting is?
We have 500 MB of RAM and an additional 500 MB of RAM was
added. How do you give more memory to SQL server?
In previous posts that I have scanned for memory in here,
what is awe?
Thanks,
Cynthia
(only temporarily assisting to optimize the SQL Server, as
I am not a SQL Server DBA..any help is appreciated).Until you reach 4GB of physical RAM, PAE and AWE are unnecessary settings.
Normally, SQL will adjust itself to take all memory and leave 8-10MB free.
This is good if the server is dedicated to SQL. If other applications run
on SQL, you may want to limit how much memory SQL uses. That can be a trial
and error process since the memory consumption depends on the behavior of
other applications.
So, if it is a dedicated SQL server, leave it alone. Once the OS sees the
memory, SQL will take advantage of it.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Cynthia" <anonymous@.discussions.microsoft.com> wrote in message
news:940601c40525$32a37b00$a101280a@.phx.gbl...
> Hi,
> I am curious what the steps are to follow to configure the
> SQL server memory settings please?
> How do you tell what the current setting is?
> We have 500 MB of RAM and an additional 500 MB of RAM was
> added. How do you give more memory to SQL server?
> In previous posts that I have scanned for memory in here,
> what is awe?
> Thanks,
> Cynthia
> (only temporarily assisting to optimize the SQL Server, as
> I am not a SQL Server DBA..any help is appreciated).
>|||Geoff,
Thank you for the quick response. Does this mean you do
not have to run sp_configure "Memory" (similar command as
in sybase) to fix a set amt of memory if it is less than 4
gb in size?
Thanks
Cynthia
>--Original Message--
>Until you reach 4GB of physical RAM, PAE and AWE are
unnecessary settings.
>Normally, SQL will adjust itself to take all memory and
leave 8-10MB free.
>This is good if the server is dedicated to SQL. If other
applications run
>on SQL, you may want to limit how much memory SQL uses.
That can be a trial
>and error process since the memory consumption depends on
the behavior of
>other applications.
>So, if it is a dedicated SQL server, leave it alone.
Once the OS sees the
>memory, SQL will take advantage of it.
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>I support the Professional Association for SQL Server
>www.sqlpass.org
>"Cynthia" <anonymous@.discussions.microsoft.com> wrote in
message
>news:940601c40525$32a37b00$a101280a@.phx.gbl...
the
was
here,
as
>
>.
>|||Actually, there are commands to set min and max server memory. These are
for two circumstances, 1) there is more than 4GB of physical RAM in the box.
2) If you want/need to manage memory yourself. If neither apply and you
want SQL to take care of memory management, just leave it alone.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:8df701c40528$402761d0$a301280a@.phx.gbl...
> Geoff,
> Thank you for the quick response. Does this mean you do
> not have to run sp_configure "Memory" (similar command as
> in sybase) to fix a set amt of memory if it is less than 4
> gb in size?
> Thanks
> Cynthia
> unnecessary settings.
> leave 8-10MB free.
> applications run
> That can be a trial
> the behavior of
> Once the OS sees the
> message
> the
> was
> here,
> as

How to configure ports in SQL server configuration manager

Hi,
unfortunately I mixed up the ip settings in SQL server configuration manager
(I'm running SBS 2003 R1 with Backup Exec 11d and SQL 2005 Express). Now I
have an event in the application protocol (3), it says that configuration for
SQL instances "bkupexec" and "sqlexpress" are invalid.
I tried 100 different settings in SQL configuratin manager, but the events
are remaining. I cannot find out to configure this. Backup Exce for example
has nothing where I could configure a port address for communicating with its
SQL instance.
Can someone provide me with information about what to configure in SQL
Server Configuration Manager (and probably in Backup Exec - Symantec did not
answer until now) to avoid the error messages?
Thanx in advance,
Tim
Hi
"Tim Meltzer" wrote:

> Hi,
> unfortunately I mixed up the ip settings in SQL server configuration manager
> (I'm running SBS 2003 R1 with Backup Exec 11d and SQL 2005 Express). Now I
> have an event in the application protocol (3), it says that configuration for
> SQL instances "bkupexec" and "sqlexpress" are invalid.
> I tried 100 different settings in SQL configuratin manager, but the events
> are remaining. I cannot find out to configure this. Backup Exce for example
> has nothing where I could configure a port address for communicating with its
> SQL instance.
> Can someone provide me with information about what to configure in SQL
> Server Configuration Manager (and probably in Backup Exec - Symantec did not
> answer until now) to avoid the error messages?
> Thanx in advance,
> Tim
By default SQLExpress will not have remote connections enabled. If you are
using a database on the same server then you should not need to enabled
TCP/IP.
Have you checked these instances of SQL Server are running using the service
applet or typing NET START at a command prompt?
In the Network Protocols branch under SQL Server Configuration Manager, is
the protocol Enabled? If you double click the tcp/ip entry that you will get
the IP and port settings in the properties dialog.
John
|||Hi John,
thanks for input.

> In the Network Protocols branch under SQL Server Configuration Manager, is
> the protocol Enabled?
Which protocol? I tried them all, the error no. 3 remained.

> If you double click the tcp/ip entry that you will get
> the IP and port settings in the properties dialog.
Yes, but I don't no, wether these IP settings are the right ones for Backup
Exec, I don't know, what exactly it is what Windows is complaining about.
Finally I uninstalled BE and SQL Server and reinstalled it, but without
success.
You stated, that TCP is not needed if everything is running on one server.
So I think I'm going to ignore the message since everything seems to work.
Thanks again.
|||Hi Tim
"Tim Meltzer" wrote:

> Hi John,
> thanks for input.
>
> Which protocol? I tried them all, the error no. 3 remained.
>
> Yes, but I don't no, wether these IP settings are the right ones for Backup
> Exec, I don't know, what exactly it is what Windows is complaining about.
> Finally I uninstalled BE and SQL Server and reinstalled it, but without
> success.
> You stated, that TCP is not needed if everything is running on one server.
> So I think I'm going to ignore the message since everything seems to work.
> Thanks again.
It is not clear where exactly where the error message is being displayed! Is
this in Backup exec, SQL Server error log or the Windows Event log?
If after installing Backup Exec again what protocols are enabled?
John

How to configure ports in SQL server configuration manager

Hi,
unfortunately I mixed up the ip settings in SQL server configuration manager
(I'm running SBS 2003 R1 with Backup Exec 11d and SQL 2005 Express). Now I
have an event in the application protocol (3), it says that configuration fo
r
SQL instances "bkupexec" and "sqlexpress" are invalid.
I tried 100 different settings in SQL configuratin manager, but the events
are remaining. I cannot find out to configure this. Backup Exce for example
has nothing where I could configure a port address for communicating with it
s
SQL instance.
Can someone provide me with information about what to configure in SQL
Server Configuration Manager (and probably in Backup Exec - Symantec did not
answer until now) to avoid the error messages?
Thanx in advance,
TimHi
"Tim Meltzer" wrote:

> Hi,
> unfortunately I mixed up the ip settings in SQL server configuration manag
er
> (I'm running SBS 2003 R1 with Backup Exec 11d and SQL 2005 Express). Now I
> have an event in the application protocol (3), it says that configuration
for
> SQL instances "bkupexec" and "sqlexpress" are invalid.
> I tried 100 different settings in SQL configuratin manager, but the events
> are remaining. I cannot find out to configure this. Backup Exce for exampl
e
> has nothing where I could configure a port address for communicating with
its
> SQL instance.
> Can someone provide me with information about what to configure in SQL
> Server Configuration Manager (and probably in Backup Exec - Symantec did n
ot
> answer until now) to avoid the error messages?
> Thanx in advance,
> Tim
By default SQLExpress will not have remote connections enabled. If you are
using a database on the same server then you should not need to enabled
TCP/IP.
Have you checked these instances of SQL Server are running using the service
applet or typing NET START at a command prompt?
In the Network Protocols branch under SQL Server Configuration Manager, is
the protocol Enabled? If you double click the tcp/ip entry that you will get
the IP and port settings in the properties dialog.
John|||Hi John,
thanks for input.

> In the Network Protocols branch under SQL Server Configuration Manager, is
> the protocol Enabled?
Which protocol? I tried them all, the error no. 3 remained.

> If you double click the tcp/ip entry that you will get
> the IP and port settings in the properties dialog.
Yes, but I don't no, wether these IP settings are the right ones for Backup
Exec, I don't know, what exactly it is what Windows is complaining about.
Finally I uninstalled BE and SQL Server and reinstalled it, but without
success.
You stated, that TCP is not needed if everything is running on one server.
So I think I'm going to ignore the message since everything seems to work.
Thanks again.|||Hi Tim
"Tim Meltzer" wrote:

> Hi John,
> thanks for input.
>
> Which protocol? I tried them all, the error no. 3 remained.
>
> Yes, but I don't no, wether these IP settings are the right ones for Backu
p
> Exec, I don't know, what exactly it is what Windows is complaining about.
> Finally I uninstalled BE and SQL Server and reinstalled it, but without
> success.
> You stated, that TCP is not needed if everything is running on one server.
> So I think I'm going to ignore the message since everything seems to work.
> Thanks again.
It is not clear where exactly where the error message is being displayed! Is
this in Backup exec, SQL Server error log or the Windows Event log?
If after installing Backup Exec again what protocols are enabled?
John

How to configure ports in SQL server configuration manager

Hi,
unfortunately I mixed up the ip settings in SQL server configuration manager
(I'm running SBS 2003 R1 with Backup Exec 11d and SQL 2005 Express). Now I
have an event in the application protocol (3), it says that configuration for
SQL instances "bkupexec" and "sqlexpress" are invalid.
I tried 100 different settings in SQL configuratin manager, but the events
are remaining. I cannot find out to configure this. Backup Exce for example
has nothing where I could configure a port address for communicating with its
SQL instance.
Can someone provide me with information about what to configure in SQL
Server Configuration Manager (and probably in Backup Exec - Symantec did not
answer until now) to avoid the error messages?
Thanx in advance,
TimHi
"Tim Meltzer" wrote:
> Hi,
> unfortunately I mixed up the ip settings in SQL server configuration manager
> (I'm running SBS 2003 R1 with Backup Exec 11d and SQL 2005 Express). Now I
> have an event in the application protocol (3), it says that configuration for
> SQL instances "bkupexec" and "sqlexpress" are invalid.
> I tried 100 different settings in SQL configuratin manager, but the events
> are remaining. I cannot find out to configure this. Backup Exce for example
> has nothing where I could configure a port address for communicating with its
> SQL instance.
> Can someone provide me with information about what to configure in SQL
> Server Configuration Manager (and probably in Backup Exec - Symantec did not
> answer until now) to avoid the error messages?
> Thanx in advance,
> Tim
By default SQLExpress will not have remote connections enabled. If you are
using a database on the same server then you should not need to enabled
TCP/IP.
Have you checked these instances of SQL Server are running using the service
applet or typing NET START at a command prompt?
In the Network Protocols branch under SQL Server Configuration Manager, is
the protocol Enabled? If you double click the tcp/ip entry that you will get
the IP and port settings in the properties dialog.
John|||Hi John,
thanks for input.
> In the Network Protocols branch under SQL Server Configuration Manager, is
> the protocol Enabled?
Which protocol? I tried them all, the error no. 3 remained.
> If you double click the tcp/ip entry that you will get
> the IP and port settings in the properties dialog.
Yes, but I don't no, wether these IP settings are the right ones for Backup
Exec, I don't know, what exactly it is what Windows is complaining about.
Finally I uninstalled BE and SQL Server and reinstalled it, but without
success.
You stated, that TCP is not needed if everything is running on one server.
So I think I'm going to ignore the message since everything seems to work.
Thanks again.|||Hi Tim
"Tim Meltzer" wrote:
> Hi John,
> thanks for input.
> > In the Network Protocols branch under SQL Server Configuration Manager, is
> > the protocol Enabled?
> Which protocol? I tried them all, the error no. 3 remained.
> > If you double click the tcp/ip entry that you will get
> > the IP and port settings in the properties dialog.
> Yes, but I don't no, wether these IP settings are the right ones for Backup
> Exec, I don't know, what exactly it is what Windows is complaining about.
> Finally I uninstalled BE and SQL Server and reinstalled it, but without
> success.
> You stated, that TCP is not needed if everything is running on one server.
> So I think I'm going to ignore the message since everything seems to work.
> Thanks again.
It is not clear where exactly where the error message is being displayed! Is
this in Backup exec, SQL Server error log or the Windows Event log?
If after installing Backup Exec again what protocols are enabled?
John

how to configure database settings from config file?

Hi guys,
I am very new to Reporting Services, so please bear with me here. I am
curious about how we can configure the database server, database name, and
login data using data from a properties file so that when Reporting Services
and the Report Server start up, they have all the data they need to connect
to the appropriate database. Has anyone tried this yet? If so how would it
be possible?
Thanks a bunch,
Carolyn
cvoREMOVE_ALL_CAPS@.REMOVE_ALL_CAPSacornsys.comPlease take a look at RSConfig.exe tool. You should be able to provide these
settings as command line parameters to this tool.
--
Dmitry Vasilevsky, SQL Server Reporting Services Developer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
---
"Carolyn Vo" <cvoREMOVE_ALL_CAPS@.REMOVE_ALL_CAPSacornsys.com> wrote in
message news:OYdWxHGhEHA.3320@.TK2MSFTNGP11.phx.gbl...
> Hi guys,
> I am very new to Reporting Services, so please bear with me here. I am
> curious about how we can configure the database server, database name, and
> login data using data from a properties file so that when Reporting
Services
> and the Report Server start up, they have all the data they need to
connect
> to the appropriate database. Has anyone tried this yet? If so how would
it
> be possible?
> Thanks a bunch,
> Carolyn
> cvoREMOVE_ALL_CAPS@.REMOVE_ALL_CAPSacornsys.com
>|||You may find the following posting useful:
http://prologika.com/blog/archive/2004/08/20/161.aspx
--
Hope this helps.
---
Teo Lachev, MCSD, MCT
Author: "Microsoft Reporting Services in Action"
http://www.prologika.com
---
"Carolyn Vo" <cvoREMOVE_ALL_CAPS@.REMOVE_ALL_CAPSacornsys.com> wrote in
message news:OYdWxHGhEHA.3320@.TK2MSFTNGP11.phx.gbl...
> Hi guys,
> I am very new to Reporting Services, so please bear with me here. I am
> curious about how we can configure the database server, database name, and
> login data using data from a properties file so that when Reporting
Services
> and the Report Server start up, they have all the data they need to
connect
> to the appropriate database. Has anyone tried this yet? If so how would
it
> be possible?
> Thanks a bunch,
> Carolyn
> cvoREMOVE_ALL_CAPS@.REMOVE_ALL_CAPSacornsys.com
>