Option to SAVE SQL Import as SSIS not available

Question

Option to SAVE SQL Import as SSIS not available

Garin T

Right there with Babe

Points: 731
More actions
March 16, 2017 at 1:01 pm

#319673

Every morning I manually used Tasks SQL Import to populate my table using excel file as my source of data.
After one week of doing this process manually, it is getting boring. I do not want to manually do this import every morning. I want to save my manual SQL Import as SSIS package so I can use SQL Agent Job to execute SSIS package.
But for some reason, during my manual SQL Import process, I do not see an option to allow me to save my import process as SSIS package.
I am currently using SQLServer2012. What are my options in order for me to save my SQL import as SSIS package?
Thank you.

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Sue_H SSC Guru Points: 90860 More actions · Answer 1

Garin T - Thursday, March 16, 2017 1:01 PM
Every morning I manually used Tasks SQL Import to populate my table using excel file as my source of data.
After one week of doing this process manually, it is getting boring. I do not want to manually do this import every morning. I want to save my manual SQL Import as SSIS package so I can use SQL Agent Job to execute SSIS package.
But for some reason, during my manual SQL Import process, I do not see an option to allow me to save my import process as SSIS package.
I am currently using SQLServer2012. What are my options in order for me to save my SQL import as SSIS package?
Thank you.

Could be you're using the Express edition. Only the Import/Export wizard and data source adapters are available with Express.

Sue

Garin T Right there with Babe Points: 731 More actions · Answer 2

Garin T

Right there with Babe

Points: 731

March 16, 2017 at 2:01 pm

#1933614

I am using Enterprise edition.

Sue_H SSC Guru Points: 90860 More actions · Answer 3

Garin T - Thursday, March 16, 2017 2:01 PM
I am using Enterprise edition.

Not sure how yours is different then. There is a Save and Run Package option towards the end of the process, before you get to the Finish page.
If you have that option, that is where you would save the package. Maybe it's there and you've just run through it fast and didn't notice?

Sue

Garin T Right there with Babe Points: 731 More actions · Answer 4

On below screen print, I am expecting to see a Check Box for saving the import as SSIS package

Sue_H SSC Guru Points: 90860 More actions · Answer 5

Garin T - Thursday, March 16, 2017 2:20 PM
On below screen print, I am expecting to see a Check Box for saving the import as SSIS package

Read the bottom of the screen - the part in yellow where it says why you can't save it.
Doesn't look like it's the Enterprise Edition.

Sue

Luis Cazares SSC Guru Points: 183706 More actions · Answer 6

Is it possible that you have Express in your local machine and Enterprise on the server?
That might explain why the option is not there.

Luis C.
General Disclaimer:
Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?

How to post data/code on a forum to get the best help: Option 1 / Option 2

Garin T Right there with Babe Points: 731 More actions · Answer 7

When I right-click on my server name, the screen print below shows "Enterprise"

Sue_H SSC Guru Points: 90860 More actions · Answer 8

My guess would be that Luis is correct - there is a server that is Enterprise SQL Server that you connect to and you also have SQL Server Express installed locally. I can't think of any other explanation for the differences. Check the services on your PC.

Sue