Re: Trying to get a SSIS Import wizard package to actually schedule and work.
- From: v-adamqu@xxxxxxxxxxxxxxxxxxxx (Adams Qu [MSFT])
- Date: Fri, 21 Dec 2007 08:03:38 GMT
Dear Frank,
Thank you for posting back.
First of all, we are sorry for the inconvenience this has brought to you. I
would like to explain that we are allowed to re-use the SSIS package
created by Import/Export Wizard. However, we need to ensure that the temp
files initially created by this package exit on the system. These temporary
files are responsible for the functions of Connection Manger of running
SSIS package.
Thus, if you prefer to re-use the package saved from "Import/Export
Wizard", we need to backup all the tmp files created by this package to
prevent them from being unexpectedly deleted.
In addition, you can also attempt to use the "Transfer SQL Server Objects
Task" in SQL Server Business Intelligence Development Studio (Method One in
my previous post). Please be assured that this task also does not require
the development skill. We use this task to transfer the SQL Server Objects
by editing its properties directly. For your reference, I have included the
article which contains the detail information about "Transfer SQL Server
Objects Task" for your reference.
Transfer SQL Server Objects Task
http://msdn2.microsoft.com/en-us/library/ms142159.aspx
Copy SQL Server Objects Task
http://msdn2.microsoft.com/en-us/library/aa933510(SQL.80).aspx
I also understand that you have a lot of users who create 2000 DTS
packages. I also would like to explain that after installing Run-time
Support for SQL Server 2000 DTS Packages, we are still able to run the SQL
Server 2000 DTS on the SQL Server 2005 SSIS via the " dtsrun.exe" from
command-line or "Execute DTS 2000 Package Task" from Integration Services
Packages. The following article should be helpful:
SQL Server 2005 Integration Services Backward Compatibility
http://msdn2.microsoft.com/en-us/library/ms143706.aspx
At the same time, I also would like to share with the following relevant
resources for your further reference:
Additional Reference
=========================
Reusing Package Objects
http://msdn2.microsoft.com/en-us/library/ms345172.aspx
SQL Server 2005 Webcasts
http://msdn2.microsoft.com/en-us/sqlserver/aa336323.aspx
Please don't hesitate to let me know if you have any further question or
needs my further assistance.
Have a nice day!
Best regards,
Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "frankm" <frankm@xxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.sqlserver.dts
| References: <d7Q9j.25029$4V6.5475@xxxxxxxxxxxxxxxxxxxxxxxxxx>
<zzCvDIhQIHA.8164@xxxxxxxxxxxxxxxxxxxxxx>
| Subject: Re: Trying to get a SSIS Import wizard package to actually
schedule and work.
| Lines: 169
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
| X-RFC2646: Format=Flowed; Original
| Message-ID: <Xo9aj.264$6%.210@xxxxxxxxxxxxxxxxxxxx>
| NNTP-Posting-Host: 165.152.63.227
| X-Complaints-To: abuse@xxxxxxxxxxx
| X-Trace: nlpi061.nbdc.sbc.com 1198072503 ST000 165.152.63.227 (Wed, 19
Dec 2007 08:55:03 EST)
| NNTP-Posting-Date: Wed, 19 Dec 2007 08:55:03 EST
| Organization: AT&T http://yahoo.sbc.com
| X-UserInfo1:
TSU[@I_AO@UQBWXYAZJD]_\@VR]^@B@MCPWZKB]MPXH@ETUCCNSKQFCY@TXDX_WHSVB]ZEJLSNY\
^J[CUVSA_QLFC^RQHUPH[P[NRWCCMLSNPOD_ESALHUK@TDFUZHBLJ\XGKL^NXA\EVHSP[D_C^B_^
JCX^W]CHBAX]POG@SSAZQ\LE[DCNMUPG_VSC@VJM
| Date: Wed, 19 Dec 2007 07:54:59 -0600
| Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!newsfeed0
0.sul.t-online.de!t-online.de!newshub.sdsu.edu!newscon04.news.prodigy.net!pr
odigy.net!newsdst01.news.prodigy.net!prodigy.com!postmaster.news.prodigy.com
!nlpi061.nbdc.sbc.com.POSTED!e51d285f!not-for-mail
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.dts:4233
| X-Tomcat-NG: microsoft.public.sqlserver.dts
|
| Thanks you for your response...
| I was unaware that the Import/Export wizard pkgs was to perform the tasks
| only once.
| It allows you to save it as did DTS wizard. The assumption is that you
can
| re-use it.
| This is inconsistent with SQL Server 2000 DTS. So I had no way of knowing
-
| thank you.
|
| I will try Method 2, simply because I have no time to become a developer.
| We have a lot of regular users who create 2000 DTS pkgs now, this is
going
| to be a nightmare.
|
|
|
|
| "Adams Qu [MSFT]" <v-adamqu@xxxxxxxxxxxxxxxxxxxx> wrote in message
| news:zzCvDIhQIHA.8164@xxxxxxxxxxxxxxxxxxxxxxxxx
| > Dear Frank,
| >
| > Thank you for posting here.
| >
| > Based on my experience and research, I would like to explain that when
| > using the wizard to build the package, while saving or executing it at
the
| > first time, there are some *.tmp files that will stored under
| > %USERPROFILE%\Local Settings\Temp folder and these *.tmp files are
| > necessary during the execution of the package. If any of them are
corrupt
| > or missing, we may experience the behavior you have experienced.
| >
| > To workaround/resolve the above issue, there are two possible methods:
| >
| > Method One
| > ------------------
| > 1) As you know, the Import/Export Wizard is for you to perform the tasks
| > once. To reuse the package and easily deploy the package to other SQL
| > servers, I suggest that you develop the package in BIDS (SQL Server
| > Business Intelligence Development Studio). With the written package, it
is
| > easily deployed / reused on other servers. Therefore, I suggest that you
| > create the package manually to transfer objects between databases
directly
| > in BIDS by using "Transfer SQL Server Objects Task"
| >
| > Method Two
| > ------------------
| > 2) If you prefer to use the package saved from "Import/Export Wizard"
and
| > reuse it, we have to also take a copy of all generated *.tmp files under
| > %USERPROFILE%\Local Settings\Temp folder. Whenever you execute the
package
| > again, check the "Connection Manager" part in "Execute Package Utility"
| > and
| > note down the path/file information recorded into the package. Then,
copy
| > all originally saved *.tmp files to the expected folder and run the
| > package. Or, we can also change the path/file information to the new
one
| > in
| > the "Connection Manager" part, where stores these *.temp files.
| >
| > According to above methods, we recommend using the first method to
rebuild
| > the SSIS package via BIDS ->"Transfer SQL Server Objects Task" to see
if
| > it
| > can resolve our issue.
| >
| > If the issue persists, please help me to capture a screenshot when the
| > package fails to be executed:
| >
| > Screenshot
| > =========================
| > 1. Please press the Print Screen key (PrtScn) on your keyboard.
| > 2. Click Start, click Run, type MSPAINT, and click OK.
| > 3. In Paint, click Paste under the Edit Menu, click Save under the File
| > menu, type a file name for the snap shot, choose JPEG as "Save as type",
| > click "Desktop" on the left pane, and click Save.
| > 4. Please find the screenshot on the Desktop and send it as an
attachment
| > to: v-adamqu@xxxxxxxxxxxxx
| >
| > If anything is unclear in my post, please don't hesitate to let me know
| > and
| > I will be glad to help.
| >
| > Have a nice day!
| >
| > Best regards,
| >
| > Adams Qu
| > MCSE, MCDBA, MCTS
| > Microsoft Online Support
| >
| > Microsoft Global Technical Support Center
| >
| > Get Secure! - www.microsoft.com/security
| > =====================================================
| > When responding to posts, please "Reply to Group" via your newsreader so
| > that others may learn and benefit from your issue.
| > =====================================================
| > This posting is provided "AS IS" with no warranties, and confers no
| > rights.
| >
| > --------------------
| > | From: "frankm" <frankm@xxxxxxxxxxxxxxxx>
| > | Newsgroups: microsoft.public.sqlserver.dts
| > | Subject: Trying to get a SSIS Import wizard package to actually
schedule
| > and work.
| > | Lines: 34
| > | X-Priority: 3
| > | X-MSMail-Priority: Normal
| > | X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
| > | X-RFC2646: Format=Flowed; Original
| > | Message-ID: <d7Q9j.25029$4V6.5475@xxxxxxxxxxxxxxxxxxxxxxxxxx>
| > | NNTP-Posting-Host: 165.152.63.227
| > | X-Complaints-To: abuse@xxxxxxxxxxx
| > | X-Trace: newssvr14.news.prodigy.net 1197985353 ST000 165.152.63.227
| > (Tue,
| > 18 Dec 2007 08:42:33 EST)
| > | NNTP-Posting-Date: Tue, 18 Dec 2007 08:42:33 EST
| > | Organization: SBC http://yahoo.sbc.com
| > | X-UserInfo1:
| >
[[PAPDCAO@UQBWXYAZJD]_\@VR]^@B@MCPWZKB]MPXHTEPIB_NVUAH_[BL[\IRKIANGGJBFNJF_D
| >
OLSCENSY^U@FRFUEXR@KFXYDBPWBCDQJA@X_DCBHXR[C@\EOKCJLED_SZ@RMWYXYWE_P@\\GOIW^
| > @SYFFSWHFIXMADO@^[ADPRPETLBJ]RDGENSKQQZN
| > | Date: Tue, 18 Dec 2007 13:42:33 GMT
| > | Path:
| >
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!newsfeed0
| >
0.sul.t-online.de!t-online.de!newshub.sdsu.edu!newscon04.news.prodigy.net!pr
| >
odigy.net!newsdst01.news.prodigy.net!prodigy.com!postmaster.news.prodigy.com
| > !newssvr14.news.prodigy.net.POSTED!e51d285f!not-for-mail
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.dts:4223
| > | X-Tomcat-NG: microsoft.public.sqlserver.dts
| > |
| > | Sorry in advance for the frustrated tone.......
| > |
| > | -Created an straight up Wizard Import of data from one system /
database
| > to
| > | another.
| > | -Figured out the scheduling a SSIS pkg thing.
| > | -Was getting encryption errors - found I needed Server Storage.
| > | -Figured out that I had to "COPY xxxx AS'
| > | -Was actually able to run the packages manually from the job. woohoo!
| > | -Scheduled jobs to run - running sa and or service account etc.
| > | -Come in Monday to find that they have been failing over the weekend.
| > | -Then got the fact that it couldn't find a tmp file in _MY_ home
| > directory
| > | (why it would that is incomprehensible).
| > | -Tried to create a common folder, am now getting access denied no
matter
| > how
| > | many rights I give to how may logins for any level of the directory or
| > | drive.
| > | -Kinda looks like a temporal key file that expires, goes away or is
| > deleted
| > | on exit.
| > | -Now I am back to - can't run it manually or schedule it to run.
| > |
| > | Can anyone help me???????????????
| > | I'm an admin and a dba - not a developer.
| > |
| > | Just ordered 2 books on SSIS - hope someone gets their pockets lined
| > from
| > | the $70 I just shelled out.
| > |
| > | Does anyone think this is insane? Something that I could do in 10-15
| > minutes
| > | in DTS is now running into 3 days and I still haven't gotten it
running.
| > |
| > |
| > | frankm
| > |
| > |
| > |
| > |
| > |
| >
|
|
|
.
- Follow-Ups:
- References:
- Prev by Date: Re: Insert data to table with index
- Next by Date: Re: Syntax help
- Previous by thread: Re: Trying to get a SSIS Import wizard package to actually schedule and work.
- Next by thread: Re: Trying to get a SSIS Import wizard package to actually schedule and work.
- Index(es):
Relevant Pages
|