ITW wont save script file

Hi all,

I am running the ITW against several trace files that were created from a single trace file. I only have the following problem when attempting to save the script file from the analysis of any one of the multiple trace files. I have used the ITW against single trace files with no problem.

Here's the problem:
Everything works fine until I select the "Save Script File" option. After selecting this option, designating a file name to save to, and then clicking the "Next" button, the application appears to hang up. It displays an hourglass pointer, as though it is working, but just sits there forever. Also, when I look at the task manager this application reports that it is "not responding". I have allowed it to sit there in this state for several hours before finaly killing the process. Is there some additional configuration or method required to analyze multiple trace files from a single trace session?

Any suggestions would be greatly appreciated.

Thanks,
RickThis could be a bug. You might want to contact PSS.

Issues with moving existing single production server setup to a New Cluster installation

According to the documentation the chosen Cluster name and IP address need
to be unused before installing the cluster. The IP address is not a problem,
but it will be a difficult task with the Cluster Name as the business
processes have many scripts, DTS packages, stored procedures and views that
have the production server name hard coded. There are many other servers
involved for updating and transferring data, so there was no way around it
and I would like to keep it that way if possible.
Therefore, my question is how can I reuse the production server name for the
cluster without jeopardising the Cluster installation ?
Hello,
You may need to rename the current production server name "ServerA" to
another name before installing virtual server. After that, you could reuse
the name "ServerA" as the virtual server name.
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||You can't, however there are a lot of workarounds. If you are in an AD/DNS
envorinment, you can create an alias record that points the old name to the
new server. You can also set up a SQL alias on each client, but that is
generally harder.
Geoff N. Hiten
Microsoft SQL Server MVP
"GMG" <nospam@.nospam.com> wrote in message
news:uNQ4jV6dFHA.4060@.TK2MSFTNGP10.phx.gbl...
> According to the documentation the chosen Cluster name and IP address need
> to be unused before installing the cluster. The IP address is not a
> problem,
> but it will be a difficult task with the Cluster Name as the business
> processes have many scripts, DTS packages, stored procedures and views
> that
> have the production server name hard coded. There are many other servers
> involved for updating and transferring data, so there was no way around it
> and I would like to keep it that way if possible.
> Therefore, my question is how can I reuse the production server name for
> the
> cluster without jeopardising the Cluster installation ?
>

Issue with the ForEachLoop Task in SSIS

Hi,

I am using a SQL task to execute a stored procedure which returns a single field with multiple records. I want the records returned by the stored procedure to be processed one by one within a ForEachLoop container. How do I assign the records one by one to one variable and use it in a Script task running inside the ForEachLoop container.

I am using 2 tasks in my package.

In my first task I call a SQL task that executes a stored procedure which returns a list of reference numbers (TrackData). This works perfectly.

However, in my second task I must use the ForEachLoop task to loop through the above list and set the value of var_TrackData (a user variable declared by me) with the value of the TrackData present in it during that particular loop.

I am not sure how to go about the second task. Any help would be greatly appreciated.

Create an object variable.

In the execute sql task set the resultset to the variable name (set result name to 0).

Create a variable to hold the reference numbers (int or string?)

Create a for each loop task

Set the collection to for each ADO enumerator

Set the ADO object source variable to your object variable name (which contains the resultset).

In variable mappings set the variable to the variable name you created to hold the reference numbers

Set the precednce so that the execute sql runs before the for each llop.

Now when this runs the object variable will be set to the resultset the the for each loop will itterate through it setting the variable to the reference number for each loop.

|||

See if this post gives you some idea of how you can do it:

http://rafael-salas.blogspot.com/2006/12/import-header-line-tables-into-dynamic_22.html

Issue with restoring master db

Hi all,

I am trying to restore my master database to a new server in sql 2000. I have started sql in single user mode from the command line and connected to enterprise manager and attempted to do the restore. I also tried query analyzer and used the restore database from disk ='file path of backup' used the move option with the correct file path and on both counts received the same error message...

Error: 9001, Severity: 21, State: 1.
Error: 3151, Severity: 21, State: 0.

Any ideas? The connection is then broken (which I would expect anyway as restoring master shuts down sql but, I checked and it has not restored the db)

Thanks!This article may be of some help:

http://www.dbarecovery.com/restoremasterdb.html|||lmao @. your sig ... rdjabarov ... nice one !!!|||That is mostly what I have done (did not need to do the rebuild part) When I try to do the restore it does not complete but generates the error messages I listed in my first posting. I have done this before and it worked but, for some reason it is not allowing me to do the restore but, is breaking the connection.

Any other suggestions?|||I did some more checking - could there be an issue with one server having a windows service pack 3 and the other server having windows service pack 4?

Issue with Page Breaking

I'm having an issue with Page Breaks within a SQL Report. The report
consisting of a single table with two groups. The report is setup to
insert a page break after the first group. Grand totals are calculated
in the footer of the main table. The report renders correctly in HTML.
When the report is exported to PDF, the Grand Totals section is render
on it's own page. The Grand Totals should render right after the last
group on the report. Is there a way in SQL Reporting to prevent the
last page break on a report?
Report Group Layout
Single table containing the the following:
Table Header
Group Header 1 - Page Break after group
Group Header 2
Detail Row -
Group Footer 2 - Contains Subtotals
Group Footer 1 - Contains Subtotals
Table Footer - Grand Total
Thanks
ChadHi, make sure that the page width and height is big enough for the 2nd page
to fit in. In layout, go to Report, Report Properties, Layout. Play around
with the Page Width and Page Height (increasing height most likely) until you
come right.
"Chad McKee" wrote:
> I'm having an issue with Page Breaks within a SQL Report. The report
> consisting of a single table with two groups. The report is setup to
> insert a page break after the first group. Grand totals are calculated
> in the footer of the main table. The report renders correctly in HTML.
> When the report is exported to PDF, the Grand Totals section is render
> on it's own page. The Grand Totals should render right after the last
> group on the report. Is there a way in SQL Reporting to prevent the
> last page break on a report?
>
> Report Group Layout
> Single table containing the the following:
> Table Header
> Group Header 1 - Page Break after group
> Group Header 2
> Detail Row -
> Group Footer 2 - Contains Subtotals
> Group Footer 1 - Contains Subtotals
> Table Footer - Grand Total
> Thanks
> Chad
>|||Hello,
I have checked the Page Width and Height. Everything fits within the
page size. If I remove the "Page Break after group" on the first group.
Everything renders without the extra page break. I think something is
wrong with the "Page Break after group" when rendering to PDF.
Thanks
Chad
jagberg wrote:
> Hi, make sure that the page width and height is big enough for the 2nd page
> to fit in. In layout, go to Report, Report Properties, Layout. Play around
> with the Page Width and Page Height (increasing height most likely) until you
> come right.
> "Chad McKee" wrote:
>
>>I'm having an issue with Page Breaks within a SQL Report. The report
>>consisting of a single table with two groups. The report is setup to
>>insert a page break after the first group. Grand totals are calculated
>>in the footer of the main table. The report renders correctly in HTML.
>> When the report is exported to PDF, the Grand Totals section is render
>>on it's own page. The Grand Totals should render right after the last
>>group on the report. Is there a way in SQL Reporting to prevent the
>>last page break on a report?
>>
>>Report Group Layout
>>Single table containing the the following:
>>Table Header
>> Group Header 1 - Page Break after group
>> Group Header 2
>> Detail Row -
>> Group Footer 2 - Contains Subtotals
>> Group Footer 1 - Contains Subtotals
>>Table Footer - Grand Total
>>Thanks
>>Chad|||This is a known limitation in our PDF renderer. I don't know of a
workaround, though someone more creative than me in this group might have
one up their sleeves. :)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chad McKee" <cmckee@.startech-comp.com> wrote in message
news:uTHDB67MFHA.1172@.TK2MSFTNGP12.phx.gbl...
> I'm having an issue with Page Breaks within a SQL Report. The report
> consisting of a single table with two groups. The report is setup to
> insert a page break after the first group. Grand totals are calculated in
> the footer of the main table. The report renders correctly in HTML. When
> the report is exported to PDF, the Grand Totals section is render on it's
> own page. The Grand Totals should render right after the last group on
> the report. Is there a way in SQL Reporting to prevent the last page
> break on a report?
>
> Report Group Layout
> Single table containing the the following:
> Table Header
> Group Header 1 - Page Break after group
> Group Header 2
> Detail Row -
> Group Footer 2 - Contains Subtotals
> Group Footer 1 - Contains Subtotals
> Table Footer - Grand Total
> Thanks
> Chad|||Hello Donovan,
Thanks for the reply. Do you know if/when this issue is going to be
fixed? Will the fix be included within the next Service Pack for
Reporting Services.
Thanks
Chad
Donovan Smith [MSFT] wrote:
> This is a known limitation in our PDF renderer. I don't know of a
> workaround, though someone more creative than me in this group might have
> one up their sleeves. :)
>|||Sorry, this won't make it into RS 2000 SP2 and is not currently on our plate
for Yukon (RS 2005).
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chad McKee" <cmckee@.startech-comp.com> wrote in message
news:425ACA37.5090704@.startech-comp.com...
> Hello Donovan,
> Thanks for the reply. Do you know if/when this issue is going to be
> fixed? Will the fix be included within the next Service Pack for
> Reporting Services.
> Thanks
> Chad
> Donovan Smith [MSFT] wrote:
>> This is a known limitation in our PDF renderer. I don't know of a
>> workaround, though someone more creative than me in this group might have
>> one up their sleeves. :)|||Hi Donovan,
Do you know where I can find a workaround for this problem?
Thanks
Chad
Donovan Smith [MSFT] wrote:
> Sorry, this won't make it into RS 2000 SP2 and is not currently on our plate
> for Yukon (RS 2005).
>|||I am encountering a similar problem when displaying/printing a .pdf file from
a report containing a sub report. I have tried placing the sub report in both
rectangles and lists. I've adjusted all the margins (left, right, top and
bottom) to 0 in the sub report. There is a property called KeepTogether in a
list which I've set to both true and false without any impact. I can't seem
to find any property of any control that enables text in a sub report to span
multiple pages. I've also played with the page width and page height of the
sub report to no avail. Any help would be appreciated
"Chad McKee" wrote:
> Hi Donovan,
> Do you know where I can find a workaround for this problem?
> Thanks
> Chad
> Donovan Smith [MSFT] wrote:
> > Sorry, this won't make it into RS 2000 SP2 and is not currently on our plate
> > for Yukon (RS 2005).
> >
>|||Sorry, no. It's a limitation with our renderer. I don't have a creative
RDL solution though someone else in this group might.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chad McKee" <cmckee@.startech-comp.com> wrote in message
news:425AD6E0.9000201@.startech-comp.com...
> Hi Donovan,
> Do you know where I can find a workaround for this problem?
> Thanks
> Chad
> Donovan Smith [MSFT] wrote:
>> Sorry, this won't make it into RS 2000 SP2 and is not currently on our
>> plate for Yukon (RS 2005).|||Donovan with all due respect this issue should be easy to resolve. It's a
simple conditional check to render the table footer output on last page
following a group break.
I suspect that literally 1000's if not 10,000's of your customers are going
to be having the same issues since this is a very common scenario. If that's
justification enough for giving this a higher priority I don't know what is.
Send me the source code and I would be glad to fix... and I'm being serious!
Regards,
Kevin Weir
OmniLogic Systems
www.omnilogic.net
"Donovan Smith [MSFT]" wrote:
> Sorry, no. It's a limitation with our renderer. I don't have a creative
> RDL solution though someone else in this group might.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Chad McKee" <cmckee@.startech-comp.com> wrote in message
> news:425AD6E0.9000201@.startech-comp.com...
> > Hi Donovan,
> >
> > Do you know where I can find a workaround for this problem?
> >
> > Thanks
> > Chad
> >
> > Donovan Smith [MSFT] wrote:
> >> Sorry, this won't make it into RS 2000 SP2 and is not currently on our
> >> plate for Yukon (RS 2005).
> >>
>
>|||I agree with Kevin. Its a very common practice to have page breaks
after groups in a report containing a grand total. I just ran into the
issue again with a different report yesterday. This should be moved up
the priority list.
By the way. There is no way of working around the issue since you can't
place expressions on the page break property.
Thanks
Chad
Kevin Weir wrote:
> Donovan with all due respect this issue should be easy to resolve. It's a
> simple conditional check to render the table footer output on last page
> following a group break.
> I suspect that literally 1000's if not 10,000's of your customers are going
> to be having the same issues since this is a very common scenario. If that's
> justification enough for giving this a higher priority I don't know what is.
> Send me the source code and I would be glad to fix... and I'm being serious!
> Regards,
> Kevin Weir
> OmniLogic Systems
> www.omnilogic.net
>
> "Donovan Smith [MSFT]" wrote:
>
>>Sorry, no. It's a limitation with our renderer. I don't have a creative
>>RDL solution though someone else in this group might.
>>--
>>This posting is provided "AS IS" with no warranties, and confers no rights.
>>
>>"Chad McKee" <cmckee@.startech-comp.com> wrote in message
>>news:425AD6E0.9000201@.startech-comp.com...
>>Hi Donovan,
>>Do you know where I can find a workaround for this problem?
>>Thanks
>>Chad
>>Donovan Smith [MSFT] wrote:
>>Sorry, this won't make it into RS 2000 SP2 and is not currently on our
>>plate for Yukon (RS 2005).
>>
>>|||I Thought I'd chime in with another vote for pushing this to the top of the
request heap. It is the main issue we've had with RS. We were going to
migrate all our reports from Crystal until we found grouping/page break
problems. I guess we'll keep writing Crystal / Business Objects until
Microsoft wakes up and realizes that this issue is a deal breaker. Even the
lowly Access Report Writer has this built in.
"Chad McKee" wrote:
> I agree with Kevin. Its a very common practice to have page breaks
> after groups in a report containing a grand total. I just ran into the
> issue again with a different report yesterday. This should be moved up
> the priority list.
> By the way. There is no way of working around the issue since you can't
> place expressions on the page break property.
> Thanks
> Chad
> Kevin Weir wrote:
> > Donovan with all due respect this issue should be easy to resolve. It's a
> > simple conditional check to render the table footer output on last page
> > following a group break.
> >
> > I suspect that literally 1000's if not 10,000's of your customers are going
> > to be having the same issues since this is a very common scenario. If that's
> > justification enough for giving this a higher priority I don't know what is.
> > Send me the source code and I would be glad to fix... and I'm being serious!
> >
> > Regards,
> > Kevin Weir
> > OmniLogic Systems
> > www.omnilogic.net
> >
> >
> >
> > "Donovan Smith [MSFT]" wrote:
> >
> >
> >>Sorry, no. It's a limitation with our renderer. I don't have a creative
> >>RDL solution though someone else in this group might.
> >>
> >>--
> >>This posting is provided "AS IS" with no warranties, and confers no rights.
> >>
> >>
> >>"Chad McKee" <cmckee@.startech-comp.com> wrote in message
> >>news:425AD6E0.9000201@.startech-comp.com...
> >>
> >>Hi Donovan,
> >>
> >>Do you know where I can find a workaround for this problem?
> >>
> >>Thanks
> >>Chad
> >>
> >>Donovan Smith [MSFT] wrote:
> >>
> >>Sorry, this won't make it into RS 2000 SP2 and is not currently on our
> >>plate for Yukon (RS 2005).
> >>
> >>
> >>
> >>
>|||Hi guys I have had this issue with this.
I have discoverd two work arounds for this
1. Put everything in the group headers and simply don't use the group
footers. The extra page breaks problem vanish. I rather have Totals in the
footers below the detail but this avoids the problem
OR
2. Select the Repeat Group Footers on each page option (which looks a
little crowded) but will give your report a little "running total" look to
it.The extra page breaks problem vanishs once again.
--
Message posted via http://www.sqlmonster.com|||We really shouldn't have to preform work arounds for functionally like
page breaking. These work arounds may work in some situations, but not
all. Here is another instant of breaking not working.
I have a report that contains four tables. The second to the last table
has the page break at start set to true. The report renders correctly
and inserts page breaks in the correct places.
Now I need to add an expression to the table's visible property to hide
the table on specific records. The expression works, but when the table
is visible the page break is ignored. I'm not sure why an expression on
the visible property causes the page breaks to stop working.
There seem to be issues with page breaks in general.
Thanks
Chad
Paul Mauriello via SQLMonster.com wrote:
> Hi guys I have had this issue with this.
> I have discoverd two work arounds for this
> 1. Put everything in the group headers and simply don't use the group
> footers. The extra page breaks problem vanish. I rather have Totals in the
> footers below the detail but this avoids the problem
> OR
> 2. Select the Repeat Group Footers on each page option (which looks a
> little crowded) but will give your report a little "running total" look to
> it.The extra page breaks problem vanishs once again.
>|||I use a workaround to do RunningValue counts over a group and then show
the GrandTotal on the last page when the RunningValue count for the
recordset equals the Count of all records in the recordset.
This is an unacceptable workaround for this product. Grand Totals
should have the "Keep Together" option with the last group. This is
seriously slowing down development.