Create a new SQL Server database

I have Visual Studio 2003 Developer edition installed. The "Create a new SQL Server database" item is not enabled in the server explorer when I right click on connection. Do I have to instal a different version...or is there a common solution for this?

Thank you.

CJG

in VS 2003 , you can't .

to create a new database for SqlServer , you have to use Enterprise Manager for your SQL server version ,

if you dont have one , you can install it fromhere:

Create a new maintenance plan

I have installed SQLServer 2005 from Small Business Server premium edition. The package has been upgraded to SP2 and all the fixes have been applied.

I want to create a new maintenance plan to automate my DB backup procedures using SQL Server Management Studio. I start Management Studio and right click on the management folder and I I see is "Refresh" there is no "Create New Maintenance" plan presented.

I have tried this using the sa built-in account and the server administrator account both of which have sysadmin priviledges. I have also tried it from a client machine with another sysadmin userid but they all give the same results.

I checked to see if SSIS was installed. The add/remove programs wizard for SQL Server shows Integration Services SP2 is installed but I went ahead anyway and re-installed without error.

It seems that either SSIS is not running or I my user roles are preventing the maintenance wizard from running. Is there some way that I can tell if, in fact, SSIS is properly installed and running?

Thanks.

To create or manage maintenance plans, you must be a member of the sysadmin fixed server role. Note that Object Explorer only displays maintenance plans if the user is a member of the sysadmin fixed server role.

See http://technet.microsoft.com/en-us/library/ms189036(SQL.90).aspxsql

Create a new maintenance plan

I have installed SQLServer 2005 from Small Business Server premium edition. The package has been upgraded to SP2 and all the fixes have been applied.

I want to create a new maintenance plan to automate my DB backup procedures using SQL Server Management Studio. I start Management Studio and right click on the management folder and I I see is "Refresh" there is no "Create New Maintenance" plan presented.

I have tried this using the sa built-in account and the server administrator account both of which have sysadmin priviledges. I have also tried it from a client machine with another sysadmin userid but they all give the same results.

I checked to see if SSIS was installed. The add/remove programs wizard for SQL Server shows Integration Services SP2 is installed but I went ahead anyway and re-installed without error.

It seems that either SSIS is not running or I my user roles are preventing the maintenance wizard from running. Is there some way that I can tell if, in fact, SSIS is properly installed and running?

Thanks.

To create or manage maintenance plans, you must be a member of the sysadmin fixed server role. Note that Object Explorer only displays maintenance plans if the user is a member of the sysadmin fixed server role.

See http://technet.microsoft.com/en-us/library/ms189036(SQL.90).aspx

Crashing a server

Hi,
First of all I want to know if there is a manual way of crashing a server.
My second question -
I have two Standard Edition SQL Servers one(S1) running the production databases, and the other(S2) is just a standby. The database files are on a DISK array. Suppose if S1 crashes, can I point to the S2 Server to the same DISK array and use sp_attch sp's
to bring the database up.
Thanks,
Elvis
Have yo tried poring coke on the motherboard? That would crash the server
pretty good... you might want to explain what particular behairor you want
to cause to happen and then perhaps someone could offer good advice about
how to achieve it...
About the sp_attach...
there are a few issues.
1. Is it shared in some kind of cluster or SAN? Databases in SQL need to be
on local drives. So, you can't simply attach if the files are on a drive
that looks like a network drive to SQL.
2. If S1 goes down in an uncontrolled manner... the files themselves may be
damaged. Even if they're not damages... you can't guarantee the ability to
do an attach unless you had first done a detach. So... know... this doesn't
sound like a great solutioin.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Elvis Clinton" <anonymous@.discussions.microsoft.com> wrote in message
news:FA9EB5D2-AB32-4903-B270-DC5F6C2AC09C@.microsoft.com...
> Hi,
> First of all I want to know if there is a manual way of crashing a server.
> My second question -
> I have two Standard Edition SQL Servers one(S1) running the production
databases, and the other(S2) is just a standby. The database files are on a
DISK array. Suppose if S1 crashes, can I point to the S2 Server to the same
DISK array and use sp_attch sp's to bring the database up.
> Thanks,
> Elvis

Crashing a server

Hi,
First of all I want to know if there is a manual way of crashing a server.
My second question -
I have two Standard Edition SQL Servers one(S1) running the production datab
ases, and the other(S2) is just a standby. The database files are on a DISK
array. Suppose if S1 crashes, can I point to the S2 Server to the same DISK
array and use sp_attch sp's
to bring the database up.
Thanks,
ElvisHave yo tried poring coke on the motherboard? That would crash the server
pretty good... you might want to explain what particular behairor you want
to cause to happen and then perhaps someone could offer good advice about
how to achieve it...
About the sp_attach...
there are a few issues.
1. Is it shared in some kind of cluster or SAN? Databases in SQL need to be
on local drives. So, you can't simply attach if the files are on a drive
that looks like a network drive to SQL.
2. If S1 goes down in an uncontrolled manner... the files themselves may be
damaged. Even if they're not damages... you can't guarantee the ability to
do an attach unless you had first done a detach. So... know... this doesn't
sound like a great solutioin.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Elvis Clinton" <anonymous@.discussions.microsoft.com> wrote in message
news:FA9EB5D2-AB32-4903-B270-DC5F6C2AC09C@.microsoft.com...
> Hi,
> First of all I want to know if there is a manual way of crashing a server.
> My second question -
> I have two Standard Edition SQL Servers one(S1) running the production
databases, and the other(S2) is just a standby. The database files are on a
DISK array. Suppose if S1 crashes, can I point to the S2 Server to the same
DISK array and use sp_attch sp's to bring the database up.
> Thanks,
> Elvis

CR / VB Sort Problem

OS= Windows XP SP2 Professional, Crystal Report XI Developers Edition, Visual Basic 6 Enterprise

Below is the code I am trying to use to print a report. This code except for this "ElseIf" statement is used and works fine to print other reports. The only difference between printing this report and the other reports is 1) the name of the report and 2) this is the only report I have a sortfield.
.
.
.
ElseIf ReportName = "Alternate.rpt" Then
Set craxreport = craxapp.OpenReport(ReportPath & "\" & ReportName)
Set dbTable = craxreport.Database.Tables(1)
craxreport.RecordSortFields(0) = "+{AlternatePart.dbEnterDate}"
End If
craxreport.DiscardSavedData
' ****************************************************************************************
CrystalActiveXReportViewer1.Refresh
Call CrystalActiveXReportViewer1_RefreshButtonClicked(True)
CrystalActiveXReportViewer1.ReportSource = craxreport
CrystalActiveXReportViewer1.ViewReport
Set craxreport = Nothing
When I run this code, if I keep "craxreport.RecordSortFields(0) " I get a "Subscript out of Range" error.

The report is defined as follows:
- It uses a table called "AlternatePart"
- There are 3 fields in the table - (dbOldPn, dbNewPn, and dbEnterDate)
- All fields are described at TEXT
- The report shows all 3 fields.
- I used the Record Sort Expert to set up one sort field and that is "AlternatePart.dbEnterDate"

Can you tell me what is possibly causing the above error?

ThanksI have a little experience with crax.
I think maybe Indexes are not zero based. try index 1|||Yes try using craxreport.RecordSortFields(1) and see if it is working|||Yes try using craxreport.RecordSortFields(1) and see if it is working
That was the problem -- thank you.

Sam

CPUs and RAM limit on workgroup edition

I can find out the limit of CPUs and ram on workgroup edition are 2pc and
3GB respectively. What does this mean if I have 4 CPUs and 4GB ram in one
machine? The 3GB ram limitation refers to the maximum size of memory
allocated to SQL Server?
Thanks!The CPU and memory restrictions refer to the maximum SQL Server will use.
The additional processors/memory will be available to other applications but
ignored by SQL Server.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Jackie" <-> wrote in message news:OHt2YphsGHA.1196@.TK2MSFTNGP04.phx.gbl...
>I can find out the limit of CPUs and ram on workgroup edition are 2pc and
> 3GB respectively. What does this mean if I have 4 CPUs and 4GB ram in one
> machine? The 3GB ram limitation refers to the maximum size of memory
> allocated to SQL Server?
> Thanks!
>
>

CPUs and RAM limit on workgroup edition

I can find out the limit of CPUs and ram on workgroup edition are 2pc and
3GB respectively. What does this mean if I have 4 CPUs and 4GB ram in one
machine? The 3GB ram limitation refers to the maximum size of memory
allocated to SQL Server?
Thanks!The CPU and memory restrictions refer to the maximum SQL Server will use.
The additional processors/memory will be available to other applications but
ignored by SQL Server.
Hope this helps.
Dan Guzman
SQL Server MVP
"Jackie" <-> wrote in message news:OHt2YphsGHA.1196@.TK2MSFTNGP04.phx.gbl...
>I can find out the limit of CPUs and ram on workgroup edition are 2pc and
> 3GB respectively. What does this mean if I have 4 CPUs and 4GB ram in one
> machine? The 3GB ram limitation refers to the maximum size of memory
> allocated to SQL Server?
> Thanks!
>
>

CPU usage (HIGH, MEDIUM, LOW)

I have a Windows 2000 Advanced Server with SQL Server
2000 Enterprise Edition with SP3A.
The server has approximately 300 users and CPU usage
stays
states between 90 to 100 % for at least 200 minutes out
of a 12 hour processing windows in time.
What is a good metric for LOW, MEDIUIM, and HIGH CPU
usage rates.
Thanks,
Mark
Hi,
90-100% for more than 3 hours will be a problem. Idetify the process (might
be batch) causing the bottle neck.
If you find that there is no much optimization can be done in your program ,
probably go for 1 more additional CPU.
Low : Less than 20%
Medium : Between 21 % to 60%
High : Any thing above 60%
Thanks
Hari
MCDBA
"Mark" <anonymous@.discussions.microsoft.com> wrote in message
news:222e501c45d80$90292870$a601280a@.phx.gbl...
> I have a Windows 2000 Advanced Server with SQL Server
> 2000 Enterprise Edition with SP3A.
> The server has approximately 300 users and CPU usage
> stays
> states between 90 to 100 % for at least 200 minutes out
> of a 12 hour processing windows in time.
> What is a good metric for LOW, MEDIUIM, and HIGH CPU
> usage rates.
> Thanks,
> Mark
>
>
|||Hi,
90-100% for more than 3 hours will be a problem. Idetify the process (might
be batch) causing the bottle neck.
If you find that there is no much optimization can be done in your program ,
probably go for 1 more additional CPU.
Low : Less than 20%
Medium : Between 21 % to 60%
High : Any thing above 60%
Thanks
Hari
MCDBA
"Mark" <anonymous@.discussions.microsoft.com> wrote in message
news:222e501c45d80$90292870$a601280a@.phx.gbl...
> I have a Windows 2000 Advanced Server with SQL Server
> 2000 Enterprise Edition with SP3A.
> The server has approximately 300 users and CPU usage
> stays
> states between 90 to 100 % for at least 200 minutes out
> of a 12 hour processing windows in time.
> What is a good metric for LOW, MEDIUIM, and HIGH CPU
> usage rates.
> Thanks,
> Mark
>
>

CPU usage (HIGH, MEDIUM, LOW)

I have a Windows 2000 Advanced Server with SQL Server
2000 Enterprise Edition with SP3A.
The server has approximately 300 users and CPU usage
stays
states between 90 to 100 % for at least 200 minutes out
of a 12 hour processing windows in time.
What is a good metric for LOW, MEDIUIM, and HIGH CPU
usage rates.
Thanks,
MarkHi,
90-100% for more than 3 hours will be a problem. Idetify the process (might
be batch) causing the bottle neck.
If you find that there is no much optimization can be done in your program ,
probably go for 1 more additional CPU.
Low : Less than 20%
Medium : Between 21 % to 60%
High : Any thing above 60%
Thanks
Hari
MCDBA
"Mark" <anonymous@.discussions.microsoft.com> wrote in message
news:222e501c45d80$90292870$a601280a@.phx
.gbl...
> I have a Windows 2000 Advanced Server with SQL Server
> 2000 Enterprise Edition with SP3A.
> The server has approximately 300 users and CPU usage
> stays
> states between 90 to 100 % for at least 200 minutes out
> of a 12 hour processing windows in time.
> What is a good metric for LOW, MEDIUIM, and HIGH CPU
> usage rates.
> Thanks,
> Mark
>
>

CPU usage (HIGH, MEDIUM, LOW)

I have a Windows 2000 Advanced Server with SQL Server
2000 Enterprise Edition with SP3A.
The server has approximately 300 users and CPU usage
stays
states between 90 to 100 % for at least 200 minutes out
of a 12 hour processing windows in time.
What is a good metric for LOW, MEDIUIM, and HIGH CPU
usage rates.
Thanks,
MarkHi,
90-100% for more than 3 hours will be a problem. Idetify the process (might
be batch) causing the bottle neck.
If you find that there is no much optimization can be done in your program ,
probably go for 1 more additional CPU.
Low : Less than 20%
Medium : Between 21 % to 60%
High : Any thing above 60%
--
Thanks
Hari
MCDBA
"Mark" <anonymous@.discussions.microsoft.com> wrote in message
news:222e501c45d80$90292870$a601280a@.phx.gbl...
> I have a Windows 2000 Advanced Server with SQL Server
> 2000 Enterprise Edition with SP3A.
> The server has approximately 300 users and CPU usage
> stays
> states between 90 to 100 % for at least 200 minutes out
> of a 12 hour processing windows in time.
> What is a good metric for LOW, MEDIUIM, and HIGH CPU
> usage rates.
> Thanks,
> Mark
>
>

CPU spike with SQL Server 2005 Express Edition

Hello,
Any help is greatly appreciated.
I've recently upgraded my MSDE 2000 to SQL Server 2005 Express Edition
on my Windows 2003 server SP1. I've noticted that running a single one
table query against the new sql engine causes the sqlservr.exe process
to consume 98% of CPU on the server. The spike usually lasts for a
20-30 seconds and I can't figure out why. The query is a simple select
query against one table with only 3000 records.
The server is a one proc machine 2.0 GHz celeron, with 1 GB of RAM.
Again, any suggestions are appreciated.
Thank you.support@.holylandmarket.com wrote:
> Hello,
> Any help is greatly appreciated.
> I've recently upgraded my MSDE 2000 to SQL Server 2005 Express Edition
> on my Windows 2003 server SP1. I've noticted that running a single one
> table query against the new sql engine causes the sqlservr.exe process
> to consume 98% of CPU on the server. The spike usually lasts for a
> 20-30 seconds and I can't figure out why. The query is a simple select
> query against one table with only 3000 records.
> The server is a one proc machine 2.0 GHz celeron, with 1 GB of RAM.
> Again, any suggestions are appreciated.
> Thank you.
>
What does the execution plan for the query look like? What is the
heaviest part of the plan?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||It looks like the index scan is the heaviest part of the plan. The
problem is I get high CPU spikes regardless of the query I run.
Again the db is very small with very little data in it. I have the
same db running on Windows XP and I don't see any CPU spikes.
Isam
Thanks.
Tracy McKibben wrote:
> support@.holylandmarket.com wrote:
> What does the execution plan for the query look like? What is the
> heaviest part of the plan?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Isam wrote:
> It looks like the index scan is the heaviest part of the plan. The
> problem is I get high CPU spikes regardless of the query I run.
> Again the db is very small with very little data in it. I have the
> same db running on Windows XP and I don't see any CPU spikes.
>
You say the spike lasts for 20-30 seconds - how long does the query run?
Do you have auto-close enabled on this database?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||The query comes back in sub second but the process is still pegged.
Auto Close is set to True on the db.
Isam
Tracy McKibben wrote:
> Isam wrote:
> You say the spike lasts for 20-30 seconds - how long does the query run?
> Do you have auto-close enabled on this database?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Isam wrote:
> The query comes back in sub second but the process is still pegged.
> Auto Close is set to True on the db.
>
Turn that off and see if the spike goes away...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I can still see it spike. Turning auto close off did not change much.
Isam
support@.holylandmarket.com wrote:
> Hello,
> Any help is greatly appreciated.
> I've recently upgraded my MSDE 2000 to SQL Server 2005 Express Edition
> on my Windows 2003 server SP1. I've noticted that running a single one
> table query against the new sql engine causes the sqlservr.exe process
> to consume 98% of CPU on the server. The spike usually lasts for a
> 20-30 seconds and I can't figure out why. The query is a simple select
> query against one table with only 3000 records.
> The server is a one proc machine 2.0 GHz celeron, with 1 GB of RAM.
> Again, any suggestions are appreciated.
> Thank you.

CPU spike with SQL Server 2005 Express Edition

Hello,

Any help is greatly appreciated.

I've recently upgraded my MSDE 2000 to SQL Server 2005 Express Edition
on my Windows 2003 server SP1. I've noticted that running a single one

table query against the new sql engine causes the sqlservr.exe process
to consume 98% of CPU on the server. The spike usually lasts for a
20-30 seconds and I can't figure out why. The query is a simple select

query against one table with only 3000 records.

The server is a one proc machine 2.0 GHz celeron, with 1 GB of RAM.

Again, any suggestions are appreciated.

Thank you.Isam wrote:

Quote:

Originally Posted by

Hello,
>
Any help is greatly appreciated.
>
>
I've recently upgraded my MSDE 2000 to SQL Server 2005 Express Edition
on my Windows 2003 server SP1. I've noticted that running a single one
>
table query against the new sql engine causes the sqlservr.exe process
to consume 98% of CPU on the server. The spike usually lasts for a
20-30 seconds and I can't figure out why. The query is a simple select
>
query against one table with only 3000 records.
>
>
The server is a one proc machine 2.0 GHz celeron, with 1 GB of RAM.
>
>
Again, any suggestions are appreciated.
>
>
Thank you.

Oddly, the first rule of computer trouble shooting would seem to apply
here: When in doubt, turn off the Microsoft product. :P

Seriously, does this happen even after restarting SQL and/or the
server?

That's about it for me. I don't know enough to really trouble shoot
this, but I can point out the obvious with the best of them. ;)

--Richard|||Isam (support@.holylandmarket.com) writes:

Quote:

Originally Posted by

I've recently upgraded my MSDE 2000 to SQL Server 2005 Express Edition
on my Windows 2003 server SP1. I've noticted that running a single one
table query against the new sql engine causes the sqlservr.exe process
to consume 98% of CPU on the server. The spike usually lasts for a
20-30 seconds and I can't figure out why. The query is a simple select
query against one table with only 3000 records.

Does the query run for 20-30 seconds, or does it complete long before
the CPU spike is over?

Care to post the query and the definition for the underlying table?

By the way, did you run UPDATE STATISTICS on all tables after the upgrade?

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

CPU spike with SQL Server 2005 Express Edition

Hello,
Any help is greatly appreciated.
I've recently upgraded my MSDE 2000 to SQL Server 2005 Express Edition
on my Windows 2003 server SP1. I've noticted that running a single one
table query against the new sql engine causes the sqlservr.exe process
to consume 98% of CPU on the server. The spike usually lasts for a
20-30 seconds and I can't figure out why. The query is a simple select
query against one table with only 3000 records.
The server is a one proc machine 2.0 GHz celeron, with 1 GB of RAM.
Again, any suggestions are appreciated.
Thank you.support@.holylandmarket.com wrote:
> Hello,
> Any help is greatly appreciated.
> I've recently upgraded my MSDE 2000 to SQL Server 2005 Express Edition
> on my Windows 2003 server SP1. I've noticted that running a single one
> table query against the new sql engine causes the sqlservr.exe process
> to consume 98% of CPU on the server. The spike usually lasts for a
> 20-30 seconds and I can't figure out why. The query is a simple select
> query against one table with only 3000 records.
> The server is a one proc machine 2.0 GHz celeron, with 1 GB of RAM.
> Again, any suggestions are appreciated.
> Thank you.
>
What does the execution plan for the query look like? What is the
heaviest part of the plan?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||It looks like the index scan is the heaviest part of the plan. The
problem is I get high CPU spikes regardless of the query I run.
Again the db is very small with very little data in it. I have the
same db running on Windows XP and I don't see any CPU spikes.
Isam
Thanks.
Tracy McKibben wrote:
> support@.holylandmarket.com wrote:
> > Hello,
> >
> > Any help is greatly appreciated.
> >
> > I've recently upgraded my MSDE 2000 to SQL Server 2005 Express Edition
> > on my Windows 2003 server SP1. I've noticted that running a single one
> > table query against the new sql engine causes the sqlservr.exe process
> > to consume 98% of CPU on the server. The spike usually lasts for a
> > 20-30 seconds and I can't figure out why. The query is a simple select
> > query against one table with only 3000 records.
> >
> > The server is a one proc machine 2.0 GHz celeron, with 1 GB of RAM.
> >
> > Again, any suggestions are appreciated.
> >
> > Thank you.
> >
> What does the execution plan for the query look like? What is the
> heaviest part of the plan?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Isam wrote:
> It looks like the index scan is the heaviest part of the plan. The
> problem is I get high CPU spikes regardless of the query I run.
> Again the db is very small with very little data in it. I have the
> same db running on Windows XP and I don't see any CPU spikes.
>
You say the spike lasts for 20-30 seconds - how long does the query run?
Do you have auto-close enabled on this database?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||The query comes back in sub second but the process is still pegged.
Auto Close is set to True on the db.
Isam
Tracy McKibben wrote:
> Isam wrote:
> > It looks like the index scan is the heaviest part of the plan. The
> > problem is I get high CPU spikes regardless of the query I run.
> >
> > Again the db is very small with very little data in it. I have the
> > same db running on Windows XP and I don't see any CPU spikes.
> >
> You say the spike lasts for 20-30 seconds - how long does the query run?
> Do you have auto-close enabled on this database?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Isam wrote:
> The query comes back in sub second but the process is still pegged.
> Auto Close is set to True on the db.
>
Turn that off and see if the spike goes away...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I can still see it spike. Turning auto close off did not change much.
Isam
support@.holylandmarket.com wrote:
> Hello,
> Any help is greatly appreciated.
> I've recently upgraded my MSDE 2000 to SQL Server 2005 Express Edition
> on my Windows 2003 server SP1. I've noticted that running a single one
> table query against the new sql engine causes the sqlservr.exe process
> to consume 98% of CPU on the server. The spike usually lasts for a
> 20-30 seconds and I can't figure out why. The query is a simple select
> query against one table with only 3000 records.
> The server is a one proc machine 2.0 GHz celeron, with 1 GB of RAM.
> Again, any suggestions are appreciated.
> Thank you.

CPU licensing question

We moved from a 4 CPU server to a 2 CPU server and when we installed SQL
Server (Enterprise Edition) on the replacement server we specified 4 CPU
licenses without thinking. We would now like to apply the 2 "spare" CPU
licenses to a new server. Can we just go ahead and apply them (since they're
not useable on the current 2 CPU server) or do we need to somehow remove them
from the 2 CPU server first?
You can specify the number of CPU licenses you have from the SQL Server
license utility in Control Panel. It's a good idea to change it to the
appropriate number just to make life easier from an audit and license
management perspective.
joe.
"J Jetson" <JJetson@.discussions.microsoft.com> wrote in message
news:FE011F53-2309-4ACD-B79D-D906EAC73171@.microsoft.com...
> We moved from a 4 CPU server to a 2 CPU server and when we installed SQL
> Server (Enterprise Edition) on the replacement server we specified 4 CPU
> licenses without thinking. We would now like to apply the 2 "spare" CPU
> licenses to a new server. Can we just go ahead and apply them (since
they're
> not useable on the current 2 CPU server) or do we need to somehow remove
them
> from the 2 CPU server first?

CPU licensing question

We moved from a 4 CPU server to a 2 CPU server and when we installed SQL
Server (Enterprise Edition) on the replacement server we specified 4 CPU
licenses without thinking. We would now like to apply the 2 "spare" CPU
licenses to a new server. Can we just go ahead and apply them (since they're
not useable on the current 2 CPU server) or do we need to somehow remove the
m
from the 2 CPU server first?You can specify the number of CPU licenses you have from the SQL Server
license utility in Control Panel. It's a good idea to change it to the
appropriate number just to make life easier from an audit and license
management perspective.
joe.
"J Jetson" <JJetson@.discussions.microsoft.com> wrote in message
news:FE011F53-2309-4ACD-B79D-D906EAC73171@.microsoft.com...
> We moved from a 4 CPU server to a 2 CPU server and when we installed SQL
> Server (Enterprise Edition) on the replacement server we specified 4 CPU
> licenses without thinking. We would now like to apply the 2 "spare" CPU
> licenses to a new server. Can we just go ahead and apply them (since
they're
> not useable on the current 2 CPU server) or do we need to somehow remove
them
> from the 2 CPU server first?

CPU licensing question

We moved from a 4 CPU server to a 2 CPU server and when we installed SQL
Server (Enterprise Edition) on the replacement server we specified 4 CPU
licenses without thinking. We would now like to apply the 2 "spare" CPU
licenses to a new server. Can we just go ahead and apply them (since they're
not useable on the current 2 CPU server) or do we need to somehow remove them
from the 2 CPU server first?You can specify the number of CPU licenses you have from the SQL Server
license utility in Control Panel. It's a good idea to change it to the
appropriate number just to make life easier from an audit and license
management perspective.
joe.
"J Jetson" <JJetson@.discussions.microsoft.com> wrote in message
news:FE011F53-2309-4ACD-B79D-D906EAC73171@.microsoft.com...
> We moved from a 4 CPU server to a 2 CPU server and when we installed SQL
> Server (Enterprise Edition) on the replacement server we specified 4 CPU
> licenses without thinking. We would now like to apply the 2 "spare" CPU
> licenses to a new server. Can we just go ahead and apply them (since
they're
> not useable on the current 2 CPU server) or do we need to somehow remove
them
> from the 2 CPU server first?

CPU Distribution between Sql Server and OS

Hi,
I am a DBA for SQL server and I have a poduct to be tested for performance
with backend MSSQL Server 2005 developer edition. I have a machine of 8CPU's
and the senario is
the dataserver has to function for some big computations and data processing.
application is on .Net c# code also will be loaded on the same machine,
should also be scaleable with multiple users working on the app. and database
access.
My question is
1) Is there a guodeline for spliting the CPU's with MSSQL server and OS ( OS
and App)
2) Are any documented(cases) white papers on the same(resourse charing
between OS and sql server).
Please share you experiencies.
Thanks,
fellow DBA.
Hi
"Krish" wrote:

> Hi,
> I am a DBA for SQL server and I have a poduct to be tested for performance
> with backend MSSQL Server 2005 developer edition. I have a machine of 8CPU's
> and the senario is
> the dataserver has to function for some big computations and data processing.
> application is on .Net c# code also will be loaded on the same machine,
> should also be scaleable with multiple users working on the app. and database
> access.
> My question is
> 1) Is there a guodeline for spliting the CPU's with MSSQL server and OS ( OS
> and App)
> 2) Are any documented(cases) white papers on the same(resourse charing
> between OS and sql server).
> Please share you experiencies.
> Thanks,
> fellow DBA.
I don't know of any white papers, these things are not recommend to be on
the same machine; a general value would only be a starting point anyhow. You
should decide the configuration from the results of your load testing and
cover as many hardware combinations as possible to get the best results.
You can not use Developer Edition for a production system, if the hardware
you are testing on is not the same as the destination server you may only
have a general guideline to performance.
John

CPU Distribution between Sql Server and OS

Hi,
I am a DBA for SQL server and I have a poduct to be tested for performance
with backend MSSQL Server 2005 developer edition. I have a machine of 8CPU's
and the senario is
the dataserver has to function for some big computations and data processing
.
application is on .Net c# code also will be loaded on the same machine,
should also be scaleable with multiple users working on the app. and databas
e
access.
My question is
1) Is there a guodeline for spliting the CPU's with MSSQL server and OS ( OS
and App)
2) Are any documented(cases) white papers on the same(resourse charing
between OS and sql server).
Please share you experiencies.
Thanks,
fellow DBA.Hi
"Krish" wrote:

> Hi,
> I am a DBA for SQL server and I have a poduct to be tested for performance
> with backend MSSQL Server 2005 developer edition. I have a machine of 8CPU
's
> and the senario is
> the dataserver has to function for some big computations and data processi
ng.
> application is on .Net c# code also will be loaded on the same machine,
> should also be scaleable with multiple users working on the app. and datab
ase
> access.
> My question is
> 1) Is there a guodeline for spliting the CPU's with MSSQL server and OS (
OS
> and App)
> 2) Are any documented(cases) white papers on the same(resourse charing
> between OS and sql server).
> Please share you experiencies.
> Thanks,
> fellow DBA.
I don't know of any white papers, these things are not recommend to be on
the same machine; a general value would only be a starting point anyhow. You
should decide the configuration from the results of your load testing and
cover as many hardware combinations as possible to get the best results.
You can not use Developer Edition for a production system, if the hardware
you are testing on is not the same as the destination server you may only
have a general guideline to performance.
John

CPU Distribution between Sql Server and OS

Hi,
I am a DBA for SQL server and I have a poduct to be tested for performance
with backend MSSQL Server 2005 developer edition. I have a machine of 8CPU's
and the senario is
the dataserver has to function for some big computations and data processing.
application is on .Net c# code also will be loaded on the same machine,
should also be scaleable with multiple users working on the app. and database
access.
My question is
1) Is there a guodeline for spliting the CPU's with MSSQL server and OS ( OS
and App)
2) Are any documented(cases) white papers on the same(resourse charing
between OS and sql server).
Please share you experiencies.
Thanks,
fellow DBA.Hi
"Krish" wrote:
> Hi,
> I am a DBA for SQL server and I have a poduct to be tested for performance
> with backend MSSQL Server 2005 developer edition. I have a machine of 8CPU's
> and the senario is
> the dataserver has to function for some big computations and data processing.
> application is on .Net c# code also will be loaded on the same machine,
> should also be scaleable with multiple users working on the app. and database
> access.
> My question is
> 1) Is there a guodeline for spliting the CPU's with MSSQL server and OS ( OS
> and App)
> 2) Are any documented(cases) white papers on the same(resourse charing
> between OS and sql server).
> Please share you experiencies.
> Thanks,
> fellow DBA.
I don't know of any white papers, these things are not recommend to be on
the same machine; a general value would only be a starting point anyhow. You
should decide the configuration from the results of your load testing and
cover as many hardware combinations as possible to get the best results.
You can not use Developer Edition for a production system, if the hardware
you are testing on is not the same as the destination server you may only
have a general guideline to performance.
John