Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
arisethephoenix
Starting Member
3 Posts |
 Posted - 2008-11-24 : 17:32:54
|
| OK, n00b question here, but I'm pulling my hair out so here I am asking the pros :)I have a single file that I >think< is in .db2 format (it's a Kewill Clippership archive file and that's what the tech told me). If I open it with Excel, it's smart enough to figure out all the columns and data, but if I open with Notepad it appears somewhat readable but definitely not comma or tab delimited, etc.I would like to be able to import the data into a SQL 2005 data table. What are my >>>simplest<<< options?Please assume I only know about using the Import Data task for importing data from .csv files and do not have Integration Services readily available...Thanks in advance,Rob |
|
|
arisethephoenix
Starting Member
3 Posts |
Posted - 2008-11-26 : 10:53:34
|
| OK, I now have an SSIS package that can import the data via the Microsft Dbase ODBC driver (tip: always make sure your files follow the 8.3 format (using .dbf as the extension for compatibility with MS DBase ODBC driver and when you do a SELECT, the filename is the table name - i.e. if your flat file is mydb.dbf then SELECT * FROM MYDB or some variant should be used).Now the only trouble I'm having is running the package after I've saved it in SSIS. It runs fine when I first make the package and when I execute it manually from the GUI, but it fails when attempting to schedule it in a job. Here's a link with the error I'm getting and a suggested solution, however I cannot figure out how to get to the option he is suggesting to change (which makes sense sorta):[url]http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=4139856&SiteID=1[/url]Could someone please point me in the right direction? Hopefully this is a little easier to answer than my original post...Thanks in advance!Rob |
 |
|
|
arisethephoenix
Starting Member
3 Posts |
Posted - 2008-11-26 : 15:18:11
|
| Well, figured this one out myself too - so this is an FYI, hopefully it will help someone in the future...When you install SQL server on a 64 bit platform, the dtexec tool gets copied into both the Program Files and Program Files (x86) directory (just search for dtexec.exe for full path). So, you have to create a job that does a "Operating System (CmdExec)" Step instead of running the package "normally" via "SQL Server Integration Services Package". Include the full path and the subsequent switches for dtexec as so (where "csconn" is my SSIS package name and "cactus" is my server name):"c:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DTExec.exe" /sql csconn /ser cactusNote the position of the double quotes - very important...Providing your package runs OK from the GUI it should run just fine if you set it up this way. You do not need to do anything fancy for ODBC connections (except as stated above) and don't need to alter the 64bit debugging setup per the above link.Good luck!Rob |
|
|
|
|
|
|
|
|
Import to SQL table from .db2 file