显示标签为“nativeerror”的博文。显示所有博文
显示标签为“nativeerror”的博文。显示所有博文

2012年3月22日星期四

BCP Problem with SQL Server 2000

Ive encountered the following problem when trying to bcp out data
from a table with text columns :
Starting copy...
SQLState = S1001, NativeError = 0
Error = [Microsoft][ODBC SQL Server Driver]Memory allocation failure
Ive no idea on whats going on with it :cry:
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/Server-BCP-P...ict245539.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=852097
terry_aibo,
Try increasing the size of the windows page file. Also, allow SQL Server
to take as much memory on the machine as possible, something like
(TotalRam-200MB). Try and switch off any unnecessary services, and quit
any running applications except SQL Server. Try and make the machine a
"pure" dedicated SQL Server. Ensure you have the latest service pack.
If this fails to cure it, I would raise a call with Microsoft, this
error is quite rare.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
terry_aibo wrote:
> Ive encountered the following problem when trying to bcp out data
> from a table with text columns :
> Starting copy...
> SQLState = S1001, NativeError = 0
> Error = [Microsoft][ODBC SQL Server Driver]Memory allocation failure
>
> Ive no idea on whats going on with it :cry:
>
发帖者 Rema 时间： 17:40 0 评论
标签： , , , , , , , , , , , , , , , , ,

BCP Problem with SQL Server 2000

Ive encountered the following problem when trying to bcp out data
from a table with text columns :
Starting copy...
SQLState = S1001, NativeError = 0
Error = [Microsoft][ODBC SQL Server Driver]Memory allocation failure
Ive no idea on whats going on with it :cry:
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/Server-BCP-...rm.php?p=852097terry_aibo,
Try increasing the size of the windows page file. Also, allow SQL Server
to take as much memory on the machine as possible, something like
(TotalRam-200MB). Try and switch off any unnecessary services, and quit
any running applications except SQL Server. Try and make the machine a
"pure" dedicated SQL Server. Ensure you have the latest service pack.
If this fails to cure it, I would raise a call with Microsoft, this
error is quite rare.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
terry_aibo wrote:
> Ive encountered the following problem when trying to bcp out data
> from a table with text columns :
> Starting copy...
> SQLState = S1001, NativeError = 0
> Error = [Microsoft][ODBC SQL Server Driver]Memory allocation failu
re
>
> Ive no idea on whats going on with it :cry:
>
发帖者 Rema 时间： 17:40 0 评论
标签： , , , , , , , , , , , , , , , , ,

2012年3月20日星期二

BCP Problem - Please Help !

When I try to bcp out data from a table with text columns, the
following error prompted :
Starting copy...
SQLState = S1001, NativeError = 0
Error = [Microsoft][ODBC SQL Server Driver]Memory allocation failure
Most grateful if anyone can provide help on it. :?
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/Tools-BCP-Pr...ict245835.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=853003
terry_aibo <UseLinkToEmail@.dbForumz.com> wrote:
> When I try to bcp out data from a table with text columns, the
> following error prompted :
>
> Starting copy...
> SQLState = S1001, NativeError = 0
> Error = [Microsoft][ODBC SQL Server Driver]Memory allocation failure
>
> Most grateful if anyone can provide help on it. :?
You need more (virtual) memory - either on the client or server host. The
simplest you can do is to increase the paging file size of the machine with
mem problems.
Kind regards
robert
发帖者 Rema 时间： 20:16 0 评论
标签： , , , , , , , , , , , , , , , , ,

BCP Problem

Hi,
I am trying to bulk copy a text file into a table and I get this error
message:
SQLState = 28000, NativeError = 18452
Error = [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'Test Login'. Reason: Not associated with a trusted SQL Server connection.
I am pretty sure that my username and password are correct because I just
created them 5 minutes before.
Any clues on how to get around this problem?
JDHi
It would help if you showed the command you where executing, but it seems
that you have specified the -T option possibly instead of -t (the arguements
are case sensitive!). See Books online for more information on the BCP
utility.
John
"Joe Delphi" <delphi561@.nospam.cox.net> wrote in message
news:Zi7Xe.253734$E95.165564@.fed1read01...
> Hi,
> I am trying to bulk copy a text file into a table and I get this error
> message:
> SQLState = 28000, NativeError = 18452
> Error = [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
> user
> 'Test Login'. Reason: Not associated with a trusted SQL Server connection.
> I am pretty sure that my username and password are correct because I just
> created them 5 minutes before.
> Any clues on how to get around this problem?
>
> JD
>
>|||Joe Delphi (delphi561@.nospam.cox.net) writes:
> I am trying to bulk copy a text file into a table and I get this error
> message:
> SQLState = 28000, NativeError = 18452
> Error = [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
> user'Test Login'. Reason: Not associated with a trusted SQL Server
> connection.
> I am pretty sure that my username and password are correct because I just
> created them 5 minutes before.
It appears that the SQL Server is not configured for SQL authentication,
but only accepts Windows authentication. To examine this right-click
the sercer in Enterprise Manager and select Properties. Then go the
Security tab.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Sorry, here is the command I am using. I am not using the -t or -T option.
bcp "[local].Compensation.tblOCImport" in "PAYOC.txt" -c -o"C:\2005\Raw
Extracts\OutputLog.txt" -U"Test Login" -P"TestPassword"
I changed the Server properties to use both Windows authentication and also
SQL Server authentication and now I get this error message:
SQLState = 37000, NativeError = 4060
Error = [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database
requested in login '[local]'. Login fails.
Like I said in my original post, I just created my login and password a few
minutes ago so I know they are correct. But I don't understand why I am
getting the error message.
JD
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:%238cosSCvFHA.664@.tk2msftngp13.phx.gbl...
> Hi
> It would help if you showed the command you where executing, but it seems
> that you have specified the -T option possibly instead of -t (the
arguements
> are case sensitive!). See Books online for more information on the BCP
> utility.
> John
> "Joe Delphi" <delphi561@.nospam.cox.net> wrote in message
> news:Zi7Xe.253734$E95.165564@.fed1read01...
connection.
just
>|||The qualified table name is specified the format: <database
name>.<schema>.<object>. The server name can be specified with the '-S' BCP
parameter.
It is unclear what your server and database names are. Assuming a database
named 'Compensation' in the 'dbo' schema on the local server:
bcp "Compensation.dbo.tblOCImport" in "PAYOC.txt" -c -o"C:\2005\Raw
Extracts\OutputLog.txt" -U"Test Login" -P"TestPassword" -S"(local)"
The -S parameter can be omitted for the local server. For a remote server:
bcp "Compensation.dbo.tblOCImport" in "PAYOC.txt" -c -o"C:\2005\Raw
Extracts\OutputLog.txt" -U"Test Login" -P"TestPassword" -S"MyServer"
Hope this helps.
Dan Guzman
SQL Server MVP
"Joe Delphi" <delphi561@.nospam.cox.net> wrote in message
news:ISfXe.253752$E95.85768@.fed1read01...
> Sorry, here is the command I am using. I am not using the -t or -T
> option.
> bcp "[local].Compensation.tblOCImport" in "PAYOC.txt" -c -o"C:\2005\Raw
> Extracts\OutputLog.txt" -U"Test Login" -P"TestPassword"
> I changed the Server properties to use both Windows authentication and
> also
> SQL Server authentication and now I get this error message:
> SQLState = 37000, NativeError = 4060
> Error = [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
> database
> requested in login '[local]'. Login fails.
> Like I said in my original post, I just created my login and password a
> few
> minutes ago so I know they are correct. But I don't understand why I am
> getting the error message.
> JD
>
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:%238cosSCvFHA.664@.tk2msftngp13.phx.gbl...
> arguements
> connection.
> just
>|||Joe Delphi (delphi561@.nospam.cox.net) writes:
> Sorry, here is the command I am using. I am not using the -t or -T
> option.
> bcp "[local].Compensation.tblOCImport" in "PAYOC.txt" -c -o"C:\2005\Raw
> Extracts\OutputLog.txt" -U"Test Login" -P"TestPassword"
> I changed the Server properties to use both Windows authentication and
> also SQL Server authentication and now I get this error message:
> SQLState = 37000, NativeError = 4060
> Error = [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
> database requested in login '[local]'. Login fails.
> Like I said in my original post, I just created my login and password a
> few minutes ago so I know they are correct. But I don't understand why
> I am getting the error message.
Did you also add the Test login as a user in the database? You get this
message if the user does not have access to the database. You also get it,
if the database does not exist at all.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
发帖者 Rema 时间： 20:12 0 评论
标签： , , , , , , , , , , , , , , ,

2012年3月8日星期四

BCP fails with 134 columns

I'm trying to BCP from a csv file to a table, both have 134 columns. The error message coming back from BCP "SQLState = 37000, NativeError = 170

Error = [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near '1'."

By reducing the number of columns in both csv file and table to around 20 column , the bcp call will work and the data will load into the table.Here's a sample that shows the problem

The command line I'm using to call bcp:-

"C:\Program Files\Microsoft SQL Server\80\Tools\Binn\bcp.exe" em.dbo.mytable1 in c:\temp\_rrs\datafile.csv -S SQL_SERVER_NAME -U username -P password -t "|" -c -F 2

The version of BCP this is using :- 8.00.194 on SQL Server 2000.

Sample data in datafile.csv

1|Position|BBPLC|20060927|ALL|RDPBB092701.DAT||ALL
1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1|1
2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2|2
3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3|3

Creation script for table


if exists (select * from dbo.sysobjects where id = object_id(N'[mytable1]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)
drop table [mytable1]
GO

CREATE TABLE [mytable1] (
[1][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[2][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[3][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[4][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[5][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
Devil[varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[7][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
Music[varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[9][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[10][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[11][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[12][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[13][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[14][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[15][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[16][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[17][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[18][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[19][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[20][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[21][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[22][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[23][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[24][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[25][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[26][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[27][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[28][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[29][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[30][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[31][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[32][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[33][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[34][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[35][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[36][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[37][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[38][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[39][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[40][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[41][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[42][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[43][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[44][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[45][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[46][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[47][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[48][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[49][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[50][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[51][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[52][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[53][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[54][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[55][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[56][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[57][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[58][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[59][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[60][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[61][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[62][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[63][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[64][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[65][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[66][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[67][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[68][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[69][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[70][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[71][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[72][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[73][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[74][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[75][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[76][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[77][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[78][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[79][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[80][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[81][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[82][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[83][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[84][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[85][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[86][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[87][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[88][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[89][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[90][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[91][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[92][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[93][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[94][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[95][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[96][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[97][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[98][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[99][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[100][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[101][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[102][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[103][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[104][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[105][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[106][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[107][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[108][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[109][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[110][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[111][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[112][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[113][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[114][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[115][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[116][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[117][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[118][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[119][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[120][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[121][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[122][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[123][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[124][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[125][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[126][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[127][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[128][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[129][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[130][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[131][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[132][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[133][varchar](6) COLLATE Latin1_General_CI_AS NULL ,
[134][varchar](6) COLLATE Latin1_General_CI_AS NULL
) ON [em_Group1]
GO

Any pointers on this would be very much appreciated

Regards

RichardS71


Eureka!

Whilst SQL Server allows you to create tables with column names that begin with a number, BCP version 8.00.XXX won't let you BCP to the table.

发帖者 Rema 时间： 17:55 0 评论
标签： , , , , , , , , , , , , , , , , ,
订阅： 博文 (Atom)