Precompile Script task programatically

I have code which generates packages programatically, and script task is a part of the control flow. I've succeded to set source code programatically, but I do not know how to put binary code, because I need to have my script task precompiled.

Just setting PreCompile = true does not solve this problem

Thanks in advance.

Borko

Unfortunately, due to interactions with VSA (the script editing environment) this is not possible in this version.

Precedence puzzle

Hello folks,

I have probably a dumb newbie question but I can't find the answer anywhere.

On my Control Flow design pane I have two objects: a SQL task object and a Data flow task object. The first 'points' to the second. From my digging I believed that by indicating with the arrow from 1 to 2 that 1 would execute to finish before 2 was started.

My SQL taks is to truncate a table to receive the new data coming from the data flow task object. Instead 2 executes first and then 1. You can imagine producing an empty table was not my goal for this package.

Can anybody give me a clue?

Thanks....

Jim

That's very strange. If there is a precedence constraint pointing FROM the Exec SQL Task TO the Data-flow Task then the Exec SQL Task should execute first.

Are you sure that is how it is setup?

-Jamie

|||

Yes, that's the setup. Do you have to do anything other than drag the arrow from the Execute SQL Task to the Data Flow Task in order for precedence to be followed?

Jim

|||Are you sure they are executed in this order? How do you determine this?

I would try setting pre-execute breakpoint in designer (select the task, click F9, repeat for second task) and see what is the execution order, what happens to the tables after each step, etc.|||

Two clues tell me the steps are running out of order. First watching the process pane as it executes always shows the SQL task executing second and the end result of the package run is an empty data set.

I will try the break point to see what happens. Thanks for the tip.

|||Unfortunately, progress pane can be confusing. It groups the events from tasks under one node, and the order is determined by the order of the first events from the task. So if data flow task is validated first, it will appear above the SQL task (the validation order is not affected by precedence constraints).|||Just curious. Does your source table have any data?
Make sure its not empty.|||

That sounds like what I was seeing and just got paranoid. I set break pionts as suggested in an earlier post and confirmed the order of execution.

Thanks to all for your help!

PostBack while selecting a parameter

Hi,

I'm working on a report having 2 date parameters(which uses calendar control) and a dropdownlist. But on selecting each of these parameters, the page refreshes. For eg On selecting a date from the calendar control results in a postback. The same is the case with the dropdownlist. Could you please help to resolve this issue? We need the postback to happen only on clicking the 'View Report' button.

Also, is there any way to customize the 'View Report' button. It always appears in the right hand side. Can we set the position of this button so that it appears just below the paging button?

Thanks in advance,

Sonu.

1. No, it's not possible to avoid postbacks when you enter parameters one by one.

2. There is no way to customize the position of the button but you can change the style of the button in your report manager by using the ReportingServices.css file in the following folder (probably):

C:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\ReportManager\Styles

Please refer to more details in the following link:

http://msdn2.microsoft.com/en-us/library/ms345247.aspx

Shyam

sql

Possible to use Calendar control with date parameter?

SQL 2005 on XP Pro.
I want to call up a Calendar Control when a user enters a report parameter which is a date. Is this possible? I am using the out-of-the-box SQL Srvr Reporting Services, not a custom implementation.

Thanks in advanceThis is supported. A calendar control will be displayed for date parameters that do not have a valid values list.|||

Calender control comes automatically once you define a report parameter as datetime.

Amarnath

Possible to Limit the Export Formats

Is it possible to limit the export formats from the Report Viewer control? Specifically the options that appear in the dropdown box. I'm using it in an ASP.NET environment (RTM) and remote mode of the ReportViewer control.
In remote mode, we can edit the rsreportserver.config file on the Report Server to limit the available export formats but that will enforce for all the reporting applications running on that machine.
Can we restrict it for one of the reporting application deployed on the reporting Services and not for all?

Unfortunately the list is not customizable. You can, however, hide the dropdown entirely and add your own to the form that includes only the formats you want. You can programmatically access to all available rendering extensions through ReportViewer.LocalReport.Render().

Possible to display RTF from db? Is there a control?

I'd like to save RTF (or html, possibly) in a memo field of a table then display that as formatted text on a report. Can this be done? I've used a control (RTFedit) in Access to do this, though the results were mixed. I need to display tables with formatting.

Thanks in advance

Hello,

There is currently no way to do this with Reporting Services. We are considering adding a rich-text report control in a future version.

Thanks,
Chris

|||

Ok, so this is a really late reply, but in the event you still need it, or someone else out there is having the same problem, refer to my walkthrough in this thread http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=738557&SiteID=1

Possible to display RTF from db? Is there a control?

I'd like to save RTF (or html, possibly) in a memo field of a table then display that as formatted text on a report. Can this be done? I've used a control (RTFedit) in Access to do this, though the results were mixed. I need to display tables with formatting.

Thanks in advance

Hello,

There is currently no way to do this with Reporting Services. We are considering adding a rich-text report control in a future version.

Thanks,
Chris

|||

Ok, so this is a really late reply, but in the event you still need it, or someone else out there is having the same problem, refer to my walkthrough in this thread http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=738557&SiteID=1

Possible to add a Flash Player control to a report?

I'm working on a project where the client wants us to create custom charts which have features not found in the standard Reporting Services charts. I would like to use flash to build this and have found an existing flash charting package for which I have the code and which I plan to expand.

Here's the problem:

The client wants to include these charts in his Reports. Is there some way to add a flash control to a report so that it will appear on the web page as a fully-functional flash presentation, which can then be included when printing or exporting?

The alternative, would be to figure out some means of generating the chart using flash outside of the report, exporting a bitmap of the chart and then saving the bitmap to a known location on the file system so It can be referenced by a report. This has some serious complications, and may not be feasible.

Any ideas?

Embedding flash into reports is not supported. While there are several third party advanced charting packages available which specifically integrate with SSRS2005 Standard, Enterprise, or Developer editions (based on the CustomReportItem extensibility feature), they also cannot use flash because it is currently not supported.

-- Robert

Possible Solution to Keeping Log Size Under Control During INDEXDEFRAG

If I just backed up the log to a network drive every 15 minutes or so
during an INDEXDEFRAG wouldn't that keep the file size under control? I
have an extensive defrag that I've only been able to get partially
through because of space and I figure this will let me run it completely
in one shot.
Hi Brad,
Backing up the transaction log at regular intervals during an INDEXDEFRAG
will indeed prevent you from running out of transaction log space. DBCC
INDEXDEFRAG, in contrast to DBCC DBREINDEX, uses a large number of small
transactions to reorganise the indexes. So there are no long running
transaction that will prevent the transaction log from being emptied when it
is backed up.
Jacco Schalkwijk
SQL Server MVP
"Brad" <brad@.seesigifthere.com> wrote in message
news:MPG.1b76bd01ae8a965e989685@.news...
> If I just backed up the log to a network drive every 15 minutes or so
> during an INDEXDEFRAG wouldn't that keep the file size under control? I
> have an extensive defrag that I've only been able to get partially
> through because of space and I figure this will let me run it completely
> in one shot.
|||Brad,
Since IndexDefrag uses a lot of small transactions you can certainly backup
the log during it to keep it's size reasonable. But how much gets logged
and how fast depends on the fragmentation level of the Index and the
hardware your running it on. As such it is hard to say whether 15 minutes
is appropriate or not. Only you can determine that with testing. Most
people run log backups every 15 minutes or less anyway. Since your
apparently doing log backups at fairly long intervals I assume it is not
that busy of a system. If that is the case you might consider doing a
DBREINDEX every few days or once a week to keep the fragmentation down. You
can do indexdefrags in between if necessary. You might want to check this
out:
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx
Andrew J. Kelly SQL MVP
"Brad" <brad@.seesigifthere.com> wrote in message
news:MPG.1b76bd01ae8a965e989685@.news...
> If I just backed up the log to a network drive every 15 minutes or so
> during an INDEXDEFRAG wouldn't that keep the file size under control? I
> have an extensive defrag that I've only been able to get partially
> through because of space and I figure this will let me run it completely
> in one shot.
|||In article <Oy7PTC9dEHA.3964@.TK2MSFTNGP10.phx.gbl>,
sqlmvpnooospam@.shadhawk.com says...

> "Brad" <brad@.seesigifthere.com> wrote in message
> news:MPG.1b76bd01ae8a965e989685@.news...
> Since IndexDefrag uses a lot of small transactions you can certainly backup
> the log during it to keep it's size reasonable. But how much gets logged
> and how fast depends on the fragmentation level of the Index and the
> hardware your running it on. As such it is hard to say whether 15 minutes
> is appropriate or not. Only you can determine that with testing. Most
> people run log backups every 15 minutes or less anyway. Since your
> apparently doing log backups at fairly long intervals I assume it is not
> that busy of a system. If that is the case you might consider doing a
> DBREINDEX every few days or once a week to keep the fragmentation down. You
> can do indexdefrags in between if necessary. You might want to check this
> out:
> http://www.microsoft.com/technet/pro.../ss2kidbp.mspx
It actually is a very busy system, but we are in the process of changing
our backup strategy. Right now I am rolling my own log shipping (since
it's standard and not enterprise), but I am still doing the backups
manually to oversee the process.
The main reason I'm doing the log shipping myself is that the standby
server only has web connectivity into the environment, so I have a
process that backs up the log on the production server, zips it up and
tells the standby server that the log is ready. The standby then pulls
down the zipped log with wget, unzips it and applies it to the local
database. It's working pretty well.
|||Tying to guess the appropriate log backup interval may require a lot of
trial and error.
There may be an easier way. You can set up an alert that fires whenever the
log file reaches a specified % (try maybe 60%). When it fires, the alert
can be configured to execute a job that backs up the log file.
Mark
"Brad" <brad@.seesigifthere.com> wrote in message
news:MPG.1b76bd01ae8a965e989685@.news...
> If I just backed up the log to a network drive every 15 minutes or so
> during an INDEXDEFRAG wouldn't that keep the file size under control? I
> have an extensive defrag that I've only been able to get partially
> through because of space and I figure this will let me run it completely
> in one shot.
|||Oops, sorry about the "from" name. Just set up my newsgroups on a new
computer and did not configure that correctly.
Mark
"msnews.microsoft.com" <nosapm@.nospam.com> wrote in message
news:ujNUzGDeEHA.1048@.tk2msftngp13.phx.gbl...
> Tying to guess the appropriate log backup interval may require a lot of
> trial and error.
> There may be an easier way. You can set up an alert that fires whenever
the
> log file reaches a specified % (try maybe 60%). When it fires, the alert
> can be configured to execute a job that backs up the log file.
> Mark
> "Brad" <brad@.seesigifthere.com> wrote in message
> news:MPG.1b76bd01ae8a965e989685@.news...
>

Possible Solution to Keeping Log Size Under Control During INDEXDEFRAG

If I just backed up the log to a network drive every 15 minutes or so
during an INDEXDEFRAG wouldn't that keep the file size under control? I
have an extensive defrag that I've only been able to get partially
through because of space and I figure this will let me run it completely
in one shot.Hi Brad,
Backing up the transaction log at regular intervals during an INDEXDEFRAG
will indeed prevent you from running out of transaction log space. DBCC
INDEXDEFRAG, in contrast to DBCC DBREINDEX, uses a large number of small
transactions to reorganise the indexes. So there are no long running
transaction that will prevent the transaction log from being emptied when it
is backed up.
--
Jacco Schalkwijk
SQL Server MVP
"Brad" <brad@.seesigifthere.com> wrote in message
news:MPG.1b76bd01ae8a965e989685@.news...
> If I just backed up the log to a network drive every 15 minutes or so
> during an INDEXDEFRAG wouldn't that keep the file size under control? I
> have an extensive defrag that I've only been able to get partially
> through because of space and I figure this will let me run it completely
> in one shot.|||Brad,
Since IndexDefrag uses a lot of small transactions you can certainly backup
the log during it to keep it's size reasonable. But how much gets logged
and how fast depends on the fragmentation level of the Index and the
hardware your running it on. As such it is hard to say whether 15 minutes
is appropriate or not. Only you can determine that with testing. Most
people run log backups every 15 minutes or less anyway. Since your
apparently doing log backups at fairly long intervals I assume it is not
that busy of a system. If that is the case you might consider doing a
DBREINDEX every few days or once a week to keep the fragmentation down. You
can do indexdefrags in between if necessary. You might want to check this
out:
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
Andrew J. Kelly SQL MVP
"Brad" <brad@.seesigifthere.com> wrote in message
news:MPG.1b76bd01ae8a965e989685@.news...
> If I just backed up the log to a network drive every 15 minutes or so
> during an INDEXDEFRAG wouldn't that keep the file size under control? I
> have an extensive defrag that I've only been able to get partially
> through because of space and I figure this will let me run it completely
> in one shot.|||In article <Oy7PTC9dEHA.3964@.TK2MSFTNGP10.phx.gbl>,
sqlmvpnooospam@.shadhawk.com says...
> "Brad" <brad@.seesigifthere.com> wrote in message
> news:MPG.1b76bd01ae8a965e989685@.news...
> > If I just backed up the log to a network drive every 15 minutes or so
> > during an INDEXDEFRAG wouldn't that keep the file size under control? I
> > have an extensive defrag that I've only been able to get partially
> > through because of space and I figure this will let me run it completely
> > in one shot.
> Since IndexDefrag uses a lot of small transactions you can certainly backup
> the log during it to keep it's size reasonable. But how much gets logged
> and how fast depends on the fragmentation level of the Index and the
> hardware your running it on. As such it is hard to say whether 15 minutes
> is appropriate or not. Only you can determine that with testing. Most
> people run log backups every 15 minutes or less anyway. Since your
> apparently doing log backups at fairly long intervals I assume it is not
> that busy of a system. If that is the case you might consider doing a
> DBREINDEX every few days or once a week to keep the fragmentation down. You
> can do indexdefrags in between if necessary. You might want to check this
> out:
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
It actually is a very busy system, but we are in the process of changing
our backup strategy. Right now I am rolling my own log shipping (since
it's standard and not enterprise), but I am still doing the backups
manually to oversee the process.
The main reason I'm doing the log shipping myself is that the standby
server only has web connectivity into the environment, so I have a
process that backs up the log on the production server, zips it up and
tells the standby server that the log is ready. The standby then pulls
down the zipped log with wget, unzips it and applies it to the local
database. It's working pretty well.|||Tying to guess the appropriate log backup interval may require a lot of
trial and error.
There may be an easier way. You can set up an alert that fires whenever the
log file reaches a specified % (try maybe 60%). When it fires, the alert
can be configured to execute a job that backs up the log file.
Mark
"Brad" <brad@.seesigifthere.com> wrote in message
news:MPG.1b76bd01ae8a965e989685@.news...
> If I just backed up the log to a network drive every 15 minutes or so
> during an INDEXDEFRAG wouldn't that keep the file size under control? I
> have an extensive defrag that I've only been able to get partially
> through because of space and I figure this will let me run it completely
> in one shot.|||Oops, sorry about the "from" name. Just set up my newsgroups on a new
computer and did not configure that correctly.
Mark
"msnews.microsoft.com" <nosapm@.nospam.com> wrote in message
news:ujNUzGDeEHA.1048@.tk2msftngp13.phx.gbl...
> Tying to guess the appropriate log backup interval may require a lot of
> trial and error.
> There may be an easier way. You can set up an alert that fires whenever
the
> log file reaches a specified % (try maybe 60%). When it fires, the alert
> can be configured to execute a job that backs up the log file.
> Mark
> "Brad" <brad@.seesigifthere.com> wrote in message
> news:MPG.1b76bd01ae8a965e989685@.news...
> > If I just backed up the log to a network drive every 15 minutes or so
> > during an INDEXDEFRAG wouldn't that keep the file size under control? I
> > have an extensive defrag that I've only been able to get partially
> > through because of space and I figure this will let me run it completely
> > in one shot.
>

Possible Solution to Keeping Log Size Under Control During INDEXDEFRAG

If I just backed up the log to a network drive every 15 minutes or so
during an INDEXDEFRAG wouldn't that keep the file size under control? I
have an extensive defrag that I've only been able to get partially
through because of space and I figure this will let me run it completely
in one shot.Hi Brad,
Backing up the transaction log at regular intervals during an INDEXDEFRAG
will indeed prevent you from running out of transaction log space. DBCC
INDEXDEFRAG, in contrast to DBCC DBREINDEX, uses a large number of small
transactions to reorganise the indexes. So there are no long running
transaction that will prevent the transaction log from being emptied when it
is backed up.
Jacco Schalkwijk
SQL Server MVP
"Brad" <brad@.seesigifthere.com> wrote in message
news:MPG.1b76bd01ae8a965e989685@.news...
> If I just backed up the log to a network drive every 15 minutes or so
> during an INDEXDEFRAG wouldn't that keep the file size under control? I
> have an extensive defrag that I've only been able to get partially
> through because of space and I figure this will let me run it completely
> in one shot.|||Brad,
Since IndexDefrag uses a lot of small transactions you can certainly backup
the log during it to keep it's size reasonable. But how much gets logged
and how fast depends on the fragmentation level of the Index and the
hardware your running it on. As such it is hard to say whether 15 minutes
is appropriate or not. Only you can determine that with testing. Most
people run log backups every 15 minutes or less anyway. Since your
apparently doing log backups at fairly long intervals I assume it is not
that busy of a system. If that is the case you might consider doing a
DBREINDEX every few days or once a week to keep the fragmentation down. You
can do indexdefrags in between if necessary. You might want to check this
out:
http://www.microsoft.com/technet/pr...n/ss2kidbp.mspx
Andrew J. Kelly SQL MVP
"Brad" <brad@.seesigifthere.com> wrote in message
news:MPG.1b76bd01ae8a965e989685@.news...
> If I just backed up the log to a network drive every 15 minutes or so
> during an INDEXDEFRAG wouldn't that keep the file size under control? I
> have an extensive defrag that I've only been able to get partially
> through because of space and I figure this will let me run it completely
> in one shot.|||In article <Oy7PTC9dEHA.3964@.TK2MSFTNGP10.phx.gbl>,
sqlmvpnooospam@.shadhawk.com says...
[vbcol=seagreen]
> "Brad" <brad@.seesigifthere.com> wrote in message
> news:MPG.1b76bd01ae8a965e989685@.news...
> Since IndexDefrag uses a lot of small transactions you can certainly backu
p
> the log during it to keep it's size reasonable. But how much gets logged
> and how fast depends on the fragmentation level of the Index and the
> hardware your running it on. As such it is hard to say whether 15 minutes
> is appropriate or not. Only you can determine that with testing. Most
> people run log backups every 15 minutes or less anyway. Since your
> apparently doing log backups at fairly long intervals I assume it is not
> that busy of a system. If that is the case you might consider doing a
> DBREINDEX every few days or once a week to keep the fragmentation down. Y
ou
> can do indexdefrags in between if necessary. You might want to check this
> out:
> http://www.microsoft.com/technet/pr...n/ss2kidbp.mspx[/vbco
l]
It actually is a very busy system, but we are in the process of changing
our backup strategy. Right now I am rolling my own log shipping (since
it's standard and not enterprise), but I am still doing the backups
manually to oversee the process.
The main reason I'm doing the log shipping myself is that the standby
server only has web connectivity into the environment, so I have a
process that backs up the log on the production server, zips it up and
tells the standby server that the log is ready. The standby then pulls
down the zipped log with wget, unzips it and applies it to the local
database. It's working pretty well.|||Tying to guess the appropriate log backup interval may require a lot of
trial and error.
There may be an easier way. You can set up an alert that fires whenever the
log file reaches a specified % (try maybe 60%). When it fires, the alert
can be configured to execute a job that backs up the log file.
Mark
"Brad" <brad@.seesigifthere.com> wrote in message
news:MPG.1b76bd01ae8a965e989685@.news...
> If I just backed up the log to a network drive every 15 minutes or so
> during an INDEXDEFRAG wouldn't that keep the file size under control? I
> have an extensive defrag that I've only been able to get partially
> through because of space and I figure this will let me run it completely
> in one shot.|||Oops, sorry about the "from" name. Just set up my newsgroups on a new
computer and did not configure that correctly.
Mark
"msnews.microsoft.com" <nosapm@.nospam.com> wrote in message
news:ujNUzGDeEHA.1048@.tk2msftngp13.phx.gbl...
> Tying to guess the appropriate log backup interval may require a lot of
> trial and error.
> There may be an easier way. You can set up an alert that fires whenever
the
> log file reaches a specified % (try maybe 60%). When it fires, the alert
> can be configured to execute a job that backs up the log file.
> Mark
> "Brad" <brad@.seesigifthere.com> wrote in message
> news:MPG.1b76bd01ae8a965e989685@.news...
>

Ports used by ReportViewer web controls

When a ReportViewer control is used to access a report on a remote SQL Server database, on what ports does the communcation occur? Does the control communicate on on the SQL Server ports of 1433 and 1434 or does it communcate as a web service on port 80 (or 443 for HTPPS)?It will depend on the url that you set for the report server. For a standard url it will use 80 (and 443), however you can always pass in a url for a non-standard port.