Dbf To Ms Sql Server 2000

:eek: HI ALL
I m having my data in DBF file format. now i want to use my .Dbf files Data in to SQL Server 2000. so i can use SQL query on that and extract data from that. i want to use my DBF data in SQL. tell me how it is possible. plz give me soloution ...
Thanx
Manu VermaDo you still have a database server that will read the dbf files? If so, you can connect to it from SQL Server using DTS and import the data.|||Do you still have a database server that will read the dbf files? If so, you can connect to it from SQL Server using DTS and import the data.

we can read DBF files even in Excel or in VFoxpro. tell me the way to Import the data. i tried in SQL Server 2000. I select the Visual Foxpro ODBC Driver it gave the error. How can i import data via using DTS?|||we can read DBF files even in Excel or in VFoxpro. tell me the way to Import the data. i tried in SQL Server 2000. I select the Visual Foxpro ODBC Driver it gave the error. How can i import data via using DTS?

Follow this...
Open EM>Right click on Database>All Tasks>Import data>Select Microsoft Visual Foxpro Driver as data source>Select User/SystemDSN>New>System data source>Visual foxpro driver>Give data source name>Browse the database>Select the created DSN> and you are through...:cool:|||I select the Visual Foxpro ODBC Driver it gave the error.The error? Believe it or not, there are actually several errors you can get. Care to post the message you received?|||Hi,

You might need to download the latest drivers for Foxpro/Dbf.
Thanks

RN|||When i import the data from Foxpro .dbf file to sql, there is error:

Insert error, Column 47 ('mrlvbd',DBType_DBTimeStamp),status 6: Data Overflow.

Then i found out that it might be because of the date field of the data is blank. What can i do to solve this?

Thanks in advance|||I have found the solution.

1 ) In the Select Source Dialog Box,select the Transform Button.

2) Change the Destination Datatype of the related field from SmallDateTime to DateTime

Thanks

DBF to be attached in sqlserver2000/2005

Hi, Everybody

Please tell me the detailed procedure for having a *.DBF file attached to sqlserver 2000 or 2005.

I just want this file which is of visualfoxpro - DBF to be in sqlserver...........

thanks and regards,

Vishwanath.

Hey,

I don't believe SQL can import new database structures. You may, through DTS/SSIS, be able to copy the structure/data over, and that would create a SQL-compliant structure, depending on what was in the tables. I thought foxpro was more of an object-oriented database, which is not what SQL is...

|||

Hi Vishu

A lot depends on what you mean by "attached." You can use a linked server to access Fox data in SQL Server. You will need the FoxPro and Visual FoxPro OLE DB data provider, downloadable from a link at http://msdn2.microsoft.com/en-us/vfoxpro/bb190232.aspx . If you have a DBC (Database Container) in the directory where the Fox tables are then point your connection string to it. Otherwise, use the "Free Table" option and just point the connection string to the directory where the DBFs are. When you select data from the linked server use code like Select MyField From MyLinkedServer...MyTableName without using ".dbf" on the end of the table name.

|||

Hi!

Visual FoxPro is both an ODBC/OLE DB compliant database and a fully object-oriented development tool. In addition to using DBFs (Fox tables) as the data store you can use an Access MDB or SQL Server. In either the case of SQL Server it would be used as a front end in the same way as VB or C#.

dbf in network location

I tried to connect my *.mdf (using path like this: \\Server\infotec.mdf) file to MSSQL EXpress 2005 engine using MSS Management Studio Express but I get message that attaching databases from network paths is impossible. Is there any possibility to do this?

thx, Tom

Attaching database files in a network location is not recommended. The reason being that SQL Server needs exclusive access to the files, and also needs to ensure that reads and writes are of sufficient speed. The reads and writes also need to follow guaranteed sequence. Very few network devices can satisfy these requirements.

Here's an article that describes the issue in great detail: http://support.microsoft.com/kb/304261/en-us