Showing posts with label updated. Show all posts
Showing posts with label updated. Show all posts

Friday, March 23, 2012

Refresh Report from Browser

I post a report on report server. I open the report from IE browser, after I
updated the database and I click REFRESH button on toolbar, report was not
refreshed. The only way is that I have to close browser and launch it again
and open the report to display refreshed data.
Could anyone let me know if we only click refresh button on the tool bar of
browser so that we can get refreshed reports?
Thanks a lot.Click the Refresh Button within the report itself.
Charles Kangai, MCT, MCDBA
"Sally" wrote:
> I post a report on report server. I open the report from IE browser, after I
> updated the database and I click REFRESH button on toolbar, report was not
> refreshed. The only way is that I have to close browser and launch it again
> and open the report to display refreshed data.
> Could anyone let me know if we only click refresh button on the tool bar of
> browser so that we can get refreshed reports?
> Thanks a lot.
>|||Here is my report url, I would like disable toolbar only except Refresh
button, how do I do that?
http://localhost/corpreportserver?/UsageReports/UsageStatusSummary&rc:parameters=false&rc:toolbar=false
Thanks,
"Charles Kangai" wrote:
> Click the Refresh Button within the report itself.
> Charles Kangai, MCT, MCDBA
> "Sally" wrote:
> > I post a report on report server. I open the report from IE browser, after I
> > updated the database and I click REFRESH button on toolbar, report was not
> > refreshed. The only way is that I have to close browser and launch it again
> > and open the report to display refreshed data.
> >
> > Could anyone let me know if we only click refresh button on the tool bar of
> > browser so that we can get refreshed reports?
> >
> > Thanks a lot.
> >
> >|||Hi Sally,
Are you talking about the Browser toolbar or the Report toolbar. They are
very different things, but both have a refresh button!
The refresh button on the report toolbar re-submits the query refreshing the
data.
The refresh button on the browser toolbar just requests the report from the
web server again, if you have 'caching' on the report it won't necessarily
submit the query again.
Look in properties and execution for the report in report manager for
'Cache' settings.
Regards
Chris
"Sally" wrote:
> Here is my report url, I would like disable toolbar only except Refresh
> button, how do I do that?
> http://localhost/corpreportserver?/UsageReports/UsageStatusSummary&rc:parameters=false&rc:toolbar=false
> Thanks,
> "Charles Kangai" wrote:
> > Click the Refresh Button within the report itself.
> >
> > Charles Kangai, MCT, MCDBA
> >
> > "Sally" wrote:
> >
> > > I post a report on report server. I open the report from IE browser, after I
> > > updated the database and I click REFRESH button on toolbar, report was not
> > > refreshed. The only way is that I have to close browser and launch it again
> > > and open the report to display refreshed data.
> > >
> > > Could anyone let me know if we only click refresh button on the tool bar of
> > > browser so that we can get refreshed reports?
> > >
> > > Thanks a lot.
> > >
> > >

Refresh page when database data is update

Hi All,

Is it possible to refresh the web page when certain table data is updated? And I cannot use the auto-refresh feature. Thank you very much.

Not easily. I imagine you could hobble something together with AJAX, but it would likely be fragile and not easy to maintain.

Friday, March 9, 2012

Refer to ROWGUID col in update trigger

When writing an Update trigger on a table that has a UniqueIdentifier as the
primary key, how to I refer to the current row being updated.
I am used to using @.@.identity when working with primary keys that are of
type int but a UniqueIdentifier cannot be an identity column. I suspect it
has something to do with the "Is ROWGUID" property but I can't find the
function for getting the GUID of the row being updated.
Thanks,
Andrew.There isn't one. If you need to know this then you should generate the Guid
beforehand and use it in the insert statement.
--
Andrew J. Kelly
SQL Server MVP
"Andrew" <sql@.ses.ca> wrote in message
news:u3lnbAiRDHA.2636@.TK2MSFTNGP10.phx.gbl...
> When writing an Update trigger on a table that has a UniqueIdentifier as
the
> primary key, how to I refer to the current row being updated.
> I am used to using @.@.identity when working with primary keys that are of
> type int but a UniqueIdentifier cannot be an identity column. I suspect
it
> has something to do with the "Is ROWGUID" property but I can't find the
> function for getting the GUID of the row being updated.
> Thanks,
> Andrew.
>|||I want to access the row that is being updated, not inserted. The GUID is
already there.
Does this mean it is not possible to use a trigger to update a
"DateOfLastUpdate" field if the primary key is a GUID? I realize date could
be updated if the update was performed using a stored procedure but I feel
it would be safer to have this functionality on the table itself.
Thanks,
Andrew
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%237WJLGiRDHA.1552@.TK2MSFTNGP10.phx.gbl...
> There isn't one. If you need to know this then you should generate the
Guid
> beforehand and use it in the insert statement.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "Andrew" <sql@.ses.ca> wrote in message
> news:u3lnbAiRDHA.2636@.TK2MSFTNGP10.phx.gbl...
> > When writing an Update trigger on a table that has a UniqueIdentifier as
> the
> > primary key, how to I refer to the current row being updated.
> >
> > I am used to using @.@.identity when working with primary keys that are of
> > type int but a UniqueIdentifier cannot be an identity column. I suspect
> it
> > has something to do with the "Is ROWGUID" property but I can't find the
> > function for getting the GUID of the row being updated.
> >
> > Thanks,
> > Andrew.
> >
> >
>|||> You threw me off when you mentioned @.@.IDENTITY. @.@.IDENTITY has nothing to
> do with an UPDATE, it is only useful for Inserts. Any time you want to
> reference a row that is being updated in a trigger you can use the
Inserted
> table. To update a datetime column you would simply do this:
> UPDATE YourTable SET ModDate = GETDATE()
> WHERE PK IN (SELECT i.PK FROM Inserted as i)
> This way it works when more than 1 rows is updated and there is no need to
> know what the actual value of the PK is.
I tend to use a wrapper like:
IF NOT UPDATE(ModDate)
Just to prevent recursion. :-)|||Thanks for your help. I had just "discovered" the inserted table but the
method I came up with is not as clean as yours.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uiAkt8iRDHA.3236@.TK2MSFTNGP10.phx.gbl...
> You threw me off when you mentioned @.@.IDENTITY. @.@.IDENTITY has nothing to
> do with an UPDATE, it is only useful for Inserts. Any time you want to
> reference a row that is being updated in a trigger you can use the
Inserted
> table. To update a datetime column you would simply do this:
> UPDATE YourTable SET ModDate = GETDATE()
> WHERE PK IN (SELECT i.PK FROM Inserted as i)
> This way it works when more than 1 rows is updated and there is no need to
> know what the actual value of the PK is.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "Andrew" <sql@.ses.ca> wrote in message
> news:u53MXdiRDHA.2424@.tk2msftngp13.phx.gbl...
> > I want to access the row that is being updated, not inserted. The GUID
is
> > already there.
> >
> > Does this mean it is not possible to use a trigger to update a
> > "DateOfLastUpdate" field if the primary key is a GUID? I realize date
> could
> > be updated if the update was performed using a stored procedure but I
feel
> > it would be safer to have this functionality on the table itself.
> >
> > Thanks,
> > Andrew
> >
> >
> > "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> > news:%237WJLGiRDHA.1552@.TK2MSFTNGP10.phx.gbl...
> > > There isn't one. If you need to know this then you should generate
the
> > Guid
> > > beforehand and use it in the insert statement.
> > >
> > > --
> > >
> > > Andrew J. Kelly
> > > SQL Server MVP
> > >
> > >
> > > "Andrew" <sql@.ses.ca> wrote in message
> > > news:u3lnbAiRDHA.2636@.TK2MSFTNGP10.phx.gbl...
> > > > When writing an Update trigger on a table that has a
UniqueIdentifier
> as
> > > the
> > > > primary key, how to I refer to the current row being updated.
> > > >
> > > > I am used to using @.@.identity when working with primary keys that
are
> of
> > > > type int but a UniqueIdentifier cannot be an identity column. I
> suspect
> > > it
> > > > has something to do with the "Is ROWGUID" property but I can't find
> the
> > > > function for getting the GUID of the row being updated.
> > > >
> > > > Thanks,
> > > > Andrew.
> > > >
> > > >
> > >
> > >
> >
> >
>

Saturday, February 25, 2012

Reducing Disk I/O in SQL Server configuration

Hi All,
We have a SQL server database in which the contents are updated for
every few seconds(it can be as low as 4 sec). Therefore the tablesize
will keep growing continuously. There is a problem in the table design
itself. It has been designed without any primary key. I know this will
make the insertion slower. If we rectify this, what else should we do
in the SQL Server side to reduce the Disk I/O access for the database.
The harddisk LED keeps flashing continuosly.
Thanks
Hi
Does the table have any indexes?
<vanisathish@.gmail.com> wrote in message
news:1123756244.000317.291730@.z14g2000cwz.googlegr oups.com...
> Hi All,
> We have a SQL server database in which the contents are updated for
> every few seconds(it can be as low as 4 sec). Therefore the tablesize
> will keep growing continuously. There is a problem in the table design
> itself. It has been designed without any primary key. I know this will
> make the insertion slower. If we rectify this, what else should we do
> in the SQL Server side to reduce the Disk I/O access for the database.
> The harddisk LED keeps flashing continuosly.
> Thanks
>

Reducing Disk I/O in SQL Server configuration

Hi All,
We have a SQL server database in which the contents are updated for
every few seconds(it can be as low as 4 sec). Therefore the tablesize
will keep growing continuously. There is a problem in the table design
itself. It has been designed without any primary key. I know this will
make the insertion slower. If we rectify this, what else should we do
in the SQL Server side to reduce the Disk I/O access for the database.
The harddisk LED keeps flashing continuosly.
ThanksHi
Does the table have any indexes?
<vanisathish@.gmail.com> wrote in message
news:1123756244.000317.291730@.z14g2000cwz.googlegroups.com...
> Hi All,
> We have a SQL server database in which the contents are updated for
> every few seconds(it can be as low as 4 sec). Therefore the tablesize
> will keep growing continuously. There is a problem in the table design
> itself. It has been designed without any primary key. I know this will
> make the insertion slower. If we rectify this, what else should we do
> in the SQL Server side to reduce the Disk I/O access for the database.
> The harddisk LED keeps flashing continuosly.
> Thanks
>

Reducing Disk I/O in SQL Server configuration

Hi All,
We have a SQL server database in which the contents are updated for
every few seconds(it can be as low as 4 sec). Therefore the tablesize
will keep growing continuously. There is a problem in the table design
itself. It has been designed without any primary key. I know this will
make the insertion slower. If we rectify this, what else should we do
in the SQL Server side to reduce the Disk I/O access for the database.
The harddisk LED keeps flashing continuosly.
ThanksHi
Does the table have any indexes?
<vanisathish@.gmail.com> wrote in message
news:1123756244.000317.291730@.z14g2000cwz.googlegroups.com...
> Hi All,
> We have a SQL server database in which the contents are updated for
> every few seconds(it can be as low as 4 sec). Therefore the tablesize
> will keep growing continuously. There is a problem in the table design
> itself. It has been designed without any primary key. I know this will
> make the insertion slower. If we rectify this, what else should we do
> in the SQL Server side to reduce the Disk I/O access for the database.
> The harddisk LED keeps flashing continuosly.
> Thanks
>