Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

stored procedure that runs a bcp with xp_cmdshell hangs

Posted on 2004-04-29
6
Medium Priority
?
2,166 Views
Last Modified: 2007-12-19
Hi experts,

I have a procedure that writes a file
(@path defines where bcp.exe is and the directory where the output file will be located.
......

set @sql = @path + '\bcp "SELECT ltrim(Data1) FROM ' + @db_name + '..CTS_SendFile (nolock) " queryout "' + @path + '\CTSABO.TXT" -c -CACP -S' + @servername + ' -U' + @user + ' -P' + @pwd
exec @resp2 = master..xp_cmdshell @sql, no_output

......

it's hanging but It works when I don't consider the path for bcp.exe:

set @sql = 'bcp "SELECT ltrim(Data1) FROM ' + @db_name + '..CTS_SendFile (nolock) " queryout "' + @path + '\CTSABO.TXT" -c -CACP -S' + @servername + ' -U' + @user + ' -P' + @pwd
exec @resp2 = master..xp_cmdshell @sql, no_output

I'm considering to trust that bcp.exe is defined in PATH, but I'd like to know what's causing the problem.

Thanks
Carlos V.
0
Comment
Question by:cvillacr
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
6 Comments
 
LVL 6

Expert Comment

by:robertjbarker
ID: 10956441
To debug this I would put a print statement right after the "set @sql" statement:

print @sql

I would run my code in Query Analyzer to just past the  print statement.  Then I would cut the result from the Message panel and paste it into a command box to see what happens.
0
 
LVL 11

Expert Comment

by:rdrunner
ID: 10956976
Wild guess....

@Path ends with a '\'
0
 
LVL 26

Accepted Solution

by:
Hilaire earned 750 total points
ID: 10957437
Did you make a copy of the bcp utility to another @path folder ?

BCP.exe is intended to run in the
MS SQL Server/version/tools/binn folder
It's expecting some required dlls to be present in the same directory

When you run bcp from any location, it uses the bcp.exe that is in hte %PATH% env variable.

If you make a copy in c:\temp and run it from there, it will fail saying missing dll

HTH

Hilaire
0
Learn how to optimize MySQL for your business need

With the increasing importance of apps & networks in both business & personal interconnections, perfor. has become one of the key metrics of successful communication. This ebook is a hands-on business-case-driven guide to understanding MySQL query parameter tuning & database perf

 
LVL 26

Expert Comment

by:Hilaire
ID: 10957507
When you run the bcp utility from within the xp_cmdshell system proc, it runs on the server.
You can definitely assume that the server has a correct path.

You can also use a fully qualified path to the bcp utility ON THE SERVER, this should make no harm.
Again, this path is most likely different from the path you used to test the bcp command on your local machine.
You must use the bcp utility in the default folder, not a copy in a another folder (this makes the command hang)

Hilaire
0
 

Author Comment

by:cvillacr
ID: 10967877
Hi Hilaire, robertjbarker

The SP was tested, all the variables are well assigned. You're right Hilaire, I copied the bcp.exe to specific directory. The problem is that the software is working ok in the production environment, when I copied everything to my PC I have this problem. I think the solution will be to trust in the path of sql server. But any cause the SP is working ok in production with the bcp.exe copied in a specific path?

I tried copying all .dll from \bin  to the specific directory and bcp.exe is hanging again...

Thanks
Carlos V.
0
 
LVL 26

Expert Comment

by:Hilaire
ID: 10975427
>>I think the solution will be to trust in the path of sql server<<
Definitely

>>But any cause the SP is working ok in production with the bcp.exe copied in a specific path?<<
I guess you have more services loaded on the production server than on your PC. (SQL server agent for DTS jobs and backups, ...)
Chances are that when bcp is called on the server, the required dlls are already loaded in memory so SQL Server doesn't have to search them in the local directory.

BTW I think it's better to stick to default paths defined on the server, thus you have nothing to hard-code for the paths, and no dlls to copy if you make a server upgrade

Cheers

Hilaire
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In the first part of this tutorial we will cover the prerequisites for installing SQL Server vNext on Linux.
An alternative to the "For XML" way of pivoting and concatenating result sets into strings, and an easy introduction to "common table expressions" (CTEs). Being someone who is always looking for alternatives to "work your data", I came across this …
Familiarize people with the process of retrieving data from SQL Server using an Access pass-thru query. Microsoft Access is a very powerful client/server development tool. One of the ways that you can retrieve data from a SQL Server is by using a pa…
Using examples as well as descriptions, and references to Books Online, show the different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed

715 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question