Showing posts with label build. Show all posts
Showing posts with label build. Show all posts

Monday, March 19, 2012

BIDS programming

Hi,

I want to create a wizard to help build my packages for certain situations, something like the export and import wizard.

I couldn't find the API to do it. can you help?

Thanks

Noa

Search Books Online for Integration Services Programming.

Lots o' content there.

K

|||

Can you be more specific?

I only found programming custom components to SSIS, not a wizard to ease use.

|||

SQL Server Books Online does not have documentation on programming your own Wizard application. I think that you'll find some information on this in the Visual Studio documentation.

As for creating a package programmatically -- which is what you want your wizard to do, as I understand -- you will find sections in BOL on "Building Packages Programmatically" and "Building the Data Flow Programmatically" to get you started.

We are all learners when it comes to the vast and flexible new Integration Services APIs.

-Doug

|||

Noa wrote:

Can you be more specific?

I only found programming custom components to SSIS, not a wizard to ease use.

You will need general VS documentation. See topics VsWizard Interface, IDTWizard Inteface.

Also there is a topic Walkthrough: Creating a Wizard in Dev Tools & Languages > VS > IDE > Customizing and Automating the Development Environment > Automation and Extensibility for Visual Studio > Creating Add-ins and Wizards.

BIDS programming

Hi,

I want to create a wizard to help build my packages for certain situations, something like the export and import wizard.

I couldn't find the API to do it. can you help?

Thanks

Noa

Search Books Online for Integration Services Programming.

Lots o' content there.

K

|||

Can you be more specific?

I only found programming custom components to SSIS, not a wizard to ease use.

|||

SQL Server Books Online does not have documentation on programming your own Wizard application. I think that you'll find some information on this in the Visual Studio documentation.

As for creating a package programmatically -- which is what you want your wizard to do, as I understand -- you will find sections in BOL on "Building Packages Programmatically" and "Building the Data Flow Programmatically" to get you started.

We are all learners when it comes to the vast and flexible new Integration Services APIs.

-Doug

|||

Noa wrote:

Can you be more specific?

I only found programming custom components to SSIS, not a wizard to ease use.

You will need general VS documentation. See topics VsWizard Interface, IDTWizard Inteface.

Also there is a topic Walkthrough: Creating a Wizard in Dev Tools & Languages > VS > IDE > Customizing and Automating the Development Environment > Automation and Extensibility for Visual Studio > Creating Add-ins and Wizards.

Thursday, March 8, 2012

BI Application & SQL Server Express Edition

I was wondering whether anyone could enlighten me:
We currently build DB apps with a jet engine DB and c# Windows Form front end.
We wish to develop client windows form apps that can be installed on client PCs, which will have an SQL Server back-end and windows form Front End. However the apps we want to build are BI application using cubes we generate (in Analysis Services).
Now am I right in saying that we cannot develop an application that can be installed on a customer site that would include SQL Server Expres AND have the BI functionality? We wish to build a tool for customers that allows them to slice and dice data we provide

It is a pre-requisite that we must not assume that they have access to the internet and we cannot assume that they have an SQL Server which we could automatically install our product onto (to allow for BI functionailty).
So far all the tools we seen and the end-to-end applications, tend to refer to a pre-exisitng installation of SQL Server (with Analysis Services) e.g. Programmming SQL Server 2005 - Microsoft Press.
We need to create custom apps that can "stand alone". Is there any solution?

First. Analysis Services component of the Microsoft SQL Server 2005 product is not part of the Express Edition. It is part of any other edition of SQL Server ( except may be for the mobile edition )

This doesnt mean you cannot install Express and Standard editions of SQL Server side.

Now there is wide range of functionality supported by Analysis Services. You have to figure out what you would like to provide your users with.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Saturday, February 25, 2012

Better way to build a stored proc for an INSERT...

I've built a stored procedure where I'm inserting a row into two tables.
Both tables have a number of columns - and so I have to pass a rather larger
number of parameters to the stored proc. Like follows
INSERT INTO MyTable1 (MyCol1, MyCol2, ... MyCol25) VALUES (@.cParm1, @.cParm2,
... @.cParm25)
INSERT INTO MyTable2 (MyCol1, MyCol2, ... MyCol25) VALUES (@.cParm26,
@.cParm27, ... @.cParm50)
For any one row, however, at least a third of the columns are going to be
NULL, based on the value of one of the columns (a category column).
There's no opportunity to modify the table structure - it is what it is.
What I have "works", but I'm curious if there's a way that doesn't involve
as many parameters.
Thanks,
KevinKevin@.test.com wrote:
> I've built a stored procedure where I'm inserting a row into two
> tables.
> Both tables have a number of columns - and so I have to pass a rather
> larger number of parameters to the stored proc. Like follows
> INSERT INTO MyTable1 (MyCol1, MyCol2, ... MyCol25) VALUES (@.cParm1,
> @.cParm2, ... @.cParm25)
> INSERT INTO MyTable2 (MyCol1, MyCol2, ... MyCol25) VALUES (@.cParm26,
> @.cParm27, ... @.cParm50)
>
> For any one row, however, at least a third of the columns are going
> to be NULL, based on the value of one of the columns (a category
> column).
> There's no opportunity to modify the table structure - it is what it
> is. What I have "works", but I'm curious if there's a way that
> doesn't involve as many parameters.
>
> Thanks,
> Kevin
Write separate stored procedures for each "insert" type. So, let's say
your table has three logical implementations (design-issues aside), you
can write three separate insert SPs that only require the user pass
those that are asked.
The other option is to use defaults on the parameters, so if they are
not passed they default to an appropriate value:
Create Proc Test
@.Param1 INT = NULL
@.Param2 INT = NULL
as
Exec dbo.Test @.Param2 = 5
Exec dbo.Test @.Param1 = 3
Exec dbo.Test 1, 3
Exec dbo.Test
You may have to add some validation to the SP in the case where a user
leaves out a logically incorrect number of columns.
David Gugick
Imceda Software
www.imceda.com|||David,
Thanks!...you've given me some good ideas to seriously consider, especially
having 3 stored procs.
Kevin