I've working on a report at a client and I'm having an issue with a report
not reflecting multiple updated. The basic procedure that is followed is:
1. The client adds an event to the timeline.
2. The client runs the timeline report and the new event shows up.
3. The client adds a new event to the timeline.
4. The second, and any subsequent events do not show up.
I've checked the stored procedure that the report calls and it returns the
correct data every time (reflects the events as added). I've also checked
the execution properties in the report to be sure that the report isn't set
to be cached, and it's not. I'm using SQL Server 2000 & Reporting Services,
and I'm using Visual Studio 2003 SP1.
Any help would be really appreciated.It took me awhile to find the answer when I had the same problem.
Use;
rs:ClearSession=true in the url assuming you are using the url method.
directs the report server to remove a report from session. All report
instances associated with an authenticated user are removed from
session. (A report instance is defined as the same report run multiple
times with different report parameter values.)
Neil
John Swaringen wrote:
> I've working on a report at a client and I'm having an issue with a report
> not reflecting multiple updated. The basic procedure that is followed is:
> 1. The client adds an event to the timeline.
> 2. The client runs the timeline report and the new event shows up.
> 3. The client adds a new event to the timeline.
> 4. The second, and any subsequent events do not show up.
> I've checked the stored procedure that the report calls and it returns the
> correct data every time (reflects the events as added). I've also checked
> the execution properties in the report to be sure that the report isn't set
> to be cached, and it's not. I'm using SQL Server 2000 & Reporting Services,
> and I'm using Visual Studio 2003 SP1.
> Any help would be really appreciated.|||Neil,
That worked great. It took me a while to figure out that I had to add it
via the ReportViewer.SetParameter() function. But once I did that everything
is cooking!
Thanks for the help!
"neilgould@.gmail.com" wrote:
> It took me awhile to find the answer when I had the same problem.
> Use;
> rs:ClearSession=true in the url assuming you are using the url method.
> directs the report server to remove a report from session. All report
> instances associated with an authenticated user are removed from
> session. (A report instance is defined as the same report run multiple
> times with different report parameter values.)
> Neil
>
> John Swaringen wrote:
> > I've working on a report at a client and I'm having an issue with a report
> > not reflecting multiple updated. The basic procedure that is followed is:
> >
> > 1. The client adds an event to the timeline.
> > 2. The client runs the timeline report and the new event shows up.
> > 3. The client adds a new event to the timeline.
> > 4. The second, and any subsequent events do not show up.
> >
> > I've checked the stored procedure that the report calls and it returns the
> > correct data every time (reflects the events as added). I've also checked
> > the execution properties in the report to be sure that the report isn't set
> > to be cached, and it's not. I'm using SQL Server 2000 & Reporting Services,
> > and I'm using Visual Studio 2003 SP1.
> >
> > Any help would be really appreciated.
>
Showing posts with label basic. Show all posts
Showing posts with label basic. Show all posts
Wednesday, March 28, 2012
Friday, March 23, 2012
Pblm with Nested transactions
Friends,
I've a very basic doubt with Nested transactions (across procedures) in SQL Server and i guess the given below sample code illustarates my doubt well more than my words ..
I've a Proc1 like this
create procedure sp_proc1
as
begin
begin tran sp_proc1
insert into tab1 values (1,2)
exec sp_proc2 1
if <Some cdn statement>
rollback tran sp_proc1
else
commit tran sp_proc1
end
and called proc sp_proc2 is like this
create procedure sp_proc2
(
@.val1 int
)
as
begin tran proc2
update tab2 set col1 = 5
IF <some cdn statement>
begin
rollback tran proc2
end
else
begin
commit tran proc2
end
The pblm is when the 1st proc is executed and when the cdn statement in the 2nd proc is sucess, then it results with the error
Failed to retreive execution plan: Cannot roll back proc2. No transaction or savepoint of that name was found.
any suggestions
--SQLPgmrbegin tran proc2
update tab2 set col1 = 5
IF <some cdn statement> << Checking your tab2 but it still in tran !
begin
...
I think you probably are trying to check some thing that you are not commit yet!
I've a very basic doubt with Nested transactions (across procedures) in SQL Server and i guess the given below sample code illustarates my doubt well more than my words ..
I've a Proc1 like this
create procedure sp_proc1
as
begin
begin tran sp_proc1
insert into tab1 values (1,2)
exec sp_proc2 1
if <Some cdn statement>
rollback tran sp_proc1
else
commit tran sp_proc1
end
and called proc sp_proc2 is like this
create procedure sp_proc2
(
@.val1 int
)
as
begin tran proc2
update tab2 set col1 = 5
IF <some cdn statement>
begin
rollback tran proc2
end
else
begin
commit tran proc2
end
The pblm is when the 1st proc is executed and when the cdn statement in the 2nd proc is sucess, then it results with the error
Failed to retreive execution plan: Cannot roll back proc2. No transaction or savepoint of that name was found.
any suggestions
--SQLPgmrbegin tran proc2
update tab2 set col1 = 5
IF <some cdn statement> << Checking your tab2 but it still in tran !
begin
...
I think you probably are trying to check some thing that you are not commit yet!
Friday, March 9, 2012
Password protection
Basic, I know.....
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Password protection
Basic, I know.....
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".
Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>
|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".
Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>
|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Password protection
Basic, I know.....
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Subscribe to:
Posts (Atom)