BCP Slower Standalone vs. A/P Cluster

I have an issue with the BCP util, it is extremely slow when running a BCP in to the same database on an A/P cluster vs. Standalone system. It is a vendor application, so I have little control as to what I can do. The BCP runs from a jobserver (remote) through the network, but it runs the same way in the standalone system, yet the process is about 10X as slow with the cluster, and the only diff is cluster vs. standalone.

SQLClusterName is specified in -S, not the active node, and it uses a trusted connection, not a local account. Is there anything about a cluster config that would cause the BCP to run slower ?

Any thoughts ??

Thanks,
PaulTry to add "-a32764" and see if that makes a difference.|||Thanks, but I also found out that the Cognos Jobserver (where BCP command is running from) is on a diff subnet than the sql cluster (data is going through a router) On the current standalone config, the jobserver and sqlserver are on the same subnet, also there are NETWORKIO status' for the BCP sessions when the Cognos publish is running, which may indicate a network problem.

Thanks,
Paul|||Thanks, did some initial testing with a 135K row sample, sped it up 5 fold, I am going to see if vendor can add this param to their gen'd BCPs.

Thanks Again,
Paul

Basic SQL Cluster Questions

Ok my job is done. I have built a fully tested Windows and SQL active/passive
cluster. Not the software guys take over but as an inquiring IT guy I can't
call it done withoout some more education.
Please feel free to answer these questions or send me to more information
please.
1. I understand that the virtual clusters "CompanyCluster IP address
x.x.x.x and SqlCluster IP Address x.x.x.x" are used to map databases and
point to as the reference for websites, databases and apps. Do you perform
any tasks on these virtual machines llike servicee packs or database installs
and maintenance?
1a. If you do not use the Virtual machines then I assume you use the active
node. Would that install the database to the other node automatically?
2. Where are the Virtual machines stored and should you back them up or are
they just basically cached on the active node?
3. How about backup software any recomendations. We currently use Acronis
and is seems to work on all of our non-clustered servers.
I have not built a cluster since Server 2000 and I can tell you that this
time out with Server 2003 R2 and Sql 2005 it was much better.
Regards, emagidson
Comments Inline
"EMagidson" <EMagidson@.discussions.microsoft.com> wrote in message
news:991EA41E-F915-4A6C-9379-7BB85BE8CC44@.microsoft.com...
> Ok my job is done. I have built a fully tested Windows and SQL
> active/passive
> cluster. Not the software guys take over but as an inquiring IT guy I
> can't
> call it done withoout some more education.
> Please feel free to answer these questions or send me to more information
> please.
> 1. I understand that the virtual clusters "CompanyCluster IP address
> x.x.x.x and SqlCluster IP Address x.x.x.x" are used to map databases and
> point to as the reference for websites, databases and apps. Do you perform
> any tasks on these virtual machines llike servicee packs or database
> installs
> and maintenance?
OS service packs are applied to physical machines. SQL Service packs and
hotfixes are applied to individual instances. The installer is
cluster-aware and updates all nodes at once. From the point of view of a
client connection, there is no difference between a clustered installation
and a non-clustered system.

> 1a. If you do not use the Virtual machines then I assume you use the
> active
> node. Would that install the database to the other node automatically?
Nodes are the physical layer. Instances are the virtual abstraction. They
are independent entities. An instance can move from one node to another in
order to stay online. An instance can exist on only a single node at a
time.

> 2. Where are the Virtual machines stored and should you back them up or
> are
> they just basically cached on the active node?
SQL Data is stored on the cluster disks. The cluster configuration is
stored in teh cluster registry, an abstraction that is managed by the
cluster service on each node.

> 3. How about backup software any recomendations. We currently use Acronis
> and is seems to work on all of our non-clustered servers.
Personally, I backup the SQL servers just as I would a stand-alone system.
I do a compressed backup to disk and archive that to tape. I don't really
worry about backups. I worry about restores. Nobody got fired or rewarded
for a backup. Many folks have had that happen because they either could or
could not restore the system. One final note on restores. Test them. An
untested recoery plan is merely a recovery hope.

> I have not built a cluster since Server 2000 and I can tell you that this
> time out with Server 2003 R2 and Sql 2005 it was much better.
>
Yes, it is. That is one of the things the Server and SQL teams got right.

> Regards, emagidson
>
Good luck,
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP

Basic SQL Cluster Question

I am fairly new to administering SQL Server in a cluster environment,
I was kinda confused this morning when I was reading a post where a
individual installed SP2 for SQL 2005 on both the noeds of the
cluster. My understanding was you install the SP2 in just one node and
the cluster service takes care of it. Am I wrong? Do we really need to
install it in both the nodes?
Thanksshub wrote:
> I am fairly new to administering SQL Server in a cluster environment,
> I was kinda confused this morning when I was reading a post where a
> individual installed SP2 for SQL 2005 on both the noeds of the
> cluster. My understanding was you install the SP2 in just one node and
> the cluster service takes care of it. Am I wrong? Do we really need to
> install it in both the nodes?
> Thanks
>
actualy, SP2 instalation does it on other node(s) automaticaly, it just
asks you for a administrator login/password on the other node(s).
Finaly, sp2 instalation asks you for the restart of the node you're
running it on and reminds you to restart other node(s) manualy|||It depends on what you are patching. Some components are cluster-aware and
update all nodes. Some components require updating on each node
individually.
This blog post covers what goes where.
http://weblogs.sqlteam.com/geoffh/archive/2007/10/04/To-Cluster-or-Not-to-Cluster-That-SSIS-the-Question.aspx
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"shub" <shubtech@.gmail.com> wrote in message
news:1193403686.136330.93900@.o3g2000hsb.googlegroups.com...
>I am fairly new to administering SQL Server in a cluster environment,
> I was kinda confused this morning when I was reading a post where a
> individual installed SP2 for SQL 2005 on both the noeds of the
> cluster. My understanding was you install the SP2 in just one node and
> the cluster service takes care of it. Am I wrong? Do we really need to
> install it in both the nodes?
> Thanks
>

Basic SQL Cluster Question

I am fairly new to administering SQL Server in a cluster environment,
I was kinda confused this morning when I was reading a post where a
individual installed SP2 for SQL 2005 on both the noeds of the
cluster. My understanding was you install the SP2 in just one node and
the cluster service takes care of it. Am I wrong? Do we really need to
install it in both the nodes?
ThanksHi
You would not need to do this normally, you would need to post a link and
give more information.
John
"shub" wrote:
> I am fairly new to administering SQL Server in a cluster environment,
> I was kinda confused this morning when I was reading a post where a
> individual installed SP2 for SQL 2005 on both the noeds of the
> cluster. My understanding was you install the SP2 in just one node and
> the cluster service takes care of it. Am I wrong? Do we really need to
> install it in both the nodes?
> Thanks
>