Bcp.exe on client machine

Hi,
We use BCP.EXE to bulk upload to SQL Server. However, some of our clients
use SQL Server while others use MSDE.
We need to have BCP.EXE available on each client machine.
In case of a MSDE server does this mean that each client machine needs the
full MSDE installed just to get bcp.exe?
In case of the full SQL Server server does this mean that each client
machine needs a client tool like Query Analyzer installed just to get
bcp.exe?
Can I run SQLREDIS.EXE on a client machine instead and then just copy the
BCP.EXE and BCP.RLL files from the server machine instead? I read the
licenses but it is still unclear to me if this is allowed.
I've Googled to try find a solution but things are still as clear as mud.
Thanks in advance for any help,
Jako GroblerJako Grobler wrote:
> Hi,
> We use BCP.EXE to bulk upload to SQL Server. However, some of our
> clients use SQL Server while others use MSDE.
> We need to have BCP.EXE available on each client machine.
> In case of a MSDE server does this mean that each client machine
> needs the full MSDE installed just to get bcp.exe?
> In case of the full SQL Server server does this mean that each client
> machine needs a client tool like Query Analyzer installed just to get
> bcp.exe?
> Can I run SQLREDIS.EXE on a client machine instead and then just copy
> the BCP.EXE and BCP.RLL files from the server machine instead? I read
> the licenses but it is still unclear to me if this is allowed.
> I've Googled to try find a solution but things are still as clear as
> mud.
> Thanks in advance for any help,
> Jako Grobler
I'd just install the client utilities on every client machine (unless it's
a server at the same time). Disk space is cheap and this is definitely
the most hassle free solution - apart from licensing maybe.
Kind regards
robert|||"Robert Klemme" <bob.news@.gmx.net> wrote in
news:ONhaOCncFHA.3120@.TK2MSFTNGP12.phx.gbl:

> I'd just install the client utilities on every client machine (unless
> it's a server at the same time). Disk space is cheap and this is
> definitely the most hassle free solution - apart from licensing maybe.
> Kind regards
> robert
The problem is that the client utilities option is not available with MSDE.
Also, some companies are not happy installing Query Analyzer or Enterprise
Manager on client machines.
SQLREDIS.EXE does not install BCP.EXE, I tried it already.
:-(
Jako|||Jako Grobler wrote:
> "Robert Klemme" <bob.news@.gmx.net> wrote in
> news:ONhaOCncFHA.3120@.TK2MSFTNGP12.phx.gbl:
>
> The problem is that the client utilities option is not available with
> MSDE.
You can simply use SQL Server client utilities. They should happily
connect to an MSDE instance.

> Also, some companies are not happy installing Query Analyzer or
> Enterprise Manager on client machines.
Well then...

> SQLREDIS.EXE does not install BCP.EXE, I tried it already.
> :-(
> Jako
Kind regards
robert

Bcp.exe on client machine

Hi,
We use BCP.EXE to bulk upload to SQL Server. However, some of our clients
use SQL Server while others use MSDE.
We need to have BCP.EXE available on each client machine.
In case of a MSDE server does this mean that each client machine needs the
full MSDE installed just to get bcp.exe?
In case of the full SQL Server server does this mean that each client
machine needs a client tool like Query Analyzer installed just to get
bcp.exe?
Can I run SQLREDIS.EXE on a client machine instead and then just copy the
BCP.EXE and BCP.RLL files from the server machine instead? I read the
licenses but it is still unclear to me if this is allowed.
I've Googled to try find a solution but things are still as clear as mud.
Thanks in advance for any help,
Jako Grobler
Jako Grobler wrote:
> Hi,
> We use BCP.EXE to bulk upload to SQL Server. However, some of our
> clients use SQL Server while others use MSDE.
> We need to have BCP.EXE available on each client machine.
> In case of a MSDE server does this mean that each client machine
> needs the full MSDE installed just to get bcp.exe?
> In case of the full SQL Server server does this mean that each client
> machine needs a client tool like Query Analyzer installed just to get
> bcp.exe?
> Can I run SQLREDIS.EXE on a client machine instead and then just copy
> the BCP.EXE and BCP.RLL files from the server machine instead? I read
> the licenses but it is still unclear to me if this is allowed.
> I've Googled to try find a solution but things are still as clear as
> mud.
> Thanks in advance for any help,
> Jako Grobler
I'd just install the client utilities on every client machine (unless it's
a server at the same time). Disk space is cheap and this is definitely
the most hassle free solution - apart from licensing maybe.
Kind regards
robert
|||"Robert Klemme" <bob.news@.gmx.net> wrote in
news:ONhaOCncFHA.3120@.TK2MSFTNGP12.phx.gbl:

> I'd just install the client utilities on every client machine (unless
> it's a server at the same time). Disk space is cheap and this is
> definitely the most hassle free solution - apart from licensing maybe.
> Kind regards
> robert
The problem is that the client utilities option is not available with MSDE.
Also, some companies are not happy installing Query Analyzer or Enterprise
Manager on client machines.
SQLREDIS.EXE does not install BCP.EXE, I tried it already.
:-(
Jako
|||Jako Grobler wrote:
> "Robert Klemme" <bob.news@.gmx.net> wrote in
> news:ONhaOCncFHA.3120@.TK2MSFTNGP12.phx.gbl:
>
> The problem is that the client utilities option is not available with
> MSDE.
You can simply use SQL Server client utilities. They should happily
connect to an MSDE instance.

> Also, some companies are not happy installing Query Analyzer or
> Enterprise Manager on client machines.
Well then...

> SQLREDIS.EXE does not install BCP.EXE, I tried it already.
> :-(
> Jako
Kind regards
robert

Bcp.exe on client machine

Hi,
We use BCP.EXE to bulk upload to SQL Server. However, some of our clients
use SQL Server while others use MSDE.
We need to have BCP.EXE available on each client machine.
In case of a MSDE server does this mean that each client machine needs the
full MSDE installed just to get bcp.exe?
In case of the full SQL Server server does this mean that each client
machine needs a client tool like Query Analyzer installed just to get
bcp.exe?
Can I run SQLREDIS.EXE on a client machine instead and then just copy the
BCP.EXE and BCP.RLL files from the server machine instead? I read the
licenses but it is still unclear to me if this is allowed.
I've Googled to try find a solution but things are still as clear as mud.
Thanks in advance for any help,
Jako GroblerJako Grobler wrote:
> Hi,
> We use BCP.EXE to bulk upload to SQL Server. However, some of our
> clients use SQL Server while others use MSDE.
> We need to have BCP.EXE available on each client machine.
> In case of a MSDE server does this mean that each client machine
> needs the full MSDE installed just to get bcp.exe?
> In case of the full SQL Server server does this mean that each client
> machine needs a client tool like Query Analyzer installed just to get
> bcp.exe?
> Can I run SQLREDIS.EXE on a client machine instead and then just copy
> the BCP.EXE and BCP.RLL files from the server machine instead? I read
> the licenses but it is still unclear to me if this is allowed.
> I've Googled to try find a solution but things are still as clear as
> mud.
> Thanks in advance for any help,
> Jako Grobler
I'd just install the client utilities on every client machine (unless it's
a server at the same time). Disk space is cheap and this is definitely
the most hassle free solution - apart from licensing maybe.
Kind regards
robert|||"Robert Klemme" <bob.news@.gmx.net> wrote in
news:ONhaOCncFHA.3120@.TK2MSFTNGP12.phx.gbl:
> I'd just install the client utilities on every client machine (unless
> it's a server at the same time). Disk space is cheap and this is
> definitely the most hassle free solution - apart from licensing maybe.
> Kind regards
> robert
The problem is that the client utilities option is not available with MSDE.
Also, some companies are not happy installing Query Analyzer or Enterprise
Manager on client machines.
SQLREDIS.EXE does not install BCP.EXE, I tried it already.
:-(
Jako|||Jako Grobler wrote:
> "Robert Klemme" <bob.news@.gmx.net> wrote in
> news:ONhaOCncFHA.3120@.TK2MSFTNGP12.phx.gbl:
>> I'd just install the client utilities on every client machine (unless
>> it's a server at the same time). Disk space is cheap and this is
>> definitely the most hassle free solution - apart from licensing
>> maybe.
>> Kind regards
>> robert
> The problem is that the client utilities option is not available with
> MSDE.
You can simply use SQL Server client utilities. They should happily
connect to an MSDE instance.
> Also, some companies are not happy installing Query Analyzer or
> Enterprise Manager on client machines.
Well then...
> SQLREDIS.EXE does not install BCP.EXE, I tried it already.
> :-(
> Jako
Kind regards
robert

bcp.exe connects to go.microsoft.com?

Hi!
We're using MSDE 1.0 and one customer informed us, that his Sygate
personal firewall spit out the following message:
bcp.exe is trying to connect to go.microsoft.com [207.46.197.43] using
port 80.
the exe's path is the path that we'd expect and bcp still does it's job,
namely saving the databases to files; so I doubt that it is a hijacked
version; but we'll have to double check that.
Can anyone explain why bcp would want to connect to a website?
Thanks,
Stefan
Check your event log. For many Microsoft Products, events that have errors
can connect to or provide a link to go.microsoft.com ... if you have error
reporting enabled that might be where the error goes...
I see this in my event log for various auditing events and errors:
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
http://www.aspfaq.com/
(Reverse address to reply.)
"Stefan M. Huber" <looseleaf@.gmx.net> wrote in message
news:opsb7imbzss9ddfw@.news.individual.de...
> Hi!
> We're using MSDE 1.0 and one customer informed us, that his Sygate
> personal firewall spit out the following message:
> bcp.exe is trying to connect to go.microsoft.com [207.46.197.43] using
> port 80.
> the exe's path is the path that we'd expect and bcp still does it's job,
> namely saving the databases to files; so I doubt that it is a hijacked
> version; but we'll have to double check that.
> Can anyone explain why bcp would want to connect to a website?
> Thanks,
> Stefan
|||On Wed, 4 Aug 2004 09:43:42 -0400, Aaron [SQL Server MVP]
<ten.xoc@.dnartreb.noraa> wrote:

> Check your event log. For many Microsoft Products, events that have
> errors
> can connect to or provide a link to go.microsoft.com ... if you have
> error
> reporting enabled that might be where the error goes...
Oh thank you. That is a very good hint.
Stefan
Pink Floyd of Borg: We don't need no assimilation!