Showing posts with label driver. Show all posts
Showing posts with label driver. Show all posts

Wednesday, March 7, 2012

error 37000

I tried to run my application linked to sqlserver DB. Iobtain this message :
Erreur d'exécution 40002
37000 : [Microsoft][ODBC SQL Server Driver] [SQL Server] the log file for
database "app" si full. Back up the transaction log for the database to free
up some log space
someboy could tell me it there is a possibility to do not write in log file ?
this transaction log is always active ?
thanks
tft
Hi,
Backup the Transaction log (See BACKUP LOG command in books online) and try
accessing the database. If you do not requite a
transaction log backup then change the recovery model for your database to
'SIMPLE'. After that truncate the transaction log using
BACKUP LOG <DBNAME> WITH TRUNCATE_ONLY
The above strategies will clear your trasnaction log.
Thanks
Hari
SQL Server MVP
"ft" <ft@.discussions.microsoft.com> wrote in message
news:19A68E4F-3C6A-4502-AE07-B4C8C9DBFBA3@.microsoft.com...
>I tried to run my application linked to sqlserver DB. Iobtain this message
>:
> Erreur d'excution 40002
> 37000 : [Microsoft][ODBC SQL Server Driver] [SQL Server] the log file for
> database "app" si full. Back up the transaction log for the database to
> free
> up some log space
> someboy could tell me it there is a possibility to do not write in log
> file ?
> this transaction log is always active ?
> thanks
> tft

Sunday, February 26, 2012

error 3520 on sql insert statement from a text file (only happens in 1 location)

I have a program that uses the Microsoft ODBC text driver Driver={Microsoft Text Driver (*.txt; *.csv)} this is used to make a connection to the database and then execute an sql insert to insert data from a flat file into an access database. The code works at hundreds of locations but for some reason it does not work at 1. I have ran an sql trace and found the error 3520 which would mean the data in the text file does not match the table that it is being inserted into but I have checked that and have tried using the same data on my computer and it works fine. I have also ran mdac compenent checker and there are no mismatched files. Any ideas on how to correct this or if anyone else has ever even seen this please help...Moving thread to Data Access Forum.

Friday, February 17, 2012

Error -2147217887

I get following error when I start SQL PROFILER to trace
my query.
Platform detail
Windows 98
SQL 2000
error 2147217887 - ODBC driver does not support the
requested properties
Please suggestHi Nishant
There maybe problem with your MDAC. I suggest to apply latest MDAC on the
machine where you try to launch SQL profiler.
Sincerely,
Yih-Yoon Lee [Microsoft]
Microsoft SQL Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.