I created three datasets. Every one has the same parameter and I need to link
them together. How to do it?
Thx.You can create a global report parameter and link it to the parameters in
your query. See the sample Sales Invoice report included in the RS samples.
--
HTH,
---
Teo Lachev, MVP, MCSD, MCT
"Microsoft Reporting Services in Action"
"Applied Microsoft Analysis Services 2005"
Home page and blog: http://www.prologika.com/
---
"Mia" <Mia@.discussions.microsoft.com> wrote in message
news:5DD6DD82-8A1B-4C36-B6BC-13F2C3FF9554@.microsoft.com...
>I created three datasets. Every one has the same parameter and I need to
>link
> them together. How to do it?
> Thx.|||Where do I find these sample reports?
I can't find any mention of global report parameters in BOL
"Teo Lachev [MVP]" wrote:
> You can create a global report parameter and link it to the parameters in
> your query. See the sample Sales Invoice report included in the RS samples.
> --
> HTH,
> ---
> Teo Lachev, MVP, MCSD, MCT
> "Microsoft Reporting Services in Action"
> "Applied Microsoft Analysis Services 2005"
> Home page and blog: http://www.prologika.com/
> ---
> "Mia" <Mia@.discussions.microsoft.com> wrote in message
> news:5DD6DD82-8A1B-4C36-B6BC-13F2C3FF9554@.microsoft.com...
> >I created three datasets. Every one has the same parameter and I need to
> >link
> > them together. How to do it?
> >
> > Thx.
>
>|||Install the sample reports that come with RS. With RS 2000, there should be
a link to the installer in the Reporting Services group. I called them
"global" because they are report-level parameters.
--
HTH,
---
Teo Lachev, MVP, MCSD, MCT
"Microsoft Reporting Services in Action"
"Applied Microsoft Analysis Services 2005"
Home page and blog: http://www.prologika.com/
---
"David" <David@.discussions.microsoft.com> wrote in message
news:FF10B3A5-5E2E-487F-87A4-21CDD6C79F0D@.microsoft.com...
> Where do I find these sample reports?
> I can't find any mention of global report parameters in BOL
> "Teo Lachev [MVP]" wrote:
>> You can create a global report parameter and link it to the parameters in
>> your query. See the sample Sales Invoice report included in the RS
>> samples.
>> --
>> HTH,
>> ---
>> Teo Lachev, MVP, MCSD, MCT
>> "Microsoft Reporting Services in Action"
>> "Applied Microsoft Analysis Services 2005"
>> Home page and blog: http://www.prologika.com/
>> ---
>> "Mia" <Mia@.discussions.microsoft.com> wrote in message
>> news:5DD6DD82-8A1B-4C36-B6BC-13F2C3FF9554@.microsoft.com...
>> >I created three datasets. Every one has the same parameter and I need to
>> >link
>> > them together. How to do it?
>> >
>> > Thx.
>>|||OK, I have that report and opened it.
There is 2 datasets and each datasets as the same parameter name in the query.
Is the Global Report Paremeter, that you are refering to, this dialog box:
REPORT>REPORT PARAMETERS
If so, how do you go about linking this parameter to the parameters in your
query?
Normally, when you create the parameter in your query, it appears
automatically in this dialog box. But what do you do if it doesn't?
"Teo Lachev [MVP]" wrote:
> Install the sample reports that come with RS. With RS 2000, there should be
> a link to the installer in the Reporting Services group. I called them
> "global" because they are report-level parameters.
> --
> HTH,
> ---
> Teo Lachev, MVP, MCSD, MCT
> "Microsoft Reporting Services in Action"
> "Applied Microsoft Analysis Services 2005"
> Home page and blog: http://www.prologika.com/
> ---
> "David" <David@.discussions.microsoft.com> wrote in message
> news:FF10B3A5-5E2E-487F-87A4-21CDD6C79F0D@.microsoft.com...
> > Where do I find these sample reports?
> >
> > I can't find any mention of global report parameters in BOL
> >
> > "Teo Lachev [MVP]" wrote:
> >
> >> You can create a global report parameter and link it to the parameters in
> >> your query. See the sample Sales Invoice report included in the RS
> >> samples.
> >>
> >> --
> >> HTH,
> >> ---
> >> Teo Lachev, MVP, MCSD, MCT
> >> "Microsoft Reporting Services in Action"
> >> "Applied Microsoft Analysis Services 2005"
> >> Home page and blog: http://www.prologika.com/
> >> ---
> >> "Mia" <Mia@.discussions.microsoft.com> wrote in message
> >> news:5DD6DD82-8A1B-4C36-B6BC-13F2C3FF9554@.microsoft.com...
> >> >I created three datasets. Every one has the same parameter and I need to
> >> >link
> >> > them together. How to do it?
> >> >
> >> > Thx.
> >>
> >>
> >>
>
>|||1. You use a placeholder for this parameter in your dataset query, e.g.:
WHERE (SOH.SalesOrderNumber = @.SalesOrderNumber)
2. You open the dataset properties and in the Parameters tab you link the
query parameter to the report-level parameter, like so:
Name Value
-- ---
@.SalesOrder Header =Parameters!SalesOrderNumber.Value
--
HTH,
---
Teo Lachev, MVP, MCSD, MCT
"Microsoft Reporting Services in Action"
"Applied Microsoft Analysis Services 2005"
Home page and blog: http://www.prologika.com/
---
"David" <David@.discussions.microsoft.com> wrote in message
news:168C68E8-B032-4668-9AB3-A52EBB4E3342@.microsoft.com...
> OK, I have that report and opened it.
> There is 2 datasets and each datasets as the same parameter name in the
> query.
> Is the Global Report Paremeter, that you are refering to, this dialog box:
> REPORT>REPORT PARAMETERS
> If so, how do you go about linking this parameter to the parameters in
> your
> query?
>
> Normally, when you create the parameter in your query, it appears
> automatically in this dialog box. But what do you do if it doesn't?
>
> "Teo Lachev [MVP]" wrote:
>> Install the sample reports that come with RS. With RS 2000, there should
>> be
>> a link to the installer in the Reporting Services group. I called them
>> "global" because they are report-level parameters.
>> --
>> HTH,
>> ---
>> Teo Lachev, MVP, MCSD, MCT
>> "Microsoft Reporting Services in Action"
>> "Applied Microsoft Analysis Services 2005"
>> Home page and blog: http://www.prologika.com/
>> ---
>> "David" <David@.discussions.microsoft.com> wrote in message
>> news:FF10B3A5-5E2E-487F-87A4-21CDD6C79F0D@.microsoft.com...
>> > Where do I find these sample reports?
>> >
>> > I can't find any mention of global report parameters in BOL
>> >
>> > "Teo Lachev [MVP]" wrote:
>> >
>> >> You can create a global report parameter and link it to the parameters
>> >> in
>> >> your query. See the sample Sales Invoice report included in the RS
>> >> samples.
>> >>
>> >> --
>> >> HTH,
>> >> ---
>> >> Teo Lachev, MVP, MCSD, MCT
>> >> "Microsoft Reporting Services in Action"
>> >> "Applied Microsoft Analysis Services 2005"
>> >> Home page and blog: http://www.prologika.com/
>> >> ---
>> >> "Mia" <Mia@.discussions.microsoft.com> wrote in message
>> >> news:5DD6DD82-8A1B-4C36-B6BC-13F2C3FF9554@.microsoft.com...
>> >> >I created three datasets. Every one has the same parameter and I need
>> >> >to
>> >> >link
>> >> > them together. How to do it?
>> >> >
>> >> > Thx.
>> >>
>> >>
>> >>
>>|||Thank You!
Thank You!
Thank You!
I have been having a hell of a time trying to figure out the solution top
this problem.
I was developing a report that had the WHERE clause hard code with a value.
Once I completed development, I change the hard code to a parameter. RS would
not recognize it as a parameter and kept telling my variables were unbound.
I was all over the net and this forum trying to find the answer.
"Teo Lachev [MVP]" wrote:
> 1. You use a placeholder for this parameter in your dataset query, e.g.:
> WHERE (SOH.SalesOrderNumber = @.SalesOrderNumber)
> 2. You open the dataset properties and in the Parameters tab you link the
> query parameter to the report-level parameter, like so:
> Name Value
> -- ---
> @.SalesOrder Header =Parameters!SalesOrderNumber.Value
> --
> HTH,
> ---
> Teo Lachev, MVP, MCSD, MCT
> "Microsoft Reporting Services in Action"
> "Applied Microsoft Analysis Services 2005"
> Home page and blog: http://www.prologika.com/
> ---
> "David" <David@.discussions.microsoft.com> wrote in message
> news:168C68E8-B032-4668-9AB3-A52EBB4E3342@.microsoft.com...
> > OK, I have that report and opened it.
> >
> > There is 2 datasets and each datasets as the same parameter name in the
> > query.
> >
> > Is the Global Report Paremeter, that you are refering to, this dialog box:
> > REPORT>REPORT PARAMETERS
> >
> > If so, how do you go about linking this parameter to the parameters in
> > your
> > query?
> >
> >
> > Normally, when you create the parameter in your query, it appears
> > automatically in this dialog box. But what do you do if it doesn't?
> >
> >
> > "Teo Lachev [MVP]" wrote:
> >
> >> Install the sample reports that come with RS. With RS 2000, there should
> >> be
> >> a link to the installer in the Reporting Services group. I called them
> >> "global" because they are report-level parameters.
> >>
> >> --
> >> HTH,
> >> ---
> >> Teo Lachev, MVP, MCSD, MCT
> >> "Microsoft Reporting Services in Action"
> >> "Applied Microsoft Analysis Services 2005"
> >> Home page and blog: http://www.prologika.com/
> >> ---
> >> "David" <David@.discussions.microsoft.com> wrote in message
> >> news:FF10B3A5-5E2E-487F-87A4-21CDD6C79F0D@.microsoft.com...
> >> > Where do I find these sample reports?
> >> >
> >> > I can't find any mention of global report parameters in BOL
> >> >
> >> > "Teo Lachev [MVP]" wrote:
> >> >
> >> >> You can create a global report parameter and link it to the parameters
> >> >> in
> >> >> your query. See the sample Sales Invoice report included in the RS
> >> >> samples.
> >> >>
> >> >> --
> >> >> HTH,
> >> >> ---
> >> >> Teo Lachev, MVP, MCSD, MCT
> >> >> "Microsoft Reporting Services in Action"
> >> >> "Applied Microsoft Analysis Services 2005"
> >> >> Home page and blog: http://www.prologika.com/
> >> >> ---
> >> >> "Mia" <Mia@.discussions.microsoft.com> wrote in message
> >> >> news:5DD6DD82-8A1B-4C36-B6BC-13F2C3FF9554@.microsoft.com...
> >> >> >I created three datasets. Every one has the same parameter and I need
> >> >> >to
> >> >> >link
> >> >> > them together. How to do it?
> >> >> >
> >> >> > Thx.
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
Showing posts with label together. Show all posts
Showing posts with label together. Show all posts
Friday, March 9, 2012
Sunday, February 19, 2012
How to kill a process
Our application uses SQL 2000 for back end and Access 2003 mdb for front end
and uses ODBC to link together.
One of our users appended data to one table. Because inserted duplicate data
in primary key. The user ignored system warning message and just turned off
her computer. While the user turned on her computer again, the table could
not open it.
We checked SQL 2000 server, the locking process was found in process
information, locks/process ID and lock/object in management. We disconnected
all front end sides application, then tried to kill the process using SQL
server Enterprise Manager console. But it was failed.
Would you help me how to kill the process then unlock this object?
Thanks
When you kill a process that has a transaction open, that transaction has to
be rolled back before the process is completely killed. If it is a large
transaction, it can take a long time for the transaction to roll back. You
can check in the Current Activity pane in Enterprise Manager what the status
is of the process. It should show up as KILLED/ROLLBACK. You can also get
the status of the process with KILL <process id> WITH STATUSONLY in Query
Analyzer. You can find the process id in the Current Activity in Enterprise
Manager.
Jacco Schalkwijk
SQL Server MVP
"NzCharlie" <NzCharlie@.discussions.microsoft.com> wrote in message
news:131B6064-D73D-432C-96C1-CF58C90BD0C8@.microsoft.com...
> Our application uses SQL 2000 for back end and Access 2003 mdb for front
> end
> and uses ODBC to link together.
> One of our users appended data to one table. Because inserted duplicate
> data
> in primary key. The user ignored system warning message and just turned
> off
> her computer. While the user turned on her computer again, the table could
> not open it.
> We checked SQL 2000 server, the locking process was found in process
> information, locks/process ID and lock/object in management. We
> disconnected
> all front end sides application, then tried to kill the process using SQL
> server Enterprise Manager console. But it was failed.
> Would you help me how to kill the process then unlock this object?
> Thanks
>
|||"Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid > wrote
in message news:%23AuJx9K3EHA.3820@.TK2MSFTNGP11.phx.gbl...
> When you kill a process that has a transaction open, that transaction has
to
> be rolled back before the process is completely killed. If it is a large
> transaction, it can take a long time for the transaction to roll back. You
> can check in the Current Activity pane in Enterprise Manager what the
status
> is of the process. It should show up as KILLED/ROLLBACK. You can also get
> the status of the process with KILL <process id> WITH STATUSONLY in Query
> Analyzer. You can find the process id in the Current Activity in
Enterprise
> Manager.
>
What he's hitting up against here I bet though is a "bug" I've seen before
where if the client closes improperly, it can be impossible to kill the
connection.
I think SQL SP1 still had this problem but that it's fixed in SP3a.
[vbcol=seagreen]
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "NzCharlie" <NzCharlie@.discussions.microsoft.com> wrote in message
> news:131B6064-D73D-432C-96C1-CF58C90BD0C8@.microsoft.com...
could[vbcol=seagreen]
SQL
>
and uses ODBC to link together.
One of our users appended data to one table. Because inserted duplicate data
in primary key. The user ignored system warning message and just turned off
her computer. While the user turned on her computer again, the table could
not open it.
We checked SQL 2000 server, the locking process was found in process
information, locks/process ID and lock/object in management. We disconnected
all front end sides application, then tried to kill the process using SQL
server Enterprise Manager console. But it was failed.
Would you help me how to kill the process then unlock this object?
Thanks
When you kill a process that has a transaction open, that transaction has to
be rolled back before the process is completely killed. If it is a large
transaction, it can take a long time for the transaction to roll back. You
can check in the Current Activity pane in Enterprise Manager what the status
is of the process. It should show up as KILLED/ROLLBACK. You can also get
the status of the process with KILL <process id> WITH STATUSONLY in Query
Analyzer. You can find the process id in the Current Activity in Enterprise
Manager.
Jacco Schalkwijk
SQL Server MVP
"NzCharlie" <NzCharlie@.discussions.microsoft.com> wrote in message
news:131B6064-D73D-432C-96C1-CF58C90BD0C8@.microsoft.com...
> Our application uses SQL 2000 for back end and Access 2003 mdb for front
> end
> and uses ODBC to link together.
> One of our users appended data to one table. Because inserted duplicate
> data
> in primary key. The user ignored system warning message and just turned
> off
> her computer. While the user turned on her computer again, the table could
> not open it.
> We checked SQL 2000 server, the locking process was found in process
> information, locks/process ID and lock/object in management. We
> disconnected
> all front end sides application, then tried to kill the process using SQL
> server Enterprise Manager console. But it was failed.
> Would you help me how to kill the process then unlock this object?
> Thanks
>
|||"Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid > wrote
in message news:%23AuJx9K3EHA.3820@.TK2MSFTNGP11.phx.gbl...
> When you kill a process that has a transaction open, that transaction has
to
> be rolled back before the process is completely killed. If it is a large
> transaction, it can take a long time for the transaction to roll back. You
> can check in the Current Activity pane in Enterprise Manager what the
status
> is of the process. It should show up as KILLED/ROLLBACK. You can also get
> the status of the process with KILL <process id> WITH STATUSONLY in Query
> Analyzer. You can find the process id in the Current Activity in
Enterprise
> Manager.
>
What he's hitting up against here I bet though is a "bug" I've seen before
where if the client closes improperly, it can be impossible to kill the
connection.
I think SQL SP1 still had this problem but that it's fixed in SP3a.
[vbcol=seagreen]
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "NzCharlie" <NzCharlie@.discussions.microsoft.com> wrote in message
> news:131B6064-D73D-432C-96C1-CF58C90BD0C8@.microsoft.com...
could[vbcol=seagreen]
SQL
>
Subscribe to:
Posts (Atom)