Hi.
There is a bug with BPA.
When you configure a server with sp_configure 'user options',512 or EM
(default connection options) seting to NOCOUNT ON, BPA fails when reading
the catalog.
Esio
Thanks Esio for reporting this issue.
We shall work on fixing this issue in future release of BPA
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.
"Esio Nunes" <esio_nunes@.hotmail.com> wrote in message
news:%239d5MqL%23EHA.3988@.TK2MSFTNGP11.phx.gbl...
> Hi.
> There is a bug with BPA.
> When you configure a server with sp_configure 'user options',512 or EM
> (default connection options) seting to NOCOUNT ON, BPA fails when reading
> the catalog.
> Esio
>
Showing posts with label analyzer. Show all posts
Showing posts with label analyzer. Show all posts
Wednesday, March 28, 2012
PROBLEM WITH bcp
Hello!!
I have a problem with bcp in Query Analyzer.
The sentence is:
bcp SELECT id_categoria from categorias QUERYOUT 'c:\salida.txt' -c
-Ulogin -Ppassword
With this sentence, the error is:
Line 1: Incorrect syntax near 'c:\SADD.txt'.
PLEASE, I NEED HELP.
THANKSthis command works fine..
bcp "SELECT * from pubs..authors" QUERYOUT "C:\salida.txt" -c -S<server name> -Usa -P<password>
database name, server name and quotes around the query are missing from ur BCP command also the file path should be in full.|||hmmm, doesn't work for me, has a problem around QUERYOUT
strange.
i'll keep looking|||This is true!!, the error now is:
Line 1: Incorrect syntax near 'queryout'.
bcp "SELECT id_categoria from categorias" queryout "C:\salida.txt" -c -S<server_name> -U<login_id> -P<password>|||It works via the OS command line.|||master..xp_cmdshell 'bcp "SELECT * from pubs..authors" QUERYOUT "C:\salida.txt" -c -S<server name> -Usa -P<password>'sql
I have a problem with bcp in Query Analyzer.
The sentence is:
bcp SELECT id_categoria from categorias QUERYOUT 'c:\salida.txt' -c
-Ulogin -Ppassword
With this sentence, the error is:
Line 1: Incorrect syntax near 'c:\SADD.txt'.
PLEASE, I NEED HELP.
THANKSthis command works fine..
bcp "SELECT * from pubs..authors" QUERYOUT "C:\salida.txt" -c -S<server name> -Usa -P<password>
database name, server name and quotes around the query are missing from ur BCP command also the file path should be in full.|||hmmm, doesn't work for me, has a problem around QUERYOUT
strange.
i'll keep looking|||This is true!!, the error now is:
Line 1: Incorrect syntax near 'queryout'.
bcp "SELECT id_categoria from categorias" queryout "C:\salida.txt" -c -S<server_name> -U<login_id> -P<password>|||It works via the OS command line.|||master..xp_cmdshell 'bcp "SELECT * from pubs..authors" QUERYOUT "C:\salida.txt" -c -S<server name> -Usa -P<password>'sql
Saturday, February 25, 2012
Problem using DTSRUN in stored procedure / query analyzer
Hi. I am having a problem using DTSRun in a stored procedure or in query analyzer.
My DTS package truncates a table and then imports data from an Excel spreadsheet into the table.
The DTS package runs fine if I run it manually on Enterprise Manager or if I use DTSRun in a command prompt.
However when I try to run the package in a stored procedure or in query analyzer as follows:
ie Exec master..xp_cmdshell 'DTSRUN /SSQL SERVER /NPackageName /Uuserid /Ppassword'
The package does not return an error but it does not actually import any data from the Excel spreadsheet. It is able to truncate the table without any problem.
I've tried all kinds of combination of using Windows user id that I know has access to the excel file instead of a sql login.
I've run Filemon on the excel file and it seems like DTS is not accessing the file when I use the stored proc or query analyzer method.
If anyone could shed any light on this I would be most grateful. Thanks.The DTS package runs fine if I run it manually on Enterprise Manager or if I use DTSRun in a command prompt.
However when I try to run the package in a stored procedure or in query analyzer as follows:
ie Exec master..xp_cmdshell 'DTSRUN /SSQL SERVER /NPackageName /Uuserid /Ppassword'
When you run the package manually, are you running it from your machine (do you have EM running on your machine and connected to the SQL Server)or are you logged on to the server directly?
DTS looks for the file in the path of the machine it is running on ... so if the spreadsheet exists on your machine but not the server it will execute with success when run from your machine, but not by the SQL Agent on the server.|||Setup DTS logging and find out what is exaclty going on..|||When you run the package manually, are you running it from your machine (do you have EM running on your machine and connected to the SQL Server)or are you logged on to the server directly?
DTS looks for the file in the path of the machine it is running on ... so if the spreadsheet exists on your machine but not the server it will execute with success when run from your machine, but not by the SQL Agent on the server.
Hi. I have successfully run the package on Enterprise Manager on my machine and using DTSRun on a command prompt on my machine. The DTS package is pointing to the excel file with a full UNC pathname.
I've enabled DTS package logging and it does not return an error. The error code for the DataPump task is 0 even though it did not import any rows.|||Next place to check ... does the SQL Agent service login have permissions to the file share where the spreadsheet resides?
My DTS package truncates a table and then imports data from an Excel spreadsheet into the table.
The DTS package runs fine if I run it manually on Enterprise Manager or if I use DTSRun in a command prompt.
However when I try to run the package in a stored procedure or in query analyzer as follows:
ie Exec master..xp_cmdshell 'DTSRUN /SSQL SERVER /NPackageName /Uuserid /Ppassword'
The package does not return an error but it does not actually import any data from the Excel spreadsheet. It is able to truncate the table without any problem.
I've tried all kinds of combination of using Windows user id that I know has access to the excel file instead of a sql login.
I've run Filemon on the excel file and it seems like DTS is not accessing the file when I use the stored proc or query analyzer method.
If anyone could shed any light on this I would be most grateful. Thanks.The DTS package runs fine if I run it manually on Enterprise Manager or if I use DTSRun in a command prompt.
However when I try to run the package in a stored procedure or in query analyzer as follows:
ie Exec master..xp_cmdshell 'DTSRUN /SSQL SERVER /NPackageName /Uuserid /Ppassword'
When you run the package manually, are you running it from your machine (do you have EM running on your machine and connected to the SQL Server)or are you logged on to the server directly?
DTS looks for the file in the path of the machine it is running on ... so if the spreadsheet exists on your machine but not the server it will execute with success when run from your machine, but not by the SQL Agent on the server.|||Setup DTS logging and find out what is exaclty going on..|||When you run the package manually, are you running it from your machine (do you have EM running on your machine and connected to the SQL Server)or are you logged on to the server directly?
DTS looks for the file in the path of the machine it is running on ... so if the spreadsheet exists on your machine but not the server it will execute with success when run from your machine, but not by the SQL Agent on the server.
Hi. I have successfully run the package on Enterprise Manager on my machine and using DTSRun on a command prompt on my machine. The DTS package is pointing to the excel file with a full UNC pathname.
I've enabled DTS package logging and it does not return an error. The error code for the DataPump task is 0 even though it did not import any rows.|||Next place to check ... does the SQL Agent service login have permissions to the file share where the spreadsheet resides?
Subscribe to:
Posts (Atom)