New SQL Server.....

I have just goten in my gruby little hands a brand spanking new server to run SQL on. Im talking about a beast of a box with 8 processers and 16 gig of ram. Im loading SQL server enterprise on it and have been raised with a question. The server peps here, "it profesionals" seem to think that i need to keep 2 processors free for the os. from everything that i have read threw my studies of SQL i have seen that that is crap, that SQL will give the os its resources as it needs them. Any thoughts on this and or any Microsoft articles that prove your positions? Any help would be great here thanx
JimFirst have some respect and wash your hands!

Now... If this server is ONLY used for MSSQL server then reserving 2 processers for the OS is stupid. If you run allot of jobs or have software, other than MSQL stuff, running then reserve 1 processer AFTER seeing the remaining 7 running at 100% utilization 100% of the time. You can alter the cpu affinity at any time.

If you follow the recommendations I would be you would see the 2 OS cpus peg 100% about 0.000001% of the time and idle the remaining 99.999999% of the time!

I would ask the "professionals" to defend their point.|||Originally posted by Paul Young
First have some respect and wash your hands!

Now... If this server is ONLY used for MSSQL server then reserving 2 processers for the OS is stupid. If you run allot of jobs or have software, other than MSQL stuff, running then reserve 1 processer AFTER seeing the remaining 7 running at 100% utilization 100% of the time. You can alter the cpu affinity at any time.

If you follow the recommendations I would be you would see the 2 OS cpus peg 100% about 0.000001% of the time and idle the remaining 99.999999% of the time!

I would ask the "professionals" to defend their point.

Im with u on this one. When i set this thing up its gona go full throtel :)
thanx
any more feed back would also be nice
Regards Jim

New db cant be found

We have a brand new sql 2k server. Its all up to date on service packs
(both win2k and SQL).

I went in to enterprise manager and added a new db. I can run sprocs
and raw sql against the new db just fine from Query Analyzer.

When I try to make a dts package that refers to my new db I get the
following error:

Error desription: deferred prepare could not be completed.
Could not locate entry in sysdatabases for database 'mydbname'. No
entry found with that name. Make sure that the name is entered
correctly.

OK, so I look in sysdatabases and see 'mydbname'. Just in case im an
idiot... I actually copied the db name from that table and paste it in
my dts window.

My dts package is using an "execute SQL task" to call a stored proc.

To be ecxact:
USE mydbname
GO
EXEC MyProc

When I click on the parse button, is when I get that error message.

I have deleted the db, restarted the server, and recreated the db with
a slightly different name. I can replace mydbname with pubs or
northwind and all is ok. It just doesnt like new db's.

Any help would be greatly appreciated.

Thanks,
DaveHi

I am not sure why you need the USE statement if the associated connection is
already setting this as the database.

John

"Dave" <funkdm1@.yahoo.com> wrote in message
news:f5174e0f.0407130507.ac071b@.posting.google.com ...
> We have a brand new sql 2k server. Its all up to date on service packs
> (both win2k and SQL).
> I went in to enterprise manager and added a new db. I can run sprocs
> and raw sql against the new db just fine from Query Analyzer.
> When I try to make a dts package that refers to my new db I get the
> following error:
> Error desription: deferred prepare could not be completed.
> Could not locate entry in sysdatabases for database 'mydbname'. No
> entry found with that name. Make sure that the name is entered
> correctly.
> OK, so I look in sysdatabases and see 'mydbname'. Just in case im an
> idiot... I actually copied the db name from that table and paste it in
> my dts window.
> My dts package is using an "execute SQL task" to call a stored proc.
> To be ecxact:
> USE mydbname
> GO
> EXEC MyProc
> When I click on the parse button, is when I get that error message.
> I have deleted the db, restarted the server, and recreated the db with
> a slightly different name. I can replace mydbname with pubs or
> northwind and all is ok. It just doesnt like new db's.
> Any help would be greatly appreciated.
> Thanks,
> Dave