Export DDL in Export Wizard - Terminator

Hello,
I am using SQL Developer and looking for a way to change the statement terminator to '/'. By default it uses a semicolon.
I am exporting Object types tables and triggers.
while my table has
CREATE TABLE "SCHEMA"."CONTACT"
   (     "CONTACT_TYPE_ID" NUMBER(9,0),
     "VALUE" VARCHAR2(120 CHAR)
   ) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "SCHEMA_LARGE";semiconlon as terminator
my trigger has
CREATE OR REPLACE TRIGGER "BILLING_SCHEMA"."SUMMARY_DETAIL" BEFORE INSERT ON SCHEMA.SUMMARY_DETAIL FOR EACH ROW
BEGIN SELECT SCHEMA.SEQ_IMPORT_SUMMARY_DETAIL.NEXTVAL INTO :NEW.ID FROM DUAL; END;
/slash as the terminator because of an already existing semicolon in the trigger statement.
Could you please help me with a way to standardize the statement terminator to a slash.
Thanks in advance,
Marilyn
Edited by: user5417526 on 11/02/2013 16:43

Similar Messages

EA2 - Export Wizard - No forward slash after package spec and body in sql

I exported a schema with the export wizard. My stand alone functions and sql types in the script have have a forward slash after the "end;" statement Great. However, package specs and body create statements do not have a forward slash after the "end;" and I believe they also should have this.

This appears to be a DB issue as we are just using DBMS_METADATA to generate the ddl. Please test manually using worksheet or sqlplus
exec DBMS_METADATA.SET_TRANSFORM_PARAM( DBMS_METADATA.SESSION_TRANSFORM, 'SQLTERMINATOR' , TRUE );
select dbms_metadata.get_ddl('PACKAGE', 'PACKAGE_NAME','SCHEMA') from dual;
I looked through the DB bugs briefly and noticed a few on other objects that were fixed in 9.2.0.6 but I didn't see one for Packages...
This is not something I would fix in SQL Developer as the core issue is with DBMS_MEATADATA and your version of the DB.
As this is fixed in 10 I'm sure you can work with support and request a backport if it's not a currently available patch.

EA1: Export Wizard out of memory

Hi,
Wanted to move some data and tried to do it with the Export Wizard.
I only selected data as DDL option and 3 tables (1 has almost 2M rows) from the list of objects.
After about 20 sec. the export script appeared empty.
In the console I got this (silent) error:
Exception in thread "RunnerThread" java.lang.OutOfMemoryError: Java heap space
K.

Syme got this fixed up for the next push.
-kris

Error message when importing data using Import and export wizard

Getting below error message when importing data using IMPORT and EXPORT WIZARD
Error 0xc0202009: Data Flow Task 1: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
<dir>
<dir>
Messages
Error 0xc0202009: Data Flow Task 1: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Could not allocate a new page for database REPORTING' because of insufficient disk space in filegroup 'PRIMARY'.
Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.".
(SQL Server Import and Export Wizard)
Error 0xc0209029: Data Flow Task 1: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "Destination - Buyer_.Inputs[Destination Input]" failed because error code 0xC020907B occurred, and the error row disposition on "Destination
- Buyer_First_Qtr.Inputs[Destination Input]" specifies failure on error. An error occurred on the specified object of the specified component. There may be error messages posted before this with more information about the failure.
(SQL Server Import and Export Wizard)
Error 0xc0047022: Data Flow Task 1: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Destination - Buyer" (28) failed with error code 0xC0209029 while processing input "Destination Input" (41). The
identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information
about the failure.
(SQL Server Import and Export Wizard)
Error 0xc02020c4: Data Flow Task 1: The attempt to add a row to the Data Flow task buffer failed with error code 0xC0047020.
(SQL Server Import and Export Wizard)
</dir>
</dir>
Error 0xc0047038: Data Flow Task 1: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on Source - Buyer_First_Qtr returned error code 0xC02020C4. The component returned a failure code when the pipeline engine called PrimeOutput().
The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
(SQL Server Import and Export Wizard)
Smash126

Hi Smash126,
Based on the error message” Could not allocate a new page for database REPORTING' because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting
autogrowth on for existing files in the filegroup”, we can know that the issue is caused by the there is no sufficient disk space in filegroup 'PRIMARY' for the ‘REPORTING’ database.
To fix this issue, we can add additional files to the filegroup by add a new file to the PRIMARY filegroup on Files page, or setting Autogrowth on for existing files in the filegroup to increase the necessary space.
The following document about Add Data or Log Files to a Database is for your reference:
http://msdn.microsoft.com/en-us/library/ms189253.aspx
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Attunity connectors for Oracle in Import Export Wizard in SQL Server 2008 R2

Is there a way we can see the Attunity connectors drivers in the Import/Export Wizard (64 bit) for SQL Server 2008 R2?
Although I made it work for SSIS, I would need these drivers in the Import/Export wizard so as to automate it for numerous number of tables which I want to migrate.
Can the Attunity connectors for Oracle be used in the Import/Export wizard? If so please let me know.
Regards,
Ashutosh.
Ashutosh.

I have 100 tables to migrate. Creating a data flow for each table is tedious and that's why I was looking out for a way to do it through import export wizard so that I don't have to create a separate data source and destination for each table in the Data
flow Task.
Is there a way to loop through all tables and transfer data in SSIS without having multiple sources and destinations created for each table? This also involves a bit of transformation as well.
Regards,
Ashutosh.

Export in Terminating Mode

hi,
Please let me know the possible cause of this error : Data Export in Terminating Mode
thanks

Jim,
Export does run in a background process. There are actually at least 3 processes running.
1. You have the client, which is where you run your expdp/impdp command.
2. You have the MCP processes which is a Data Pump process
3. You have a WORKER processes (or more if you use parallel) that are Data Pump processes.
I always use LINUX, but I think it works the same for Windows. Once you have the job running, you can type a CTL-C and you will get to an IMPDP> or EXPDP> prompt. This allows you to do other commands. One is to exit the client process. You can also stop the job or kill the job. Try it and type HELP at one of those prompts.
At this same prompt, you can type STATUS will will give you some idea on what is being worked on.
Some of the reasons you would want to attach to a job is
1. You previously exited and want to reattach to change something.
2. You left it running while you were in the office and now you are home and want to see the status. (you can have multiple clients attached to the same data pump job.
3. Your job stopped for some reason (power outage, failure, etc.) and you want to restart it.
Hope this helps.
Dean

Any solutions for "Export process terminated unexpectedly [11]" problem?

Hey guys,
I'm trying to simply use Quicktime Pro (Version 7.6.6 Build 1632) to enable the "Fast Internet Start" feature of a 640 x 480 video H.264 video. It uses 16-bit Little Endian for audio, if that's of any help.
Anyway, like lots of other users with this same exact problem, I make the changes in the "Export" dialogue (in this case, enabling "Fast Internet Start" and lowering the audio quality a bit), and the little status indicator goes away and "Export Process Terminated Unexpectedly {11}" appears in its place. Has a definitive answer been found for this problem?

Similar issue here when exporting AVI files captured from Canon G9 to iPod.
QuickTime Pro quits with: Failed: process terminated unexpectedly (11).
Oddly, if I start from a power off and run QTime the error does not occur.
Of course powering off for every export is a real PAIN IN THE Axx but it is a work around on this end.
I have yet to try 3rd party software but this is error occurs with Quick Time Pro Ver 7.5 build 149.5.
Sad

Export query result to csv using Export Wizard

Been a decade since I last used Oracle and related tools.
I had to use Oracle server again, I have a query over multiple tables, I am to run a scheduled script that will spit out the query result as a csv file.
I started with SQL Developer Export wizard, in step "Specify Data", I am at a loss, where to specify the query itself? I see a Name,Schema,Type input, a text area below, Up,UpAll,Down,DownAll buttons etc etc. Where do I specify my query here? Can someone please help?
Is this the best way to go about to schedule a data export (query to csv) daily?

To export a user query rather than a whole table, run it in a worksheet and export using the context menu on the result grid. However none can be scheduled.
Instead you can look at the SPOOL command and schedule it through SQL*Plus. Any questions can go to the iSQL*Plus and/or SQL And PL/SQL forum.
Have fun,
K.

Data convertion while exporting data into flat files using export wizard in ssis

Hi ,
while exporting data to flat file through export wizard the source table is having NVARCHAR types.
could you please help me on how to do the data convertion while using the export wizard?
Thanks.

Hi Avs sai,
By default, the columns in the destination flat file will be non-Unicode columns, e.g. the data type of the columns will be DT_STR. If you want to keep the original DT_WSTR data type of the input column when outputting to the destination file, you can check
the Unicode option on the “Choose a Destination” page of the SQL Server Import and Export Wizard. Then, on the “Configure Flat File Destination” page, you can click the Edit Mappings…“ button to check the data types. Please see the screenshot:
Regards,
Mike Yin
TechNet Community Support

SQL Server Import and Export Wizard Issue

i am trying to export SQL data into excel to send out weekly reports. I have created a view and a SQL account has access to this view; however, I am unable to successfully export the data. In preview I see all of the data yet it fails on the
Pre-execute with the below. It creates the excel file with just the header. I am using SQL 2014 and loaded the 64 bit AccessDatabaseengine. I am selecting excel 2007. Any ideas welcome.
Messages
Error 0xc0202009: Data Flow Task 1: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E37.
(SQL Server Import and Export Wizard)
Error 0xc02020e8: Data Flow Task 1: Opening a rowset for "WeeklyList" failed. Check that the object exists in the database.
(SQL Server Import and Export Wizard)
Error 0xc004701a: Data Flow Task 1: Destination - WeeklyList failed the pre-execute phase and returned error code 0xC02020E8.
(SQL Server Import and Export Wizard)

Hi astro,
Please ensure that you haven’t renamed or moved the destination excel file during the exporting process. Also make sure that “Create destination table” option is checked as below screenshot and the SQL statement is correct.
For more details about using SQL Server Import/Export Wizard to export data from a SQL Server database to an Excel spreadsheet, please review the below blog.
http://www.mssqltips.com/sqlservertutorial/202/simple-way-to-export-data-from-sql-server/
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.
Lydia Zhang
TechNet Community Support

Error when exporting to xslx using export wizard or SSIS package

Greetings:
SQL Server 2008 R2, SSMS version 10.50.2500.0
I tried to use the import/export wizard to create a SSIS package that takes the results of a query and outputs to an excel file.
Here is the table it is deriving from:
CREATE TABLE OrderTravOutput (
TravelerID int
,FirstName varchar(255)
,LastName varchar(255)
,Email varchar(255)
,Email2 varchar(255)
,Cell varchar(255)
,OrderID varchar(255)
,OrderSkillSet varchar(255)
,FacilityName varchar(255)
,City varchar(255)
,StateProvinceID varchar(255)
,ParentID int
,HealthSystem varchar(255)
,UnitName varchar(255)
,LastContact datetime
,OrderStart datetime
,OrderEnd datetime
,Tag varchar(255)
,CompleteDate datetime
,Recruiter varchar(255)
,Brand varchar(255)
,RecruiterEmail varchar(255)
,NumberOfWeeks int
,OrderShifts varchar(255)
,MaxPayrate varchar(255)
,FileOut int
,JobDescription varchar(max)
,RequiredQualifications varchar(max)
,PreferredQualifications varchar(max))
Here is the query being used in the wizard:
select DISTINCT r2.*
from OrderTravOutput r2
JOIN OrderTravOutput r3 ON r2.OrderID = r3.OrderID
AND r2.CompleteDate = (SELECT max(CompleteDate)
FROM OrderTravOutput
WHERE OrderID = r2.OrderID
AND TravelerID = r2.TravelerID
AND r2.OrderSkillSet = ( SELECT TOP 1 OrderSkillSet
FROM OrderTravOutput
WHERE OrderID = r2.OrderID
AND TravelerID = r2.TravelerID)
When I run it, it fails. Here is the report:
Operation stopped...
- Initializing Data Flow Task (Success)
- Initializing Connections (Success)
- Setting SQL Command (Success)
- Setting Source Connection (Success)
- Setting Destination Connection (Success)
- Validating (Success)
- Saving (Success)
- Prepare for Execute (Success)
- Pre-execute (Error)
Messages
* Error 0xc0202009: Data Flow Task 1: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E21.
(SQL Server Import and Export Wizard)
* Error 0xc0202025: Data Flow Task 1: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)
* Error 0xc004701a: Data Flow Task 1: component "Destination - Query" (103) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
- Executing (Warning)
Messages
* Warning: Preparation SQL Task 1: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done. (SQL Server Import and Export Wizard)
* Warning: Preparation SQL Task 1: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done. (SQL Server Import and Export Wizard)
- Copying to `Query` (Stopped)
- Post-execute (Stopped)
Messages
* Information 0x4004300b: Data Flow Task 1: "component "Destination - Query" (103)" wrote 0 rows.
(SQL Server Import and Export Wizard)
What did I do wrong?
Thanks for any help.

I see some possible problems with the query. Does it return expected results when executed in the Query window in SQL Server Management Studio (SSMS)?
1. You will want to specify fields explicitly in the select list, rather than using "*"
2. You will want to add r3 and r4 aliases in the subqueries, because OrderTravOutput r2 and r3 are definitely in scope there, and specifying an unqualified "OrderID" in the join condition would be ambiguous.
3. Add an ORDER BY clause to the second subquery, because otherwise TOP 1 OrderSkillSet is meaningless.
4. The intersection of these two subqueries may exclude records you want to see. For example, you might have 20 records for a particular combination of OrderID and TravelerID. But if one of those records has
the MAX(CompleteDate) and a different record has the TOP 1 OrderSkillSet, the query will return zero records for this OrderID and TravelerID, because there is no single record that satisfies both conditions. Is this what you intend? Running the
query first in SSMS helps to clarify whether it is returning the expected results.
Anyway, you could start with something like this version of the query:
SELECT DISTINCT r2.TravelerID,
r2.FirstName,
r2.LastName,
r2.Email
FROM OrderTravOutput r2
JOIN OrderTravOutput r3 ON r2.OrderID = r3.OrderID
AND r2.CompleteDate = (SELECT MAX(CompleteDate)
FROM OrderTravOutput r3
WHERE r3.OrderID = r2.OrderID
AND r3.TravelerID = r2.TravelerID)
AND r2.OrderSkillSet = (SELECT TOP 1 OrderSkillSet
FROM OrderTravOutput r4
WHERE r4.OrderID = r2.OrderID
AND r4.TravelerID = r2.TravelerID
ORDER BY r4.OrderSkillSet)

Import/Export wizard auto-generates all columns as DATE

Hi
I'm trying to use the Import/Export Wizard as I used to, as a handy tool to figure out what a series of T-SQL statements (in an SSIS package) is doing - or, if I'm lucky, what on earth the original dev
intended them to do.
Version: SQL 2014 64-bit running on Win 7 64-bit
The code is pretty dreadful:
SELECT DISTINCT on one set of column names,
join this set to another table but not on exactly the same set of column names,
embedded (SELECT MAX(bla) FROM SameTable WHERE [match to outer set on another set of columns] GROUP BY [hey, yet another set of columns!]) inside the SELECT column list...
and it all goes to a nasty #Tmp, which is then abused with further bad code further down.
Imp/Exp is always handy to quickly get the intermediate results into an auto-created real table, so I can figure out exactly what the effect of this is. I use it to export from the database back to the same database, but to a persisted table.
This time (first time with SQL2014) it's not working. The source is "write a query" (paste the actual query). The destination I set to a new table. The auto-generation of the new table creates every column as type
date. Not surprisingly, this doesn't work, as the original data is mostly not of
date time.
Looks like a bug. Any idea of a workaround or fix?
thanks!

Sorry, but I think you're still not getting what I'm saying.
This is not a production SSIS package design, but a quick'n'nasty diagnosis technique I'm used to using:
- Find some SQL in an existing query/script that I'm trying to debug
- Paste it into Import/Export wizard as a source
- Wizard creates a new table for the result - I then have the results persisted for examination, comparison with the results from refactored code, etc.
And I can't even put suitable CAST/CONVERT statements in, because the wizard is mis-identifying the
input column data types, with no way to change them. It's somehow thinking that every column in the input (the SQL query) is of type
date(500), when the columns are obviously not of this type.

SQL Exoress 2008 import export Wizard wont import Access 2003 mdb to SQL 2008 DB

Just installed SQL Express with Tools, including SSME and Import Export Wizard.
Attempted to transfer Access 2003 DB tables from an mdb file to a SQL 2008 Express DB.
I can view the data in the tables in Access, however, when I tell it to do the deed, it begins the process and then errors out with a Error 0xc020801c:
"TITLE: SQL Server Import and Export Wizard
Could not connect source component.
Error 0xc020801c: Source - ParentingStats [1]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "SourceConnectionOLEDB" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
ADDITIONAL INFORMATION:
Exception from HRESULT: 0xC020801C (Microsoft.SqlServer.DTSPipelineWrap)"
I am unable to find anything that translates this into something mere mortals can deal with. This is repeatable.
Steps in the wizard:
1. Source: Data Source selected is "Microsoft Access". The filename is correct. The username is correct. The password is blank (there is no password in the Access db). Clicking on the "Advanced..." button, I get the opportunity to "Test Connection". I test the connection and the test is successful.
2. Destination: I select my server name and the SQL Native Client, select Windows Authentication, and Select my SQL 2008 Express db from the dropdown list.
3. Specify Tabloe Copy or Query: I select Table copy
4. Select Table or Views: I check the tables I want to copy and successfully preview the data in each table that I checked. I click on "Edit Mappings ..." and verify that I want to create a new table for each checked table.
5. Run package: I accept the pre-checked "Run Immediately" and click the NEXT button
6. I get the following:
"Source Location : C:\Users\wb5rvz\Documents\StatisticsApp_V3_69.mdb
Source Provider : Microsoft.Jet.OLEDB.4.0
Destination Location : SHACK_PC\SQLEXPRESS
Destination Provider : SQLNCLI
Copy rows from `ParentingStats` to [dbo].[ParentingStats]
The new target table will be created.
Copy rows from `Statistics` to [dbo].[Statistics]
The new target table will be created.
Copy rows from `StatsSummary` to [dbo].[StatsSummary]
The new target table will be created.
Copy rows from `Volunteers_Confidential` to [dbo].[Volunteers_Confidential]
The new target table will be created.
Copy rows from `YearMonthTbl` to [dbo].[YearMonthTbl]
The new target table will be created.
The package will not be saved.
The package will be run immediately.
Provider mapping file : c:\Program Files\Microsoft SQL Server\100\DTS\MappingFiles\JetToMSSql9.xml"
7. I click the FINISH button and I get
"Initializing Data Tasks .... Success"
"Initializing Connections ...Success"
"Setting SQL Commend ....20% Compoete"
"Setting Source Connection ...Error (and an error link)"
(All following tasks were "Stopped"
Error detail is:
===================================
Could not connect source component.
Error 0xc020801c: Source - ParentingStats [1]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "SourceConnectionOLEDB" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
(SQL Server Import and Export Wizard)
===================================
Exception from HRESULT: 0xC020801C (Microsoft.SqlServer.DTSPipelineWrap)
Program Location:
at Microsoft.SqlServer.Dts.Pipeline.Wrapper.CManagedComponentWrapperClass.AcquireConnections(Object pTransaction)
at Microsoft.SqlServer.Dts.DtsWizard.Execute.SetSourceConnection(Exception& ex, TransformInfo ti)
OS is Vista Home Premium SP1 (32 bit)
Processor = Intel core 2 duo E7200 @ 2.5 GHz
SQL Server Software was just downloaded yesterday, so it is whatever is current on the download site:
SQL Express with Tools
So, how do I get this transform to work? I do not have nor do I want/afford to put Access 2003 on this machine.
Thanks
RRR

I had this similar problem - 32-bit SQL Server 2005 trying to import tables from Access 2000 .mdb file, same error:
Error 0xc020801c: Source - ParentingStats [1]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "SourceConnectionOLEDB" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
(SQL Server Import and Export Wizard)
===================================
Exception from HRESULT: 0xC020801C (Microsoft.SqlServer.DTSPipelineWrap)
I know you said you clicked "Advanced..." and Test Connection when you chose your Access database - but that is what resolved the error for me. I chose my .mdb file, username is admin, password is blank, but if I don't click the Advanced button and test the connection before continuing on, the import fails with above error message. Go figure, since the username/blank password is correct.
FWIW, sorry if that doesn't help you though.

SQL Server 2012: Import and Export Wizard - Exporting Multiple Result Sets at Once?

I'm working in SQL Server 2012 trying to export some data from our database into an Excel file. My SQL statement has two separate Select statements. They are not joined by a union. When I Execute them inside of SQL Server Management Studio, with Results
set to go to a Grid, I get two result sets back. Two full tables of data.
However, when I use the Import and Export Wizard, the Excel sheet only has the first set of data.
What do I need to do to have it so both result sets show up in the excel file?

Why cant use merge them using union/union all if intention is to get them to same sheet? Is it like the metadata is different so that they cant be merged to single sheet?
If that being the case you need to do it in two steps.
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Error message using SQL import and Export Wizard with Excel spread sheet

I am trying to import an Excel spreadsheet using the Import export wizard that is provided with SQL 2014.
Everything seems to set up OK but then when I go to do the transfer "error message" comes up saying:
External Table is not in the expected format.(Microsoft Jet Database Engine).
This is a spreadsheet and there is no database, that is why I want to import it into a database!! So the reference to JET is a tad disappointing.
So why the error and how do I fix the problem?
As there are over 100 variables in the spread sheet rows, it would be great to have this automatically create the database and populate the fields.
I am using SQL 2014 Express and Office Excel 2013.
Thank you in advance for taking the time to read this, and hopefully sheading some light on the issue.

Hi AWlcurrent,
When import a .xlsx file to SQL Server using SQL Server Import and Export Wizard, you see a “External Table is not in the expected format.(Microsoft Jet Database Engine).” error message. This error message seems that the Microsoft JET Database Engine is
unable to handle something that is contained in the file.
So please make sure there is no unsupported content in the Excel file. Alternatively, we can use ‘Microsoft Excel’ as the Data Source, then Select ‘Microsoft Excel 2007’ as the Excel version to import the excel file.
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support

Export DDL in Export Wizard - Terminator

Similar Messages

Maybe you are looking for