additional data files not filing

We have a quad sql server that runs OLTP transactions at the rate of
100's per second (read & Write).

We used to have all the tables on 1 file but started to notice high contention on this file. We added 3 more files to match the processor number. The problem is that the 3 additional files are not filling with data. Does anyone know why this happens or can reccommend a fix?
--
willVerify that the newly added files are in the appropriate file group (probably PRIMARY) and are of the appropriate file type (ie, they were created as data files, not log files). Also, your new file(s) may not get data written to them if the old file still has space available.

Your logic for reducing contention by adding files to match the number of processors does not make sense. Contention is caused by physical IO going to the same physical disk and getting backed up because the pipe to the physical disk is too small. You would add files to a database filegroup to ease contention by creating the files on separate physical disks. It has no relation the number of CPUs.

Regards,

hmscott|||Yes they are all the same file type (data files).

Microsoft claims that you should have a seperate file per processor for high contention OLTP sql servers. Parallelism is the goal here. Sql server can only access 1 file per cpu at any one time. If it was a dual processor machine It would have less impact considering the OS & tempdb usually have something going on in parallel.

Considering we have a quad sql server = 4 files per file group.

As an FYI we are running a raid 10 with 14 disks.|||Hmm, not doubting you, but could you send a link with the MS info? I had not seen that before.

As for your issue, what's the state of the original data file? Full, nearly full or not even close? Also, can you verify that the new files you added were updateable (ie, not read-only)? Beyond that, I would try testing some scenarios out on a development server somewhere.

Regards,

hmscott

adding second node to sql cluster

I created a one node Cluster in Windows 2003 enterprise server. I then loaded
a SQL 2000 Vitrual server. I now need to add a second node. The cluster sees
the new node. However when I attempt to load the SLQ executables on the
second node the only option I have once I choose the virtual server is to
upgrade the existing installation. That does not install the executable on
the second node. What am I doing wrong. Thanks in advance.
you must choose upgrade the existing installation on virual server and add
second node for existing virtual sql server
Aleksandar Grbic
MCDBA, Senior Database Administrator
"Joe McHae" wrote:

> I created a one node Cluster in Windows 2003 enterprise server. I then loaded
> a SQL 2000 Vitrual server. I now need to add a second node. The cluster sees
> the new node. However when I attempt to load the SLQ executables on the
> second node the only option I have once I choose the virtual server is to
> upgrade the existing installation. That does not install the executable on
> the second node. What am I doing wrong. Thanks in advance.
|||I did choose upgrade. I did not see an option to add a second node for the
existing sql server. The second server is in the cluster.
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> you must choose upgrade the existing installation on virual server and add
> second node for existing virtual sql server
> --
> Aleksandar Grbic
> MCDBA, Senior Database Administrator
>
> "Joe McHae" wrote:
|||In the setup routine, there will be an Advanced option. After selecting,
there will be a Maintain and Existing Installation option.
This will take you down an installation path were you can add new cluster
member nodes as a potential SQL Server failover partner.
In the maintenance section of the SQL Server 2000 failover clustering
document is an Add/Remove Cluster Nodes sub-section.
Adding or Removing a Cluster Node from the Virtual Server Definition
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx#EPUAG
Best of luck.
Sincerely,
Anthony Thomas

"Joe McHae" <JoeMcHae@.discussions.microsoft.com> wrote in message
news:332E6DA7-9F20-455C-97BE-ABD7BE8EFAE8@.microsoft.com...[vbcol=seagreen]
> I did choose upgrade. I did not see an option to add a second node for the
> existing sql server. The second server is in the cluster.
> "Aleksandar Grbic" wrote:
add[vbcol=seagreen]
loaded[vbcol=seagreen]
cluster sees[vbcol=seagreen]
the[vbcol=seagreen]
to[vbcol=seagreen]
executable on[vbcol=seagreen]
|||Anthony;
thanks, the problem I wa having was the executables for SQL were not loading
on the second node. I followed your link then removed the node and added it
again. for some reasons the executables are there. I guess that is why they
call it magic.
Joe
"Anthony Thomas" wrote:

> In the setup routine, there will be an Advanced option. After selecting,
> there will be a Maintain and Existing Installation option.
> This will take you down an installation path were you can add new cluster
> member nodes as a potential SQL Server failover partner.
> In the maintenance section of the SQL Server 2000 failover clustering
> document is an Add/Remove Cluster Nodes sub-section.
> Adding or Removing a Cluster Node from the Virtual Server Definition
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx#EPUAG
> Best of luck.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Joe McHae" <JoeMcHae@.discussions.microsoft.com> wrote in message
> news:332E6DA7-9F20-455C-97BE-ABD7BE8EFAE8@.microsoft.com...
> add
> loaded
> cluster sees
> the
> to
> executable on
>
>

Adding node to cluster

Hello everyone!
We currently have a one node cluster (w2k3 and sql2000ent) and have had it
this way for a while waiting on the second server to arrive, well, the time
has come and now we are about to install the second node in this
active/passive cluster.
I have been reading in booksonline on how to do this and it seems fairly
simple. Install the second server, add it to the cluster and run sql setup
on it, choosing "maintaining a virtual server for failover" and so on. Am I
right so far?
My questions are:
Should I run the sql installation from the new node or from the old one? Or
does it not matter?
When the installation is done I've understood that I have to reapply sp3a?
And that this is done from the node that is currently the owner?
Thanks in advance for your help!
Regards,
Erik
1. You run SQL Server setup from the old node, with SQL Server running on
that node.
2. You run SP3a from the node that currently owns SQL Server while SQL
Server is active on that node.
You will also need to apply any patches as well.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||1. You run SQL Server setup from the old node, with SQL Server running on
that node.
2. You run SP3a from the node that currently owns SQL Server while SQL
Server is active on that node.
You will also need to apply any patches as well.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thanks alot for those tips!
/Erik
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:h9sx6h6UEHA.2436@.cpmsftngxa10.phx.gbl...
> 1. You run SQL Server setup from the old node, with SQL Server running on
> that node.
> 2. You run SP3a from the node that currently owns SQL Server while SQL
> Server is active on that node.
> You will also need to apply any patches as well.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

Adding node back after hardware failure.

After you have to take a node out of a SQL cluster, what is
the procedure to get it back in the cluster?
The second machine is back up and working on the cluster
with everything except the SQL resources, which makes sense
because you have to install SQL on the cluster after it is
set up.
But how should we go about getting this machine back in the
SQL cluster? Should we just reinstall SQL on the cluster,
or should we uninstall first? Is uninstalling simple on a
cluster?
Is there anything obvious that I'm leaving out that will
cause us headaches?
Thanks in advance,
Shawn
Look up 'Maintaining a Failover Cluster' in BOL. It has step-by-step
instructions on how to replace a failed node in a SQL cluster.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Shawn" <anonymous@.discussions.microsoft.com> wrote in message
news:18cfe01c44bdc$c8664390$a501280a@.phx.gbl...
> After you have to take a node out of a SQL cluster, what is
> the procedure to get it back in the cluster?
> The second machine is back up and working on the cluster
> with everything except the SQL resources, which makes sense
> because you have to install SQL on the cluster after it is
> set up.
> But how should we go about getting this machine back in the
> SQL cluster? Should we just reinstall SQL on the cluster,
> or should we uninstall first? Is uninstalling simple on a
> cluster?
> Is there anything obvious that I'm leaving out that will
> cause us headaches?
> Thanks in advance,
> Shawn
|||Awesome. Thanks.
>--Original Message--
>Look up 'Maintaining a Failover Cluster' in BOL. It has
step-by-step
>instructions on how to replace a failed node in a SQL cluster.
>
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>I support the Professional Association for SQL Server
>www.sqlpass.org
>"Shawn" <anonymous@.discussions.microsoft.com> wrote in message
>news:18cfe01c44bdc$c8664390$a501280a@.phx.gbl...
>
>.
>