Showing posts with label export. Show all posts
Showing posts with label export. 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 Dev Studio - export the grid in Dimension Usage tab?

Is anyone aware of a simple way to export the grid (or similar contents) from the Dimension Usage tab in the cube designer?

I imagine it can be done by parsing the XML definition of the cube, but I'm not much of developer with that sort of thing, and I wondered if there's a simple way or a not-so-simple-but-already-written way to get this. I'm not picky about formatting (spreadsheet, text, whatever -- anything but a bitmap screenshot!).

Does anyone else think this would be a handy self documenting feature?

Thanks,

CJB

Keep an eye on http://www.codeplex.com/bidshelper as that feature should be posted within the next week or two. Basically it's going to spit out a print-friendly version of that dimension usage tab.|||I have an early release of this working on my machine at the moment. It prints out using nested groups rather than the matrix that you see in the report usage tab, but most of the info is in there. If you are interested in having a look at an early version contact me via my blog. Otherwise as Greg says, we should have a release out in the next week or two.|||

Thanks, I will keep an eye on that. I poked around on the codeplex projects that you and Mr. Gosbell are working on. I cringed at how much cooler it all is than anything I've put together.

I'm still climbing a .NET learning curve, which wasn't really necessary for me until recently -- as the use of SQL 2005 has begun to mature a bit, and the ease of integrating assemblies into SQL and SSAS has become so slick now, it's too valuable to ignore.

Sunday, February 12, 2012

Best way to export data.

Hello,

I have some questions on my options available.

I have to export some tables to csv files to enable another department
to process the files. What I need is a way to do this in ms sql
though a stored proc with quoted identifiers and column names as
heads. I cannot figure out how to do this.

Can anybody give me some options that would be the best options.

I am using ms sql 2000.

Thank you for your time.On Apr 9, 7:27 am, "Designing Solutions WD"
<michael.grass...@.gmail.comwrote:

Quote:

Originally Posted by

Hello,
>
I have some questions on my options available.
>
I have to export some tables to csv files to enable another department
to process the files. What I need is a way to do this in ms sql
though a stored proc with quoted identifiers and column names as
heads. I cannot figure out how to do this.
>
Can anybody give me some options that would be the best options.
>
I am using ms sql 2000.
>
Thank you for your time.


The easiest solution that came to my head is to execute DTS package in
command shell. In DTS package you can define whatever format you want.
Create it. Debug it. Play with it. Then just add xp_cmdshell
'dtsrun.exe -S<server-N<dts-package-E -M<dts-password>' to your
procedure.

- Roman|||On Apr 9, 7:27 am, "Designing Solutions WD"
<michael.grass...@.gmail.comwrote:

Quote:

Originally Posted by

Hello,
>
I have some questions on my options available.
>
I have to export some tables to csv files to enable another department
to process the files. What I need is a way to do this in ms sql
though a stored proc with quoted identifiers and column names as
heads. I cannot figure out how to do this.
>
Can anybody give me some options that would be the best options.
>
I am using ms sql 2000.
>
Thank you for your time.


Straight forward solution is to UNION field names with data and use
BCP -

1. Create a SELECT statement that includes field names -
DECLARE @.names varchar(100), @.delimiter varchar(10)
SET @.delimiter = ','
SELECT @.names = COALESCE(@.names + @.delimiter, '') + '"' + name + '"'
FROM syscolumns where id = (select id from sysobjects where
name='TABLE_TO_EXPORT')

SELECT 'select ' + @.names

2. Concatenate it with UNION SELECT cast(FIELD1 as char), cast(FIELD2
as char), ... From TABLE_TO_EXPORT (which is ugly but it has to be
done to create union)

3. Then using UNION create a VIEW which can be used in BCP to export
data

4. Use BCP from command shell xp_cmdshell "BCP ""select * from
VIEW_TO_EXPORT"" out c:\results.csv -c -t, -T -S<servername>

- Roman

Friday, February 10, 2012

Best way to capture/export about 45 fields - 3000 records

I am new to SQL server 2005 and trying to help a charity org move selected kids data out of a POS SQL POS database.

There are maybe 65 tables (only 5 - 7 tables will apply that will contain the 45 fields that I need). About 3000 records need to filtered to create a new database.

Ideally, with the small amout of data I actually need, we thought it would be best to just pump t into Excel so that I can pass the data to the charity where they can scrub the data themselves. We would then pump it into an online app that likes Excel imports.

After restoring the data sucessfully from a .bak file I am now failing miserably at converting a few tables with data into Excel even though it appeared to be straightforward. HELP please?

Can some experienced folks maybe help me out with a good plan?

Quote:

Originally Posted by computerchick

I am new to SQL server 2005 and trying to help a charity org move selected kids data out of a POS SQL POS database.

There are maybe 65 tables (only 5 - 7 tables will apply that will contain the 45 fields that I need). About 3000 records need to filtered to create a new database.

Ideally, with the small amout of data I actually need, we thought it would be best to just pump t into Excel so that I can pass the data to the charity where they can scrub the data themselves. We would then pump it into an online app that likes Excel imports.

After restoring the data sucessfully from a .bak file I am now failing miserably at converting a few tables with data into Excel even though it appeared to be straightforward. HELP please?

Can some experienced folks maybe help me out with a good plan?


There are a number of ways.

One is (if you need it only once) to query the tables in Query Analyzer (to a grid), then copy/paste into Excel. (You will lose the header row, though.)

Another one is to use an ODBC connection to the SQL database from Excel and retrieve the data from an "External data source".

The third one is that you use MS Access, pull the data into it (either from the source, or through ODBC), then export the tables into Excel.

If you need it regularly I suggest the second one; we have been using it widely.|||You can try the IMPORT/EXPORT Wizard which is quite easy to use.

Aash.|||Thank you for mucho for responding - it is much appreciated. What happened was that some of the tables were in am "incompatible format". I did end up getting it ported to Excel 2007 which in turn worked like a charm porting it into all other data formats as well. Yea! A process that works! :)

Quote:

Originally Posted by azimmer

There are a number of ways.

One is (if you need it only once) to query the tables in Query Analyzer (to a grid), then copy/paste into Excel. (You will lose the header row, though.)

Another one is to use an ODBC connection to the SQL database from Excel and retrieve the data from an "External data source".

The third one is that you use MS Access, pull the data into it (either from the source, or through ODBC), then export the tables into Excel.

If you need it regularly I suggest the second one; we have been using it widely.

|||Thank you too - that is what I was using but it would not work on the specific formatting applied to a few of my tables (the first time I had a corrupt bak file - woe is me! I did get it resolved after a bit of head banging!

Quote:

Originally Posted by patelaashish

You can try the IMPORT/EXPORT Wizard which is quite easy to use.

Aash.