Showing posts with label package. Show all posts
Showing posts with label package. Show all posts

Monday, March 19, 2012

Create Report Snapshot from SSIS

I need to create a SSRS report snapshot at the end of an SSIS package (seems like this would be a common task). I tried connecting to the ReportingService web service to do this but I get the following error when after I select the web service in the Web Service Task:

This version of the Web Services Description Language (WSDL) is not supported.

Is there as simple way to do what I want?

The Web Service task has some limitations in respect to what WSDL it can consume. Put bluntly it is not much use in practice.

The easiest way to do this would be to write a custom task. You could do this in a script task, but generating the proxy class from WSDL and installing it for use by the Script Task would be almost as much work as just doing it all in a custom task. There are only a few lines of code required to actually call the methods, it is not hard.

|||

I'm interested in doing the exact same thing. Can you provide a sample or template for how to do this? By writting a custom task, do I still have to create the proxy? What would the custom task look like?

Thanks for your help!

|||

See the ReportingService2005.UpdateReportExecutionSnapshot method.

The proxy class is just WS wrapper class, if you write a custom task, then I would expect you to add the web reference directly into you project, there is no point in creating a proxy. The Script task does not allow you to add web references, so it is a must in that case.

Create Report Snapshot from SSIS

I need to create a SSRS report snapshot at the end of an SSIS package (seems like this would be a common task). I tried connecting to the ReportingService web service to do this but I get the following error when after I select the web service in the Web Service Task:

This version of the Web Services Description Language (WSDL) is not supported.

Is there as simple way to do what I want?

The Web Service task has some limitations in respect to what WSDL it can consume. Put bluntly it is not much use in practice.

The easiest way to do this would be to write a custom task. You could do this in a script task, but generating the proxy class from WSDL and installing it for use by the Script Task would be almost as much work as just doing it all in a custom task. There are only a few lines of code required to actually call the methods, it is not hard.

|||

I'm interested in doing the exact same thing. Can you provide a sample or template for how to do this? By writting a custom task, do I still have to create the proxy? What would the custom task look like?

Thanks for your help!

|||

See the ReportingService2005.UpdateReportExecutionSnapshot method.

The proxy class is just WS wrapper class, if you write a custom task, then I would expect you to add the web reference directly into you project, there is no point in creating a proxy. The Script task does not allow you to add web references, so it is a must in that case.

Create Report Snapshot from SSIS

I need to create a SSRS report snapshot at the end of an SSIS package (seems like this would be a common task). I tried connecting to the ReportingService web service to do this but I get the following error when after I select the web service in the Web Service Task:

This version of the Web Services Description Language (WSDL) is not supported.

Is there as simple way to do what I want?

The Web Service task has some limitations in respect to what WSDL it can consume. Put bluntly it is not much use in practice.

The easiest way to do this would be to write a custom task. You could do this in a script task, but generating the proxy class from WSDL and installing it for use by the Script Task would be almost as much work as just doing it all in a custom task. There are only a few lines of code required to actually call the methods, it is not hard.

|||

I'm interested in doing the exact same thing. Can you provide a sample or template for how to do this? By writting a custom task, do I still have to create the proxy? What would the custom task look like?

Thanks for your help!

|||

See the ReportingService2005.UpdateReportExecutionSnapshot method.

The proxy class is just WS wrapper class, if you write a custom task, then I would expect you to add the web reference directly into you project, there is no point in creating a proxy. The Script task does not allow you to add web references, so it is a must in that case.

Sunday, March 11, 2012

Create Package in SQL Server Management Studio Express?

Our server currently has the following components installed for SQL Server 2005: 1. SQL Server Management Studio Express and 2. Configuration Tools (SQL Server Configuration Manager, SQL Server Error and Usage Reporting, and SQL Server Service Area Configuration).

Is there a way to setup a package using the software currently installed (if not, what needs to be installed in order to setup a package)?

I'm looking to schedule running an executible, it was fairly easy with SQL Server 2000 (using DTS), but I'm unsure how to set this up using the software we currently have installed.

It looks like you are using SQL Sever 2005 express?

Sorry but SSIS doesn't come with express, you'll need Standard edition or better:

see the section, "Integration and Interoperability":

http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx

|||P.S. Installing standard edition tools seems to do the trick (be sure to install Integration Services).

Wednesday, March 7, 2012

Create My Own Log (for functionality)

I'm calling stored procedures in a DTS package. The log file only shows that of DTS. In stored procedures I use "Print" to print out error messages the program encouters. I can see the errors when I execute a procedure in Query Analyzer, but they go nowhere when I run a DTS package.

How do I generate a myfunctionality.log with these lines?

Thanks,

LiliHi,

The best way to add Own Log functionality , is to create a log table and use insert statement to log message instead of print. The advantage will be that log will be available for future reference whereas filelog will be over written every time you run package.

best of luck

Create MSI Installer for SSIS Package

Can anyone sugest me steps to create the MSI Installer for SSIS packages

That is a bit of an open question.

I would use WIX to create the MSI. All you need to do is copy the SSIS package file to a folder location.

How you specify the location is up to you, and really depends on yoru requirements.

You could also create a Setup project in VS 2005, if you have it, or use one of the many other third party MSI creation tools.

If you wanted to install the packages in a manged location that would be harder. For the "SSIS Package Store" folder, then just copy the files to the folder. It may get a bit mnessy, but some points to help find that location. Try the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTS\Setup\DTSPath key to get the root folder. By default the sub-folder you want is Packages, but to be sure you would have to read the SSIS Service config file. To find this look in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTS\ServiceConfigFile

You may have to write a custom action to handle the manged stores, so for that reason I'd say go with files!

Saturday, February 25, 2012

Create Job From Package

Trying to re-create a job after creating a new package. Old job was called
with the following synax:
DTSRun
/~Z0x322A50F270D63181ED3C87B10CDFB82666EFD66DAA4A08 5A03A8BC5BE88F8ED29DDEA7B407C5035D24F856D65611E761 9014C84B379DD1CCDEDB18D65E657D60798D4F56B37D443D16 CE7A685E612C69DA8A82131E8A281EED2D73345D8E942D9BAE 8B20CB8A6844A569E61F23A0079738A695D8847C6811CFF198 6E161BE2D3A581BE388FDF14D4703D00
Where is this number located? Can this package be called using the syntax:
DTSRUN /N 'Name of my Package'
?
Regards,
Jamie
As my reply previously...
the easiest thing to do is to use DTSRUNUI to generate human-readable
command-line arguments and enter these in your DTS scheduled jobs, provided
they don't include passwords ie overwrite these arguments. The command you
have is encrypted and I don't know of any way to have it unencrypted. If
your question is how to relate this job to the parent DTS package, then the
name of the job should be the same as the package name.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Is this done to hide the sa password? I'm not sure why it would have been
encrypted. Must the permissions all coincide with the agent user-login if
those permissions are not run as sa? What might happen if the previous dba's
role/permissions on the database are no longer "systemadmin" and the job runs
under the context of their login?
Regards,
Jamie
"Paul Ibison" wrote:

> As my reply previously...
> the easiest thing to do is to use DTSRUNUI to generate human-readable
> command-line arguments and enter these in your DTS scheduled jobs, provided
> they don't include passwords ie overwrite these arguments. The command you
> have is encrypted and I don't know of any way to have it unencrypted. If
> your question is how to relate this job to the parent DTS package, then the
> name of the job should be the same as the package name.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
|||Jamie,
encrypting passwords is one reason it's useful - I certainly wouldn't want
my sa password in plain text hanging around
I generally prefer trusted security anyway for these packages. If not,
you'll have a sysadmin password available or have to encrypt the whole line
(or set up a proxy). The ideal solution for myself is to be able to read the
command line in the job to see what it is doing, and not have a security
worry, so trusted security fits the bill.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Friday, February 24, 2012

Create Flat File source programatically

I created a SSIS package, added Script task. created data flow task programatically, trying to add a flat file source component programatically. stuck at this point.

my goal is to add flat file source component to the data flow task and insert into a table in sql server using oledb destination component all programatically.

any help is appreciated. thanks.

You have to build a Flat File Connection Manager first and then reference it in your Flat File Source.

Have you looked at the BOL and previous posts in this forum for guidance?

Thanks.

|||

Iam creating the connection, I want know how I can read the flat file, and insert into a table. he is the code Iam using....

' Add the component to the dataFlow metadata collection

flatfileSource = dataFlowTask.ComponentMetaDataCollection.New()

' Set the common properties

flatfileSource.ComponentClassID = "DTSAdapter.FlatFileSource"

flatfileSource.Name = "FlatFileSource"

flatfileSource.Description = "Flat file source"

' Create an instance of the component

Dim inst As CManagedComponentWrapper = flatfileSource.Instantiate()

inst.ProvideComponentProperties()

' Associate the runtime ConnectionManager with the component

flatfileSource.RuntimeConnectionCollection(0).ConnectionManagerID _

= package.Connections("FlatFileConnection").ID

flatfileSource.RuntimeConnectionCollection(0).ConnectionManager _

= DtsConvert.ToConnectionManager90( _

package.Connections("FlatFileConnection"))

|||

You need to configure your connection manager by defining the file to use, column formats, and all additional properties before setting up your source.

There are also three more methods to call on your flat file source after the code you displayed:

AcquireConnections()

ReinitializeMetadata()

ReleaseConnections()

After that, you should hook up your source with the rest of a data flow and try to execute it.

HTH.

|||

sorry, Iam not explaining the problem correctly.

I do have those 3 lines of code. Iam lot where I have to loop through the columns or rows of my flat file. and how to map the columns to the destination table columns. any good example or reference please. thanks.

|||

Iam using the CreatePackage example in the samples. Iam able to create flat file source connection. not able to read the file.

Private Sub MapFlatFileDestinationColumns()

Dim wrp As CManagedComponentWrapper = flatfileDestination.Instantiate()

Dim vInput As IDTSVirtualInput90 = flatfileDestination.InputCollection(0).GetVirtualInput()

For Each vColumn As IDTSVirtualInputColumn90 In vInput.VirtualInputColumnCollection

wrp.SetUsageType(flatfileDestination.InputCollection(0).ID, vInput, vColumn.LineageID, DTSUsageType.UT_READONLY)

Next

' For each column in the input collection

' find the corresponding external metadata column.

Dim exCol As IDTSExternalMetadataColumn90

For Each col As IDTSInputColumn90 In flatfileDestination.InputCollection(0).InputColumnCollection

exCol = flatfileDestination.InputCollection(0).ExternalMetadataColumnCollection(col.Name)

wrp.MapInputColumn(flatfileDestination.InputCollection(0).ID, col.ID, exCol.ID)

Next

End Sub

trying use this code to map the columns, now my flat file connection is a source instead of destination. hope Iam explaining the problem.

thanks.

|||

External columns are automatically mapped to output columns when you call ReinitializeMetadata of your flat file source.

A good way for testing this would be to configure your package to some point (only a flat file source initially), save the package to a file and then open that file in the designer and inspect the metadata using the advanced component editor.

Thanks.

|||

Hi, i'm trying to 'emulate' a flat file source component using the script component in a data flow task. I need to be able to create a flat file connection and get the columns in the script (the columns change now and then, so i can't create a 'fixed' flatfile connection manager).

After getting the columns, i need to create output columns for the script component and to go through each row of the file and assign the column details.

I have derived column transformation after this source file step, do i need to make changes to the input / output columns of the derived column component in any way?

I also have an oledb destination, how can i generate an sql command to be used in the oledb destination? I know i can use sql from variable in an oledb source, but i can't find it in the oledb destination

I don't need real code examples, but i need some help on what objects need to be created, what functions need to be called etc... I'm very new to ssis programming.

Create Flat File source programatically

I created a SSIS package, added Script task. created data flow task programatically, trying to add a flat file source component programatically. stuck at this point.

my goal is to add flat file source component to the data flow task and insert into a table in sql server using oledb destination component all programatically.

any help is appreciated. thanks.

You have to build a Flat File Connection Manager first and then reference it in your Flat File Source.

Have you looked at the BOL and previous posts in this forum for guidance?

Thanks.

|||

Iam creating the connection, I want know how I can read the flat file, and insert into a table. he is the code Iam using....

' Add the component to the dataFlow metadata collection

flatfileSource = dataFlowTask.ComponentMetaDataCollection.New()

' Set the common properties

flatfileSource.ComponentClassID = "DTSAdapter.FlatFileSource"

flatfileSource.Name = "FlatFileSource"

flatfileSource.Description = "Flat file source"

' Create an instance of the component

Dim inst As CManagedComponentWrapper = flatfileSource.Instantiate()

inst.ProvideComponentProperties()

' Associate the runtime ConnectionManager with the component

flatfileSource.RuntimeConnectionCollection(0).ConnectionManagerID _

= package.Connections("FlatFileConnection").ID

flatfileSource.RuntimeConnectionCollection(0).ConnectionManager _

= DtsConvert.ToConnectionManager90( _

package.Connections("FlatFileConnection"))

|||

You need to configure your connection manager by defining the file to use, column formats, and all additional properties before setting up your source.

There are also three more methods to call on your flat file source after the code you displayed:

AcquireConnections()

ReinitializeMetadata()

ReleaseConnections()

After that, you should hook up your source with the rest of a data flow and try to execute it.

HTH.

|||

sorry, Iam not explaining the problem correctly.

I do have those 3 lines of code. Iam lot where I have to loop through the columns or rows of my flat file. and how to map the columns to the destination table columns. any good example or reference please. thanks.

|||

Iam using the CreatePackage example in the samples. Iam able to create flat file source connection. not able to read the file.

Private Sub MapFlatFileDestinationColumns()

Dim wrp As CManagedComponentWrapper = flatfileDestination.Instantiate()

Dim vInput As IDTSVirtualInput90 = flatfileDestination.InputCollection(0).GetVirtualInput()

For Each vColumn As IDTSVirtualInputColumn90 In vInput.VirtualInputColumnCollection

wrp.SetUsageType(flatfileDestination.InputCollection(0).ID, vInput, vColumn.LineageID, DTSUsageType.UT_READONLY)

Next

' For each column in the input collection

' find the corresponding external metadata column.

Dim exCol As IDTSExternalMetadataColumn90

For Each col As IDTSInputColumn90 In flatfileDestination.InputCollection(0).InputColumnCollection

exCol = flatfileDestination.InputCollection(0).ExternalMetadataColumnCollection(col.Name)

wrp.MapInputColumn(flatfileDestination.InputCollection(0).ID, col.ID, exCol.ID)

Next

End Sub

trying use this code to map the columns, now my flat file connection is a source instead of destination. hope Iam explaining the problem.

thanks.

|||

External columns are automatically mapped to output columns when you call ReinitializeMetadata of your flat file source.

A good way for testing this would be to configure your package to some point (only a flat file source initially), save the package to a file and then open that file in the designer and inspect the metadata using the advanced component editor.

Thanks.

|||

Hi, i'm trying to 'emulate' a flat file source component using the script component in a data flow task. I need to be able to create a flat file connection and get the columns in the script (the columns change now and then, so i can't create a 'fixed' flatfile connection manager).

After getting the columns, i need to create output columns for the script component and to go through each row of the file and assign the column details.

I have derived column transformation after this source file step, do i need to make changes to the input / output columns of the derived column component in any way?

I also have an oledb destination, how can i generate an sql command to be used in the oledb destination? I know i can use sql from variable in an oledb source, but i can't find it in the oledb destination

I don't need real code examples, but i need some help on what objects need to be created, what functions need to be called etc... I'm very new to ssis programming.

Sunday, February 19, 2012

create dymanic dts

i can writing dynamic dts package . but not working.

code is here :

Public goPackageOld As New Package
Public goPackage As Package2

Public Sub RunDTS()
Dim goPackage As Package2
goPackage = CType(goPackageOld, Package2)
goPackage.Name = "DTS3"
goPackage.Description = "DTS package description"
goPackage.WriteCompletionStatusToNTEventLog = False
goPackage.FailOnError = False
goPackage.PackagePriorityClass = CType(2, DTSPackagePriorityClass)
goPackage.MaxConcurrentSteps = 4
goPackage.LineageOptions = 0
goPackage.UseTransaction = True
goPackage.TransactionIsolationLevel = CType(4096, DTSIsolationLevel)
goPackage.AutoCommitTransaction = True
goPackage.RepositoryMetadataOptions = 0
goPackage.UseOLEDBServiceComponents = True
goPackage.LogToSQLServer = False
goPackage.LogServerFlags = 0
goPackage.FailPackageOnLogFailure = False
goPackage.ExplicitGlobalVariables = False
goPackage.PackageType = 0


Dim oConnProperty As OleDBProperty
'

' create package connection information

'

Dim oConnection As Connection2
'- a new connection defined below.

oConnection = CType(goPackage.Connections.New("DTSFlatFile"), Connection2)

oConnection.ConnectionProperties.Item("Data Source").Value = "C:\hede\50.txt"
oConnection.ConnectionProperties.Item("Mode").Value = 1
oConnection.ConnectionProperties.Item("Row Delimiter").Value = "||##"
oConnection.ConnectionProperties.Item("File Format").Value = 1
oConnection.ConnectionProperties.Item("Column Delimiter").Value = "|#$,"
oConnection.ConnectionProperties.Item("File Type").Value = 1
oConnection.ConnectionProperties.Item("Skip Rows").Value = 0
oConnection.ConnectionProperties.Item("First Row Column Name").Value() = True
oConnection.ConnectionProperties.Item("Max characters per delimited column").Value = 8000
oConnection.Name = "Connection 1"
oConnection.ID = 1
oConnection.Reusable = True
oConnection.ConnectImmediate = False
oConnection.DataSource = "C:\hede\50.txt"
oConnection.ConnectionTimeout = 60
oConnection.UseTrustedConnection = False
oConnection.UseDSL = False
goPackage.Connections.Add(CType(oConnection, Connection))


oConnection = CType(goPackage.Connections.New("SQLOLEDB"), Connection2)
oConnection.ConnectionProperties.Item("Integrated Security").Value = "SSPI"
oConnection.ConnectionProperties.Item("Persist Security Info").Value() = True
oConnection.ConnectionProperties.Item("Initial Catalog").Value = "**"
oConnection.ConnectionProperties.Item("Data Source").Value = "(local)"
oConnection.ConnectionProperties.Item("Application Name").Value = "DTS Import/Export Wizard"
oConnection.Name = "Connection 2"
oConnection.ID = 2
oConnection.Reusable = True
oConnection.ConnectImmediate = False
oConnection.DataSource = "(local)"
oConnection.UserID = "**"
oConnection.Password = "**"
oConnection.ConnectionTimeout = 60
oConnection.Catalog = "**"
oConnection.UseTrustedConnection = True
oConnection.UseDSL = False
goPackage.Connections.Add(CType(oConnection, Connection))
oConnection = Nothing

'

' create package steps information

'

Dim oStep As Step2
Dim oPrecConstraint As PrecedenceConstraint

oStep = CType(goPackage.Steps.New, Step2)
oStep.Name = "Copy Data from myTextFile to [(local)].[dbo].[111] Step"
oStep.Description = "Copy Data from myTextFile to [(local)].[dbo].[111] Step"
oStep.ExecutionStatus = CType(1, DTSStepExecStatus)
oStep.TaskName = "Copy Data from myTextFile to [(local)].[dbo].[111] Task"
oStep.CommitSuccess = False
oStep.RollbackFailure = False
oStep.ScriptLanguage = "VBScript"
oStep.AddGlobalVariables = True
oStep.RelativePriority = CType(3, DTSStepRelativePriority)
oStep.CloseConnection = False
oStep.ExecuteInMainThread = False
oStep.IsPackageDSORowset = False
oStep.JoinTransactionIfPresent = False
oStep.DisableStep = False
oStep.FailPackageOnError = False
goPackage.Steps.Add(oStep)
oStep = Nothing
goPackage.SaveToSQLServer("(local)", "**", "**", DTSSQLServerStorageFlags.DTSSQLStgFlag_Default, "", "", "")
Try
goPackage.Execute()
Catch ex As Exception
MsgBox(ex.Message)
End Try
End Sub

not have error. try clause is running.but not correct result.

thx..

The Package.Execute method will only thow an exception if it cannot run the package at all, virtual impossible to get. It does not throw an exception if the package fails, as that is still a valid execution.

To capture details of any errors that happend within the package, use the package events provider.

HOW TO: Handle Data Transformation Services Package Events in Visual C# .NET
(http://support.microsoft.com/kb/319985/en-us)

|||

ok i done.

but it didnt have error.

created package in sql server.

but double click on package have error =

Error Source: Microsoft Data Transformation Services(DTS) Package
Error Description: Task 'Copy Data from C:\hede\hede.txt to [(local)].[dbo].[111] Task' was not found.

i want to here : can i do writing Transformation Task Name = Task

Create DTS PACKAGE programmatic

Hi guys..!!

i am working on Dynamic creation of DTS-packages in C#.NET 2005(sql server 200)

but i not must create package in Sql Server.
but i cant...

can i do ?
any ideas ?

thx...

DTS has a Save as VB option. This is a great way of getting sample code, so try that on a demo package. VB to VB.Net has some differences, see this link for some tips.

Converting a DTS Package from Visual Basic 6.0 to Visual Basic .Net
(http://www.sqldts.com/default.aspx?264)

VB.Net to C# should not be hard, plenty of tools that do this.

Hopefully when you view the VB sample code you will get a feel for the object model and how it is used, and going forward you can just write the C# directly.

There is a DTS specific newsgroup (microsoft.public.sqlserver.dts) which may be worth search and posting on, as it is DTS not SSIS focused.

|||

but this source not contain code for vb or vb.net
no problem is writing vb or vb.net

problem is "how to create programmatic (dynamic) DTS-Package in dotnet? "

thx...

|||

You appear to be repeating yourself, so can we try again...

Mehmet Metin Altuntas wrote:

problem is "how to create programmatic (dynamic) DTS-Package in dotnet? "

To create a DTS package dynamically in dotnet you need to write some code. DTS uses an object model, have you added a reference?

Mehmet Metin Altuntas wrote:

but this source not contain code for vb or vb.net

What is not source code? I suggested using the Save as VB option to generate some sample code. If you already know how to use the DTS object model in code, what are you asking? If you do not know how to use the DTS object model in code, try generating some sample code as a guide.

Mehmet Metin Altuntas wrote:

no problem is writing vb or vb.net

Sorry, that does not make sense.

The Save as VB option wil give you VB code. The link told you how to convert this to VB.net. There are tools that convert VB.net to C#. It may be a three stage process but it will give you C# code. Once you are familiar with this you can write c# directly, but to HELP you LEARN how to use it in code, Save as VB is a start point.

Surely some code, even VB is easier to learn from than no code at all. There is no Save As C# option, so learn from the VB.

Any help?

Create DTS Package in SQL server 2005 (Ver:9.0.1116).

Hi,
I am using SQL server 2005 (Ver:9.0.1116).
I am unable to find how to create a DTS package from Sql Server Management Studio.
It is showing "DTS 2000 Packages" in the "Object Explorer" of the Sql Server Management Studio.
I want to know how to start a Integration services in Yukon.
As,the DTS 2000 Packages in the Services tree does not Open nor can Import any package.

Thanks!
TechFreakYou need to use the "Business Intelligence Development Studio" to build SQL Server Integration Services (SSIS) packages, not SQL Server management Studio.

Go to: Start-->Programs-->Microsoft SQL Server 2005-->SQL Server Business Intelligence Development Studio

This is all in the documentation (Books Online) so look in there, and in the tutorials, to see how to go about building your first package.

-Jamie|||Yeah Jamie,

Thanx for the concern..

But using "Business Intelligence Development Studio" also it shows an error message as below:

"Could not load file or assembly 'Microsoft.DataTransformationServices.Wizards' or one of its dependencies.The System cannot find the file specified"

In the Yukon tutorials there is no info provided for Integration Services.

-TechFreak|||

Does anybody has a solution for this? I am getting the same error. I have Visual Studio 2005, SQL Server 2005 (Developer Edition) on Windows 2003 machine. I was trying to create an Integration Services Project, but getting the above error. Please help!

Thanks

|||

even i am getting the same error, any help regarding this ?

Thanks

http://techyfreak.blogspot.com

|||You have to be sure that SQL Server Integration Services installed on your PC.
To check go Help -> About Microsoft Visual Studio.

I got the same error after reinstalled MS Visual Studio 2005 from default location
C:/Program Files/Microsoft Visual Studio 8 to D:/Program Files/Microsoft Visual Studio 8
due to insufficient disk space on C.

SQL Server Integration Services just disappeared from installed list.
I was trying repairing VS from CD. Did not help.
I had to uninstall VS from D to C drive again and leave MSDN on D. After I could start Integration project again.
Why this happened I do not know. May be because MS SQL Server 2005 was still on C drive. Not sure.

I hope this help.

Create DTS Package in SQL server 2005 (Ver:9.0.1116).

Hi,
I am using SQL server 2005 (Ver:9.0.1116).
I am unable to find how to create a DTS package from Sql Server Management Studio.
It is showing "DTS 2000 Packages" in the "Object Explorer" of the Sql Server Management Studio.
I want to know how to start a Integration services in Yukon.
As,the DTS 2000 Packages in the Services tree does not Open nor can Import any package.

Thanks!
TechFreakYou need to use the "Business Intelligence Development Studio" to build SQL Server Integration Services (SSIS) packages, not SQL Server management Studio.

Go to: Start-->Programs-->Microsoft SQL Server 2005-->SQL Server Business Intelligence Development Studio

This is all in the documentation (Books Online) so look in there, and in the tutorials, to see how to go about building your first package.

-Jamie|||Yeah Jamie,

Thanx for the concern..

But using "Business Intelligence Development Studio" also it shows an error message as below:

"Could not load file or assembly 'Microsoft.DataTransformationServices.Wizards' or one of its dependencies.The System cannot find the file specified"

In the Yukon tutorials there is no info provided for Integration Services.

-TechFreak|||

Does anybody has a solution for this? I am getting the same error. I have Visual Studio 2005, SQL Server 2005 (Developer Edition) on Windows 2003 machine. I was trying to create an Integration Services Project, but getting the above error. Please help!

Thanks

|||

even i am getting the same error, any help regarding this ?

Thanks

http://techyfreak.blogspot.com

|||You have to be sure that SQL Server Integration Services installed on your PC.
To check go Help -> About Microsoft Visual Studio.

I got the same error after reinstalled MS Visual Studio 2005 from default location
C:/Program Files/Microsoft Visual Studio 8 to D:/Program Files/Microsoft Visual Studio 8
due to insufficient disk space on C.

SQL Server Integration Services just disappeared from installed list.
I was trying repairing VS from CD. Did not help.
I had to uninstall VS from D to C drive again and leave MSDN on D. After I could start Integration project again.
Why this happened I do not know. May be because MS SQL Server 2005 was still on C drive. Not sure.

I hope this help.|||Try Start>Run> DTSwizard

Create DTS Package in SQL server 2005 (Ver:9.0.1116).

Hi,
I am using SQL server 2005 (Ver:9.0.1116).
I am unable to find how to create a DTS package from Sql Server Management Studio.
It is showing "DTS 2000 Packages" in the "Object Explorer" of the Sql Server Management Studio.
I want to know how to start a Integration services in Yukon.
As,the DTS 2000 Packages in the Services tree does not Open nor can Import any package.

Thanks!
TechFreak
You need to use the "Business Intelligence Development Studio" to build SQL Server Integration Services (SSIS) packages, not SQL Server management Studio.

Go to: Start-->Programs-->Microsoft SQL Server 2005-->SQL Server Business Intelligence Development Studio

This is all in the documentation (Books Online) so look in there, and in the tutorials, to see how to go about building your first package.

-Jamie|||Yeah Jamie,

Thanx for the concern..

But using "Business Intelligence Development Studio" also it shows an error message as below:

"Could not load file or assembly 'Microsoft.DataTransformationServices.Wizards' or one of its dependencies.The System cannot find the file specified"

In the Yukon tutorials there is no info provided for Integration Services.

-TechFreak|||

Does anybody has a solution for this? I am getting the same error. I have Visual Studio 2005, SQL Server 2005 (Developer Edition) on Windows 2003 machine. I was trying to create an Integration Services Project, but getting the above error. Please help!

Thanks

|||

even i am getting the same error, any help regarding this ?

Thanks

http://techyfreak.blogspot.com

|||You have to be sure that SQL Server Integration Services installed on your PC.
To check go Help -> About Microsoft Visual Studio.

I got the same error after reinstalled MS Visual Studio 2005 from default location
C:/Program Files/Microsoft Visual Studio 8 to D:/Program Files/Microsoft Visual Studio 8
due to insufficient disk space on C.

SQL Server Integration Services just disappeared from installed list.
I was trying repairing VS from CD. Did not help.
I had to uninstall VS from D to C drive again and leave MSDN on D. After I could start Integration project again.
Why this happened I do not know. May be because MS SQL Server 2005 was still on C drive. Not sure.

I hope this help.

Create DTS Package in SQL server 2005 (Ver:9.0.1116).

Hi,
I am using SQL server 2005 (Ver:9.0.1116).
I am unable to find how to create a DTS package from Sql Server Management Studio.
It is showing "DTS 2000 Packages" in the "Object Explorer" of the Sql Server Management Studio.
I want to know how to start a Integration services in Yukon.
As,the DTS 2000 Packages in the Services tree does not Open nor can Import any package.

Thanks!
TechFreak
You need to use the "Business Intelligence Development Studio" to build SQL Server Integration Services (SSIS) packages, not SQL Server management Studio.

Go to: Start-->Programs-->Microsoft SQL Server 2005-->SQL Server Business Intelligence Development Studio

This is all in the documentation (Books Online) so look in there, and in the tutorials, to see how to go about building your first package.

-Jamie|||Yeah Jamie,

Thanx for the concern..

But using "Business Intelligence Development Studio" also it shows an error message as below:

"Could not load file or assembly 'Microsoft.DataTransformationServices.Wizards' or one of its dependencies.The System cannot find the file specified"

In the Yukon tutorials there is no info provided for Integration Services.

-TechFreak|||

Does anybody has a solution for this? I am getting the same error. I have Visual Studio 2005, SQL Server 2005 (Developer Edition) on Windows 2003 machine. I was trying to create an Integration Services Project, but getting the above error. Please help!

Thanks

|||

even i am getting the same error, any help regarding this ?

Thanks

http://techyfreak.blogspot.com

|||You have to be sure that SQL Server Integration Services installed on your PC.
To check go Help -> About Microsoft Visual Studio.

I got the same error after reinstalled MS Visual Studio 2005 from default location
C:/Program Files/Microsoft Visual Studio 8 to D:/Program Files/Microsoft Visual Studio 8
due to insufficient disk space on C.

SQL Server Integration Services just disappeared from installed list.
I was trying repairing VS from CD. Did not help.
I had to uninstall VS from D to C drive again and leave MSDN on D. After I could start Integration project again.
Why this happened I do not know. May be because MS SQL Server 2005 was still on C drive. Not sure.

I hope this help.

Friday, February 17, 2012

Create database within SSIS package

I want to create a package that imports data from a Visual Foxpro database to SQL Server 2005 Express database. I used the wizard in BI Development Studio (similar to the DTS in SQL Server 2000) to create a package and noticed that the SQL statements created in the Preparation SQL Task only has code for creating tables. I want to make the package such that it first creates the destination database before creating all the related tables in it! When I tried to edit the SQL code to include DROP DATABASE and/or CREATE DATABASE statements, these were rejected.

Is it possible to do this or do I have to first create the database outside the package and then call the package? I want to make this a seamless process for clients who do not have the know-how of SQL Server database administration.

HELP!!!!!!

Can't you just run a CREATE DATABASE DDL statement in a execute sql task?

|||

Peter K wrote:

Can't you just run a CREATE DATABASE DDL statement in a execute sql task?

yes. i'm afraid that the import/export wizard won't be sufficient to solve this problem.