Generating and Printing Reports

I've created a data flow where I have linked to an OLE DB Source then created a Flat File Destination. My file is now on my c: drive. I'd like to use that data to create a report, then print to a PDF. How would I do that?

Currently I was doing this in Access, but I am moving my processes to SSIS.

You wouldn't use SSIS to do that. SSIS is an ETL tool, not a reporting tool.

-Jamie

|||But if I created my report in Reporting Services for instance, how could I put that in my data flow in SSIS?|||I was also assuming that I could put this in a Script Task, but I didn't know how far I could go with generating a report from there.|||

I don't know what you mean by "put a report in the data flow" or "put it in a script task". Can you expand on that?

There is a way that you can consume a SSIS dataflow from within SSRS but that doesn't seem to be what you're after here. You seem to want to build a report on top of a text file (that just happens to have been created by SSIS). I'm sorry, I don't understand what it is you actually want SSIS to do.

-Jamie

|||

I've gotten my answer:

Write an application in VB using the Report Viewer from the toolbar to create and print the report

Then execute that application from SSIS.

|||

So you're calling the SSRS API, is that correct? If so, you don't have to write another app to do that - you can embed it into SSIS.

-Jamie

|||What do you mean by calling the SSRS API? I'm using Visual Studio 2005.|||

ifaber wrote:

What do you mean by calling the SSRS API? I'm using Visual Studio 2005.

Shall we start again. What exactly is your VB app going to do?

|||My application is going to pull data from many tables, then export to a flat file. Our network person will pick up the files, and put the data on a website. Then from 2 of those tables, I pulled a list of instructors that currently is on our website in PDF reports. In Access, I have pulled the data, created a report and exported to a PDF. Our network person pulls those reports and puts them on the website. It's pretty simple compared to some other stuff I have done.|||

Fair enough, if it works for you that's good. I was just wondering if there was an option to utilise SQL Server Reporting Services (SSRS) seeing as that is a reporting application. I mistakenly assumed that seeing as you were using SSIS that you would be trying to use SSRS for reporting - my mistake. Sorry.

I also thought you were trying to automate the creation of PDF files - something that I suspect could be done from SSRS and ergo from SSIS if there is an API available for doing that. Again it looks like my assumption was wrong.

To me, it seems strange that you would use a differrent application to do all this when it can all be achieved with SSRS but then again I am a SQL Server zealot so I would say that :)

Good luck with it.

-Jamie

|||Wellllll, I know how to use SQL Server Reporting Services too. In fact, I have a lot of reports using SSRS. Pretty much, after I have updated the flat file, I'd like to run something that would create a report and would print to PDF.|||

Right. Well what I was driving at is if SSRS can create PDF reports (and I'm reliably informed that it can) then you can call the SSRS API from SSIS in order to create those reports for you. I haven't actually done it but I'm sure its possible.

-Jamie

|||Bingo!! Now how do I call the API :)|||

ifaber wrote:

Bingo!! Now how do I call the API :)

I was worried you were about to ask that.

I don't actually know, but I've no doubt that you can do it. To know more about the SSRS API you;d be best checking out the SSRS forum.

What I DO know is that SSRS itself is a web service which means that everything that can be done in SSRS can be called via that web service. essentially that web service IS the SSRS API.

You can calls web services from SSIS using the Web Service task. HOWEVER, I am aware that there are limitations with SSIS's web service task (search this forum to find out more) but don't despair because you have another optionavailable to you. You can call web services from within the SSIS script task.using dotnet APIs.

I hope that is useful and I hope you didn't mind me continuing the thread. Its just that you seemed to want to do all from within one package and I figured it would be possible. Anything that can be accessed via dotnet code can be done from SSIS's Script Task..

-Jamie

Generating and directing new rows in PostExecute.

I want to construct a dataset based on all rows passed in from a source and, upon running through all of them, push each dataset record to an output.

Unfortunately, upon calling the AddRow method, I get an "object reference not set to an instance of an object" error. Am I not allowed to create new rows in PostExecute?

Bill,

Can you post your code, indicate which line the error occurs on, and tell us how you have configured the outputs of the component.

-Jamie

|||It errors on reference to a row buffer.

With dsMaterialBuffer
.AddRow()
'Code for row values
End With

I've added the following to check if it's actually defined within PostExecute;
If dsMaterialBuffer Is Nothing Then MsgBox("dsMaterialBuffer is nothing.") 'My row buffer

dsMaterialBuffer, which is the row buffer I'm using, evaluates to "Nothing" and that is where my object reference errors are coming from.

Is it possible that the row buffers are being thrown out once PostExecute hits?

The outputs, by the way, are non-synchronous with standard columns.|||

What is the name of the output as defined in the inputs and outputs tab of the script component editor?

-Jamie

|||dsMaterial|||

Hmm, strange. if you want, drop me an email via here: http://blogs.conchango.com/jamiethomson/contact.aspx and I'll reply so you can send me the package. I can take a look and see if anything jumps out.

If you can build the package so that I am able to run it as well (i.e. not reliant on external data sources, just use a script source component instead) then that'd help.

-Jamie

Generating and directing new rows in PostExecute.

I want to construct a dataset based on all rows passed in from a source and, upon running through all of them, push each dataset record to an output.

Unfortunately, upon calling the AddRow method, I get an "object reference not set to an instance of an object" error. Am I not allowed to create new rows in PostExecute?

Bill,

Can you post your code, indicate which line the error occurs on, and tell us how you have configured the outputs of the component.

-Jamie

|||It errors on reference to a row buffer.

With dsMaterialBuffer
.AddRow()
'Code for row values
End With

I've added the following to check if it's actually defined within PostExecute;
If dsMaterialBuffer Is Nothing Then MsgBox("dsMaterialBuffer is nothing.") 'My row buffer

dsMaterialBuffer, which is the row buffer I'm using, evaluates to "Nothing" and that is where my object reference errors are coming from.

Is it possible that the row buffers are being thrown out once PostExecute hits?

The outputs, by the way, are non-synchronous with standard columns.|||

What is the name of the output as defined in the inputs and outputs tab of the script component editor?

-Jamie

|||dsMaterial|||

Hmm, strange. if you want, drop me an email via here: http://blogs.conchango.com/jamiethomson/contact.aspx and I'll reply so you can send me the package. I can take a look and see if anything jumps out.

If you can build the package so that I am able to run it as well (i.e. not reliant on external data sources, just use a script source component instead) then that'd help.

-Jamie

generate scripts from management studio

Hello all,
Our database gets replaced every day with new tables and data. Basically
the routine job is to retore database from other source database, in which we
get fresh data and tables. However, it will also wipe out all views,
procedures and functions created by developer. So, every day, our developer
will need to generate the scripts before the database get replaced and rerun
the scripts for all views/procedures/functions. The way we generate the
script is from the SQL Server Manager Studio, the problem is, the developer
will need to click the necessary options for the scripts, for instance, she
needs to reset the dependency as true every time she generates the script,
and in some degree, it is riskey, because if she forgot reset certain options
then it will not generate the correct scripts. Is there a way to set the
options on Server Management Studio permanantly? or any other better ideas to
get the functions/views/procedures scripts?
Thanks,
Hi Jenny
There are several ways you may want to get around this. If your stored
procedures, views and functions and are in a source code control system, they
could be extracted and run against the database. This would be better than
storing the source code on disc and just running each of the files using
SQLCMD. If you wish to execute all file in a give directory with osql with a
command like:
for %i in (*.sql) do SQLCMD -E -d Mydb -i %i -o %i.out
An alternative approach would be to rename the existing database, restore
the backup, then use a SSIS package to copy them.
A third approach would be to use SMO instead of using the batch files or
wizards.
John
"Jenny" wrote:

> Hello all,
> Our database gets replaced every day with new tables and data. Basically
> the routine job is to retore database from other source database, in which we
> get fresh data and tables. However, it will also wipe out all views,
> procedures and functions created by developer. So, every day, our developer
> will need to generate the scripts before the database get replaced and rerun
> the scripts for all views/procedures/functions. The way we generate the
> script is from the SQL Server Manager Studio, the problem is, the developer
> will need to click the necessary options for the scripts, for instance, she
> needs to reset the dependency as true every time she generates the script,
> and in some degree, it is riskey, because if she forgot reset certain options
> then it will not generate the correct scripts. Is there a way to set the
> options on Server Management Studio permanantly? or any other better ideas to
> get the functions/views/procedures scripts?
>
> Thanks,
|||Hi John,
I am not quite sure if our developer using source code control system. I
know she is using Visual Studio. So the first way might not work.
The second way you mentioned - rename the database and restore the backup
and then use SSIS package to copy it. It could work tempory, since I will
need to have 2 database capacity. Our database is around 15 G and it is
growing, I will need to watch the space very carefully.
The third one you mentioned maybe will work better, but I don't know how to
use SMO. Do you have a quick way to do the SMO?
Thanks,
Jenny
"John Bell" wrote:
[vbcol=seagreen]
> Hi Jenny
> There are several ways you may want to get around this. If your stored
> procedures, views and functions and are in a source code control system, they
> could be extracted and run against the database. This would be better than
> storing the source code on disc and just running each of the files using
> SQLCMD. If you wish to execute all file in a give directory with osql with a
> command like:
> for %i in (*.sql) do SQLCMD -E -d Mydb -i %i -o %i.out
> An alternative approach would be to rename the existing database, restore
> the backup, then use a SSIS package to copy them.
> A third approach would be to use SMO instead of using the batch files or
> wizards.
> John
> "Jenny" wrote:
|||The source data actually is from a DB2 database. All tables and data are map
to a sql server database (a transition database). Every day the transition
database get backup and then the bakcup is ftp to our server. And then the
retore process get started.
"Tibor Karaszi" wrote:

> Why would you first drop objects if you then restore the database? In case I misunderstood you:
> Write a small app for the script generation. All the script generation liven in the SMO programming
> API, and is really easy to use. See http://www.karaszi.com/SQLServer/info_generate_script.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Jenny" <Jenny@.discussions.microsoft.com> wrote in message
> news:1BFD57F7-1C08-484F-9773-216419ECE254@.microsoft.com...
>
|||Hi Jenny
If you are not using version control, you will not have a process of rolling
back any changes to a known version. Visual Studio has close integration with
source code control systems, particularly Visual Source Safe, therefore it
would not require any effort for you developer to use it other than the
initial configuration.
If you want to limit the space used by the current database, backup the
current database before renaming it, then truncate all the tables and shrink
the data file.
John
John
"Jenny" wrote:
[vbcol=seagreen]
> Hi John,
> I am not quite sure if our developer using source code control system. I
> know she is using Visual Studio. So the first way might not work.
> The second way you mentioned - rename the database and restore the backup
> and then use SSIS package to copy it. It could work tempory, since I will
> need to have 2 database capacity. Our database is around 15 G and it is
> growing, I will need to watch the space very carefully.
> The third one you mentioned maybe will work better, but I don't know how to
> use SMO. Do you have a quick way to do the SMO?
>
> Thanks,
> Jenny
> "John Bell" wrote:

generate scripts from management studio

Hello all,
Our database gets replaced every day with new tables and data. Basically
the routine job is to retore database from other source database, in which we
get fresh data and tables. However, it will also wipe out all views,
procedures and functions created by developer. So, every day, our developer
will need to generate the scripts before the database get replaced and rerun
the scripts for all views/procedures/functions. The way we generate the
script is from the SQL Server Manager Studio, the problem is, the developer
will need to click the necessary options for the scripts, for instance, she
needs to reset the dependency as true every time she generates the script,
and in some degree, it is riskey, because if she forgot reset certain options
then it will not generate the correct scripts. Is there a way to set the
options on Server Management Studio permanantly? or any other better ideas to
get the functions/views/procedures scripts?
Thanks,Why would you first drop objects if you then restore the database? In case I misunderstood you:
Write a small app for the script generation. All the script generation liven in the SMO programming
API, and is really easy to use. See http://www.karaszi.com/SQLServer/info_generate_script.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jenny" <Jenny@.discussions.microsoft.com> wrote in message
news:1BFD57F7-1C08-484F-9773-216419ECE254@.microsoft.com...
> Hello all,
> Our database gets replaced every day with new tables and data. Basically
> the routine job is to retore database from other source database, in which we
> get fresh data and tables. However, it will also wipe out all views,
> procedures and functions created by developer. So, every day, our developer
> will need to generate the scripts before the database get replaced and rerun
> the scripts for all views/procedures/functions. The way we generate the
> script is from the SQL Server Manager Studio, the problem is, the developer
> will need to click the necessary options for the scripts, for instance, she
> needs to reset the dependency as true every time she generates the script,
> and in some degree, it is riskey, because if she forgot reset certain options
> then it will not generate the correct scripts. Is there a way to set the
> options on Server Management Studio permanantly? or any other better ideas to
> get the functions/views/procedures scripts?
>
> Thanks,|||Hi Jenny
There are several ways you may want to get around this. If your stored
procedures, views and functions and are in a source code control system, they
could be extracted and run against the database. This would be better than
storing the source code on disc and just running each of the files using
SQLCMD. If you wish to execute all file in a give directory with osql with a
command like:
for %i in (*.sql) do SQLCMD -E -d Mydb -i %i -o %i.out
An alternative approach would be to rename the existing database, restore
the backup, then use a SSIS package to copy them.
A third approach would be to use SMO instead of using the batch files or
wizards.
John
"Jenny" wrote:
> Hello all,
> Our database gets replaced every day with new tables and data. Basically
> the routine job is to retore database from other source database, in which we
> get fresh data and tables. However, it will also wipe out all views,
> procedures and functions created by developer. So, every day, our developer
> will need to generate the scripts before the database get replaced and rerun
> the scripts for all views/procedures/functions. The way we generate the
> script is from the SQL Server Manager Studio, the problem is, the developer
> will need to click the necessary options for the scripts, for instance, she
> needs to reset the dependency as true every time she generates the script,
> and in some degree, it is riskey, because if she forgot reset certain options
> then it will not generate the correct scripts. Is there a way to set the
> options on Server Management Studio permanantly? or any other better ideas to
> get the functions/views/procedures scripts?
>
> Thanks,|||Hi John,
I am not quite sure if our developer using source code control system. I
know she is using Visual Studio. So the first way might not work.
The second way you mentioned - rename the database and restore the backup
and then use SSIS package to copy it. It could work tempory, since I will
need to have 2 database capacity. Our database is around 15 G and it is
growing, I will need to watch the space very carefully.
The third one you mentioned maybe will work better, but I don't know how to
use SMO. Do you have a quick way to do the SMO?
Thanks,
Jenny
"John Bell" wrote:
> Hi Jenny
> There are several ways you may want to get around this. If your stored
> procedures, views and functions and are in a source code control system, they
> could be extracted and run against the database. This would be better than
> storing the source code on disc and just running each of the files using
> SQLCMD. If you wish to execute all file in a give directory with osql with a
> command like:
> for %i in (*.sql) do SQLCMD -E -d Mydb -i %i -o %i.out
> An alternative approach would be to rename the existing database, restore
> the backup, then use a SSIS package to copy them.
> A third approach would be to use SMO instead of using the batch files or
> wizards.
> John
> "Jenny" wrote:
> > Hello all,
> >
> > Our database gets replaced every day with new tables and data. Basically
> > the routine job is to retore database from other source database, in which we
> > get fresh data and tables. However, it will also wipe out all views,
> > procedures and functions created by developer. So, every day, our developer
> > will need to generate the scripts before the database get replaced and rerun
> > the scripts for all views/procedures/functions. The way we generate the
> > script is from the SQL Server Manager Studio, the problem is, the developer
> > will need to click the necessary options for the scripts, for instance, she
> > needs to reset the dependency as true every time she generates the script,
> > and in some degree, it is riskey, because if she forgot reset certain options
> > then it will not generate the correct scripts. Is there a way to set the
> > options on Server Management Studio permanantly? or any other better ideas to
> > get the functions/views/procedures scripts?
> >
> >
> >
> > Thanks,|||The source data actually is from a DB2 database. All tables and data are map
to a sql server database (a transition database). Every day the transition
database get backup and then the bakcup is ftp to our server. And then the
retore process get started.
"Tibor Karaszi" wrote:
> Why would you first drop objects if you then restore the database? In case I misunderstood you:
> Write a small app for the script generation. All the script generation liven in the SMO programming
> API, and is really easy to use. See http://www.karaszi.com/SQLServer/info_generate_script.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Jenny" <Jenny@.discussions.microsoft.com> wrote in message
> news:1BFD57F7-1C08-484F-9773-216419ECE254@.microsoft.com...
> > Hello all,
> >
> > Our database gets replaced every day with new tables and data. Basically
> > the routine job is to retore database from other source database, in which we
> > get fresh data and tables. However, it will also wipe out all views,
> > procedures and functions created by developer. So, every day, our developer
> > will need to generate the scripts before the database get replaced and rerun
> > the scripts for all views/procedures/functions. The way we generate the
> > script is from the SQL Server Manager Studio, the problem is, the developer
> > will need to click the necessary options for the scripts, for instance, she
> > needs to reset the dependency as true every time she generates the script,
> > and in some degree, it is riskey, because if she forgot reset certain options
> > then it will not generate the correct scripts. Is there a way to set the
> > options on Server Management Studio permanantly? or any other better ideas to
> > get the functions/views/procedures scripts?
> >
> >
> >
> > Thanks,
>|||Hi Jenny
If you are not using version control, you will not have a process of rolling
back any changes to a known version. Visual Studio has close integration with
source code control systems, particularly Visual Source Safe, therefore it
would not require any effort for you developer to use it other than the
initial configuration.
If you want to limit the space used by the current database, backup the
current database before renaming it, then truncate all the tables and shrink
the data file.
John
John
"Jenny" wrote:
> Hi John,
> I am not quite sure if our developer using source code control system. I
> know she is using Visual Studio. So the first way might not work.
> The second way you mentioned - rename the database and restore the backup
> and then use SSIS package to copy it. It could work tempory, since I will
> need to have 2 database capacity. Our database is around 15 G and it is
> growing, I will need to watch the space very carefully.
> The third one you mentioned maybe will work better, but I don't know how to
> use SMO. Do you have a quick way to do the SMO?
>
> Thanks,
> Jenny
> "John Bell" wrote:
> > Hi Jenny
> >
> > There are several ways you may want to get around this. If your stored
> > procedures, views and functions and are in a source code control system, they
> > could be extracted and run against the database. This would be better than
> > storing the source code on disc and just running each of the files using
> > SQLCMD. If you wish to execute all file in a give directory with osql with a
> > command like:
> > for %i in (*.sql) do SQLCMD -E -d Mydb -i %i -o %i.out
> >
> > An alternative approach would be to rename the existing database, restore
> > the backup, then use a SSIS package to copy them.
> >
> > A third approach would be to use SMO instead of using the batch files or
> > wizards.
> >
> > John
> >
> > "Jenny" wrote:
> >
> > > Hello all,
> > >
> > > Our database gets replaced every day with new tables and data. Basically
> > > the routine job is to retore database from other source database, in which we
> > > get fresh data and tables. However, it will also wipe out all views,
> > > procedures and functions created by developer. So, every day, our developer
> > > will need to generate the scripts before the database get replaced and rerun
> > > the scripts for all views/procedures/functions. The way we generate the
> > > script is from the SQL Server Manager Studio, the problem is, the developer
> > > will need to click the necessary options for the scripts, for instance, she
> > > needs to reset the dependency as true every time she generates the script,
> > > and in some degree, it is riskey, because if she forgot reset certain options
> > > then it will not generate the correct scripts. Is there a way to set the
> > > options on Server Management Studio permanantly? or any other better ideas to
> > > get the functions/views/procedures scripts?
> > >
> > >
> > >
> > > Thanks,

generate scripts from management studio

Hello all,
Our database gets replaced every day with new tables and data. Basically
the routine job is to retore database from other source database, in which w
e
get fresh data and tables. However, it will also wipe out all views,
procedures and functions created by developer. So, every day, our developer
will need to generate the scripts before the database get replaced and rerun
the scripts for all views/procedures/functions. The way we generate the
script is from the SQL Server Manager Studio, the problem is, the developer
will need to click the necessary options for the scripts, for instance, she
needs to reset the dependency as true every time she generates the script,
and in some degree, it is riskey, because if she forgot reset certain option
s
then it will not generate the correct scripts. Is there a way to set the
options on Server Management Studio permanantly? or any other better ideas t
o
get the functions/views/procedures scripts?
Thanks,Why would you first drop objects if you then restore the database? In case I
misunderstood you:
Write a small app for the script generation. All the script generation liven
in the SMO programming
API, and is really easy to use. See http://www.karaszi.com/SQLServer/in.../>
_script.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jenny" <Jenny@.discussions.microsoft.com> wrote in message
news:1BFD57F7-1C08-484F-9773-216419ECE254@.microsoft.com...
> Hello all,
> Our database gets replaced every day with new tables and data. Basically
> the routine job is to retore database from other source database, in which
we
> get fresh data and tables. However, it will also wipe out all views,
> procedures and functions created by developer. So, every day, our develop
er
> will need to generate the scripts before the database get replaced and rer
un
> the scripts for all views/procedures/functions. The way we generate the
> script is from the SQL Server Manager Studio, the problem is, the develope
r
> will need to click the necessary options for the scripts, for instance, sh
e
> needs to reset the dependency as true every time she generates the script,
> and in some degree, it is riskey, because if she forgot reset certain opti
ons
> then it will not generate the correct scripts. Is there a way to set the
> options on Server Management Studio permanantly? or any other better ideas
to
> get the functions/views/procedures scripts?
>
> Thanks,|||Hi Jenny
There are several ways you may want to get around this. If your stored
procedures, views and functions and are in a source code control system, the
y
could be extracted and run against the database. This would be better than
storing the source code on disc and just running each of the files using
SQLCMD. If you wish to execute all file in a give directory with osql with a
command like:
for %i in (*.sql) do SQLCMD -E -d Mydb -i %i -o %i.out
An alternative approach would be to rename the existing database, restore
the backup, then use a SSIS package to copy them.
A third approach would be to use SMO instead of using the batch files or
wizards.
John
"Jenny" wrote:

> Hello all,
> Our database gets replaced every day with new tables and data. Basically
> the routine job is to retore database from other source database, in which
we
> get fresh data and tables. However, it will also wipe out all views,
> procedures and functions created by developer. So, every day, our develop
er
> will need to generate the scripts before the database get replaced and rer
un
> the scripts for all views/procedures/functions. The way we generate the
> script is from the SQL Server Manager Studio, the problem is, the develope
r
> will need to click the necessary options for the scripts, for instance, sh
e
> needs to reset the dependency as true every time she generates the script,
> and in some degree, it is riskey, because if she forgot reset certain opti
ons
> then it will not generate the correct scripts. Is there a way to set the
> options on Server Management Studio permanantly? or any other better ideas
to
> get the functions/views/procedures scripts?
>
> Thanks,|||Hi John,
I am not quite sure if our developer using source code control system. I
know she is using Visual Studio. So the first way might not work.
The second way you mentioned - rename the database and restore the backup
and then use SSIS package to copy it. It could work tempory, since I will
need to have 2 database capacity. Our database is around 15 G and it is
growing, I will need to watch the space very carefully.
The third one you mentioned maybe will work better, but I don't know how to
use SMO. Do you have a quick way to do the SMO?
Thanks,
Jenny
"John Bell" wrote:
[vbcol=seagreen]
> Hi Jenny
> There are several ways you may want to get around this. If your stored
> procedures, views and functions and are in a source code control system, t
hey
> could be extracted and run against the database. This would be better than
> storing the source code on disc and just running each of the files using
> SQLCMD. If you wish to execute all file in a give directory with osql with
a
> command like:
> for %i in (*.sql) do SQLCMD -E -d Mydb -i %i -o %i.out
> An alternative approach would be to rename the existing database, restore
> the backup, then use a SSIS package to copy them.
> A third approach would be to use SMO instead of using the batch files or
> wizards.
> John
> "Jenny" wrote:
>|||The source data actually is from a DB2 database. All tables and data are ma
p
to a sql server database (a transition database). Every day the transition
database get backup and then the bakcup is ftp to our server. And then the
retore process get started.
"Tibor Karaszi" wrote:

> Why would you first drop objects if you then restore the database? In case
I misunderstood you:
> Write a small app for the script generation. All the script generation liv
en in the SMO programming
> API, and is really easy to use. See http://www.karaszi.com/SQLServer/in...
te_script.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Jenny" <Jenny@.discussions.microsoft.com> wrote in message
> news:1BFD57F7-1C08-484F-9773-216419ECE254@.microsoft.com...
>|||Hi Jenny
If you are not using version control, you will not have a process of rolling
back any changes to a known version. Visual Studio has close integration wit
h
source code control systems, particularly Visual Source Safe, therefore it
would not require any effort for you developer to use it other than the
initial configuration.
If you want to limit the space used by the current database, backup the
current database before renaming it, then truncate all the tables and shrink
the data file.
John
John
"Jenny" wrote:
[vbcol=seagreen]
> Hi John,
> I am not quite sure if our developer using source code control system. I
> know she is using Visual Studio. So the first way might not work.
> The second way you mentioned - rename the database and restore the backup
> and then use SSIS package to copy it. It could work tempory, since I will
> need to have 2 database capacity. Our database is around 15 G and it is
> growing, I will need to watch the space very carefully.
> The third one you mentioned maybe will work better, but I don't know how t
o
> use SMO. Do you have a quick way to do the SMO?
>
> Thanks,
> Jenny
> "John Bell" wrote:
>

Generate report using XML as data source

Hi
How can I generate report using XML file as Datasource?
And I need to pass XML Filename dynamically at run-time..
--
Thanks in advance
BhaveshToday you have to write a data extension. In the future (Yukon) there will
be controls that can be used and it should be significantly easier to do
this sort of thing (load a dataset with the xml data and pass that to the
control).
Bruce L-C
"Bhavesh" <Bhavesh@.discussions.microsoft.com> wrote in message
news:1ED00147-3CAB-4515-A722-1D943AE2C574@.microsoft.com...
> Hi
> How can I generate report using XML file as Datasource?
> And I need to pass XML Filename dynamically at run-time..
> --
> Thanks in advance
> Bhavesh|||Pass to which Control?
I am reading XML data in dataset, in my asp page and passing it to Crystal
report control..and everything is working fine..
But I want to do this using SQL Server reporting service..
How can I do this?
Thanks
Bhavesh
"Bruce Loehle-Conger" wrote:
> Today you have to write a data extension. In the future (Yukon) there will
> be controls that can be used and it should be significantly easier to do
> this sort of thing (load a dataset with the xml data and pass that to the
> control).
> Bruce L-C
> "Bhavesh" <Bhavesh@.discussions.microsoft.com> wrote in message
> news:1ED00147-3CAB-4515-A722-1D943AE2C574@.microsoft.com...
> > Hi
> > How can I generate report using XML file as Datasource?
> >
> > And I need to pass XML Filename dynamically at run-time..
> >
> > --
> > Thanks in advance
> > Bhavesh
>
>|||What I am saying is that with the shipping product you have to create a data
extension. Read up in bol. Version 2 of RS (ships with Yukon, the next
version of SQL Server) will have controls (web and winform) so you can do it
the way you are thinking about.
Another alternative to a data extension is to rethinking where the work is
done. Have the data extraction occur within RS and then integrate in using
either URL integration or Web services.
Bruce L-C
"Bhavesh" <Bhavesh@.discussions.microsoft.com> wrote in message
news:D7E6E9F7-ECFC-493C-9FA5-9F63FDBC241D@.microsoft.com...
> Pass to which Control?
> I am reading XML data in dataset, in my asp page and passing it to Crystal
> report control..and everything is working fine..
> But I want to do this using SQL Server reporting service..
> How can I do this?
> Thanks
> Bhavesh
> "Bruce Loehle-Conger" wrote:
> > Today you have to write a data extension. In the future (Yukon) there
will
> > be controls that can be used and it should be significantly easier to do
> > this sort of thing (load a dataset with the xml data and pass that to
the
> > control).
> >
> > Bruce L-C
> >
> > "Bhavesh" <Bhavesh@.discussions.microsoft.com> wrote in message
> > news:1ED00147-3CAB-4515-A722-1D943AE2C574@.microsoft.com...
> > > Hi
> > > How can I generate report using XML file as Datasource?
> > >
> > > And I need to pass XML Filename dynamically at run-time..
> > >
> > > --
> > > Thanks in advance
> > > Bhavesh
> >
> >
> >|||Thanks Bruce..
"Bruce Loehle-Conger" wrote:
> What I am saying is that with the shipping product you have to create a data
> extension. Read up in bol. Version 2 of RS (ships with Yukon, the next
> version of SQL Server) will have controls (web and winform) so you can do it
> the way you are thinking about.
> Another alternative to a data extension is to rethinking where the work is
> done. Have the data extraction occur within RS and then integrate in using
> either URL integration or Web services.
> Bruce L-C
> "Bhavesh" <Bhavesh@.discussions.microsoft.com> wrote in message
> news:D7E6E9F7-ECFC-493C-9FA5-9F63FDBC241D@.microsoft.com...
> > Pass to which Control?
> > I am reading XML data in dataset, in my asp page and passing it to Crystal
> > report control..and everything is working fine..
> >
> > But I want to do this using SQL Server reporting service..
> > How can I do this?
> >
> > Thanks
> > Bhavesh
> >
> > "Bruce Loehle-Conger" wrote:
> >
> > > Today you have to write a data extension. In the future (Yukon) there
> will
> > > be controls that can be used and it should be significantly easier to do
> > > this sort of thing (load a dataset with the xml data and pass that to
> the
> > > control).
> > >
> > > Bruce L-C
> > >
> > > "Bhavesh" <Bhavesh@.discussions.microsoft.com> wrote in message
> > > news:1ED00147-3CAB-4515-A722-1D943AE2C574@.microsoft.com...
> > > > Hi
> > > > How can I generate report using XML file as Datasource?
> > > >
> > > > And I need to pass XML Filename dynamically at run-time..
> > > >
> > > > --
> > > > Thanks in advance
> > > > Bhavesh
> > >
> > >
> > >
>
>

generate file task with 2 files

Hi Guys,

I've one Dafta flow task where I'm getting data from OleDb source and then doing some scripting using script component and then generating a file.

Now I would need to get the same data and apply some different things and generate another file.
Can I used this same task for doing the secondry work? If yes how woulld I put the thing in place, I would need to get the same data but I would need to use a seperate scripting and generate a seperate file?

TA

Gemma

You can use a multicast transformation to split your dataflow up into two or more flows. If you add a multicast right after your OLE DB source, you can then move your data to two script components each connected to their own file destination.

OLESRC
|
MC
/ \
S S
/ \
FD FD