Architecture

Hello,
I want to kow if the following architecture is good :
Disque 1&2 ( Raid 1)
c: OS
d: sqlserver + system tables + log files
Disque 3&4&5 (Raid 5)
e: dataIf you don't plan on having any volume it would be fine. Otherwise, it would suck. A 3 disk RAID array is the slowest RAID 5 configuration possible. In addition, if you want high performance you should have the tempdb and/or the log files on seperate disks.

If you only have five disks though, this should work.

Appricated.

If any one can give me the best recommandation of optimization of my SQL
Server machine wise or database wise or just let me know what are the
parameters I have to follow to make sure my sql server is perfact running on
the production machine or what sort of things I have to consider for
optimization.
Thanks in advance.
Hi
Start at http://www.sql-server-performance.com/
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rogers" <Rogers@.discussions.microsoft.com> wrote in message
news:8EB7BFC3-1588-487D-95BA-8DED737343A2@.microsoft.com...
> If any one can give me the best recommandation of optimization of my SQL
> Server machine wise or database wise or just let me know what are the
> parameters I have to follow to make sure my sql server is perfact running
> on
> the production machine or what sort of things I have to consider for
> optimization.
> Thanks in advance.
|||Those links I listed in your last are a good place to start. The default
settings for SQL Server are good in most cases. If you are having
performance issues it is most like due to poor coding or poor db design and
not a setting in SQL Server. Those links will help you to narrow down any
issues you may have.
Andrew J. Kelly SQL MVP
"Rogers" <Rogers@.discussions.microsoft.com> wrote in message
news:8EB7BFC3-1588-487D-95BA-8DED737343A2@.microsoft.com...
> If any one can give me the best recommandation of optimization of my SQL
> Server machine wise or database wise or just let me know what are the
> parameters I have to follow to make sure my sql server is perfact running
> on
> the production machine or what sort of things I have to consider for
> optimization.
> Thanks in advance.

Applying MS05-003 broke something...

Hi folks. I have a customer who applied MS05-003 (KB871259) to their server
running MS SQLServer 2000 SP3. On doing this, certain data uploads began to
fail. Once this patch was removed, things began working again. Is there a
known issue with this patch? Has anyone else run across a similar issue? If
so, can someone suggest a work-around or other solution?
Thank you.
Daniel.Please confirm the patch you have installed/un-installed.
MS05-003 is not KB871259
http://www.microsoft.com/technet/se...n/MS05-003.mspx
is 871250.
This patch affect the Indexing Service and replaces the following file on
Win2k
Ciodm.dll
5.0.2195.6981
05-Nov-2004
04:41
68,880
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
My bad. I typoed. The patch applied is MS05-003 / 871250.
Suggestions or known issues?
Daniel.
"Kevin McDonnell [MSFT]" wrote:

> Please confirm the patch you have installed/un-installed.
> MS05-003 is not KB871259
> http://www.microsoft.com/technet/se...n/MS05-003.mspx
> is 871250.
> This patch affect the Indexing Service and replaces the following file on
> Win2k
> Ciodm.dll
> 5.0.2195.6981
> 05-Nov-2004
> 04:41
> 68,880
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||I'm not aware of this particular patch affecting SQL Server, since we're
patching the Indexing Service.
The Indexing Service is a base service for MicrosoftWindows 2000 or later
that extracts content from files and constructs an indexed catalog to
facilitate efficient and rapid searching. It is used for local searching
and can also be utilized on an IIS Web server to search remotely (with
custom web application code)
Please confirm that removing the patch allows your SQL Server to function
correctly. Open up a case with us if you're able to reproduce the problem.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||"Kevin McDonnell [MSFT]" wrote:[vbcol=seagreen]
> Please confirm that removing the patch allows your SQL Server to function
> correctly. Open up a case with us if you're able to reproduce the problem.[/vbcol
]
Kevin, Confirmed. As for "opening a case", I'd appreciate just a little
direction on exactly how to do that. I have looked with little success on th
e
web site and nothing just jumps out and shouts "log a case here". Clues are
sufficient (ususally).
d.|||Call Support Customer Care:
1-800-936-3500 (U.S. and Canada Only)
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

App. Can't find database after a RESTORE

Hi,
My application in another server can't find the SQLServer database
after a restore. The name of the DB is exactly the same! The application say
s
the the Target Database does not match destination database. My question is:
Is it possible that the reason comes from the database even if the name is
exacty the same?
Do I have to restart the database server?
Thanks!
JoeYou don't have to 'restart' the server after a restore.
Can you connect to the database using Enterprise Mangler or Query Analyzer?
Please try connecting with EM and/or QA and post the entire error message.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Barb" <Barb@.discussions.microsoft.com> wrote in message
news:95F0ED39-6083-4586-936D-9BC582C314AC@.microsoft.com...
> Hi,
> My application in another server can't find the SQLServer database
> after a restore. The name of the DB is exactly the same! The application
> says
> the the Target Database does not match destination database. My question
> is:
> Is it possible that the reason comes from the database even if the name is
> exacty the same?
> Do I have to restart the database server?
> Thanks!
> Joe
>
>

API support on SQL Server ?

Is it true that MS is pulling support of API calls to SQL
Server for the upcoming and future release(s) ?It depends on exactly what you men by API calls. All DBMS's need some API,
otherwise you couldn't write applications against the DBMS. So, there is
definitely supported API's for Yukon. The only thing I know is that The old
dead DbLibrary is in the "danger zone", but I don't know the exact official
words about Db Library.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Michael" <mykliv@.htomail.com> wrote in message
news:c33c01c4085f$08ce2720$a101280a@.phx.gbl...
> Is it true that MS is pulling support of API calls to SQL
> Server for the upcoming and future release(s) ?

Anything wrong with the connection?

Dear all,
I have a program (written in VB6) running in a Win2000 server with SQL
server 2000 in it. However, the program runs very slow or even "Time Out
Expired" many times. My connection string is:
strConn = "Provider=SQLOLEDB;Data Source=myServer;Initial Catalog=myDB;User
Id=mySQLUser;Password=myPassword;"
On the other hand I tried to run the same program in my own PC (Win2000
professional) with SQL desktop version. The program runs very fast. Can
anyone advise what is the problem when the program is running in SQL server
2000?
Thanks a million!!
Ivan
On Mon, 7 Nov 2005 01:26:50 -0800, Ivan wrote:

> Dear all,
> I have a program (written in VB6) running in a Win2000 server with SQL
> server 2000 in it. However, the program runs very slow or even "Time Out
> Expired" many times. My connection string is:
> strConn = "Provider=SQLOLEDB;Data Source=myServer;Initial Catalog=myDB;User
> Id=mySQLUser;Password=myPassword;"
> On the other hand I tried to run the same program in my own PC (Win2000
> professional) with SQL desktop version. The program runs very fast. Can
> anyone advise what is the problem when the program is running in SQL server
> 2000?
> Thanks a million!!
> Ivan
Hello,
I'm afraid that you need to investigate more in depth. Probably nothing to
do with your connection. Try to use the SQL Server profiler to trace
queries sent to the server, and watch things like reads, CPU, duration on
this trace. Then isolate the queires that could cause problems and watch
their query plan. Search for indexes that could lack.
Look in Enterprise Manager (or doing a sp_who2, or sp_lock) the number of
connections, and if there are blocking locks. Have also a look at some
performance counters.
You'll need to search for hints. Info you gave is not sufficient to give a
clue of what could be the problem.
Good luck
Rudi Bruchez
MCDBA

Anything wrong with the connection?

Dear all,
I have a program (written in VB6) running in a Win2000 server with SQL
server 2000 in it. However, the program runs very slow or even "Time Out
Expired" many times. My connection string is:
strConn = "Provider=SQLOLEDB;Data Source=myServer;Initial Catalog=myDB;User
Id=mySQLUser;Password=myPassword;"
On the other hand I tried to run the same program in my own PC (Win2000
professional) with SQL desktop version. The program runs very fast. Can
anyone advise what is the problem when the program is running in SQL server
2000?
Thanks a million!!
IvanOn Mon, 7 Nov 2005 01:26:50 -0800, Ivan wrote:

> Dear all,
> I have a program (written in VB6) running in a Win2000 server with SQL
> server 2000 in it. However, the program runs very slow or even "Time Out
> Expired" many times. My connection string is:
> strConn = "Provider=SQLOLEDB;Data Source=myServer;Initial Catalog=myDB;Use
r
> Id=mySQLUser;Password=myPassword;"
> On the other hand I tried to run the same program in my own PC (Win2000
> professional) with SQL desktop version. The program runs very fast. Can
> anyone advise what is the problem when the program is running in SQL serve
r
> 2000?
> Thanks a million!!
> Ivan
Hello,
I'm afraid that you need to investigate more in depth. Probably nothing to
do with your connection. Try to use the SQL Server profiler to trace
queries sent to the server, and watch things like reads, CPU, duration on
this trace. Then isolate the queires that could cause problems and watch
their query plan. Search for indexes that could lack.
Look in Enterprise Manager (or doing a sp_who2, or sp_lock) the number of
connections, and if there are blocking locks. Have also a look at some
performance counters.
You'll need to search for hints. Info you gave is not sufficient to give a
clue of what could be the problem.
Good luck
Rudi Bruchez
MCDBA