How many Jobs ran on a particular database yesterday

How to know how many Jobs ran on a particular database yesterday '
Thanks in Advance
Rajesh.Hi,
See msdb..sysjobhistory and sysjobs table in MSDB database of the server
Thanks
Hari
SQL Server MVP
"Rajesh" <Rajesh@.discussions.microsoft.com> wrote in message
news:5440189B-0811-4A85-84F0-DC7A06002A51@.microsoft.com...
> How to know how many Jobs ran on a particular database yesterday '
> Thanks in Advance
> Rajesh.
>

How is 'change' defined ?

Can anyone tell me how a change is defined when replicating ? in particular, if an update is done to an existing row, but the value is actually the same as it was originally, does this count as a change and will the replication attempt to update/resolve
it or not ?
I am working in a scenario where it is quite important to minimise the time/quantity of replication so want to minimise any unnecessary replicating. Are there any techniques I can use to help with this ?
any change is replicated.
|||Bother!
But thanks
|||Sarah wrote:
> Can anyone tell me how a change is defined when replicating ? in particular, if an update is done to an existing row, but the value is actually the same as it was originally, does this count as a change and will the replication attempt to update/resolv
e it or not ?
> I am working in a scenario where it is quite important to minimise the time/quantity of replication so want to minimise any unnecessary replicating. Are there any techniques I can use to help with this ?
Basically the log is replicated. So any action that will make a commited
change in the log will be replicated.
Furthermore, if you are doing updated, there is a possiblity that
inserts/deletes are replicated instead.
Typically, if you have a table with a unique index and you make an
update which update this index, sql server will replace your update by
an insert/delete and this is what will be sent to subscribers
|||Hi Sarah,
If you have a lot of updates that are setting columns to the same value
repeatedly, you can minimize the the replication volume by adding additional
"where" criteria to your update statements. For example, if you have a
statement (psuedo-code)
set @.val1 = 'XXX'
set @.tblKey = '123'
update TABLEX set fieldA = @.val1 where tblKey= @.tblKey
and you execute this 100 times, it will generate 100 updates, and 100
replication transactions.
If you add a where clause like so
update TABLEX set fieldA = @.val1 where tblKey= @.tblKey and fieldA <> @.val1
ii will not update the row after the first time. This type of clause
generally doesn't add much overhead to the transaction.
Ed
"Sarah" <anonymous@.discussions.microsoft.com> wrote in message
news:A8B78B80-4AF0-43FE-B3A8-8678C072C3E2@.microsoft.com...
> Can anyone tell me how a change is defined when replicating ? in
particular, if an update is done to an existing row, but the value is
actually the same as it was originally, does this count as a change and
will the replication attempt to update/resolve it or not ?
> I am working in a scenario where it is quite important to minimise the
time/quantity of replication so want to minimise any unnecessary
replicating. Are there any techniques I can use to help with this ?

How I resolved "Failure sending mail: The Report Server has encountered a configuration er

Hi
It seems there are various issues that lead to this problem.
If no other postings appear to solve your particular problem check
this...
Are all subscriptions failing or just some of them?
If its just some of them your problem maybe that the failing reports
have a subscription owner of a specific domain user id that has been
removed.
1) Check the subscription to the failing report and see if there is an
"Owner" specified under the "Delivered By" option.
2) If there is, check with your admin that this id still exists.
In my case this was an ex-employee who had been removed.
3) If the id has been deleted, create a clone of the subscription and
delete the failing subscription. Test your new subscription by manually
starting the appropriate job on the report server.
TIP - I identify the correct JobName with this piece of SQL on the
Report Server. You might need to adapt it slightly but it works for me!
SELECT J.name AS JobName
,C.Name AS ReportName
,CASE CHARINDEX('RenderFormat', S.ExtensionSettings)
WHEN 0 THEN 'PATH'
ELSE SUBSTRING(S.ExtensionSettings
,CHARINDEX('RenderFormat', S.ExtensionSettings) + 26
,CHARINDEX('</Value>', S.ExtensionSettings,
CHARINDEX('RenderFormat', S.ExtensionSettings)) -
(CHARINDEX('RenderFormat', S.ExtensionSettings) + 26))
END AS ExportType
,S.DeliveryExtension AS DeliveryMethod
,S.DEscription + '...' AS Recipients
FROM ReportServer.dbo.Catalog C
,ReportServer.dbo.ReportSchedule R
,ReportServer.dbo.Subscriptions S
,msdb.dbo.sysjobs J
WHERE C.ItemID = R.ReportID
AND R.SubscriptionID = S.SubscriptionID
AND J.name = CAST(R.ScheduleID AS VARCHAR(255))
ORDER BY 2
,3I'm running into this as well excep I am the owner of the report...
The one thing that has occured recently is that my PC was switched from one
domain to another. The new domian I am operating on is setup w/ active
directory.
Any ideas?
Thanks,
Ben Sullins
"perrydyball@.hotmail.com" wrote:
> Hi
> It seems there are various issues that lead to this problem.
> If no other postings appear to solve your particular problem check
> this...
> Are all subscriptions failing or just some of them?
> If its just some of them your problem maybe that the failing reports
> have a subscription owner of a specific domain user id that has been
> removed.
> 1) Check the subscription to the failing report and see if there is an
> "Owner" specified under the "Delivered By" option.
> 2) If there is, check with your admin that this id still exists.
> In my case this was an ex-employee who had been removed.
> 3) If the id has been deleted, create a clone of the subscription and
> delete the failing subscription. Test your new subscription by manually
> starting the appropriate job on the report server.
> TIP - I identify the correct JobName with this piece of SQL on the
> Report Server. You might need to adapt it slightly but it works for me!
> SELECT J.name AS JobName
> ,C.Name AS ReportName
> ,CASE CHARINDEX('RenderFormat', S.ExtensionSettings)
> WHEN 0 THEN 'PATH'
> ELSE SUBSTRING(S.ExtensionSettings
> ,CHARINDEX('RenderFormat', S.ExtensionSettings) + 26
> ,CHARINDEX('</Value>', S.ExtensionSettings,
> CHARINDEX('RenderFormat', S.ExtensionSettings)) -
> (CHARINDEX('RenderFormat', S.ExtensionSettings) + 26))
> END AS ExportType
> ,S.DeliveryExtension AS DeliveryMethod
> ,S.DEscription + '...' AS Recipients
> FROM ReportServer.dbo.Catalog C
> ,ReportServer.dbo.ReportSchedule R
> ,ReportServer.dbo.Subscriptions S
> ,msdb.dbo.sysjobs J
> WHERE C.ItemID = R.ReportID
> AND R.SubscriptionID = S.SubscriptionID
> AND J.name = CAST(R.ScheduleID AS VARCHAR(255))
> ORDER BY 2
> ,3
>