T-SQL Script: event

Showing posts with label event. Show all posts

Monday, March 26, 2012

Scheduling a Report based on an event

Is it possible to schedule a report based on a flag or stored procedure completing. Currently have an overnight load process which must complete before the report starts. Any suggestions would be most appreciated
--
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.If it's possible to detect that your stored proc is finished within SQL
(either because it sets a flag in a table or be the mire presence of data it
creates or something) there might be a way. Might not be the optimal
solution, but your SQL dataset could reference that flag so that no data is
returned at all to the report if the flag doesn't exist. You'd have to set
it up so that the data table the report references doesn't exist at all until
the stored proc is finished. Then schedule your report job to run multiple
times near the time when you expect the SQL proc to finish. Without the data
table existing, your Rpt Services job should just error out and product
nothing. Again, not an elegant solution, but if you're desperate might be
something to toy around with ... a place to start.
sebring1130
"SqlJunkies User" wrote:
> Is it possible to schedule a report based on a flag or stored procedure completing. Currently have an overnight load process which must complete before the report starts. Any suggestions would be most appreciated
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
>|||Sure this is real easy to do.
Create a schedule that has completed in the past - so effectively it will
never fire. Associate this schedule with a Report.
Now what happens is that a SQL Agent Job is created - that maps to the
schedule. You can run SQL Agent Jobs from the SQL Agent Management interface
by hand - or you can cause that job to run through T-SQL.
All that the SQL Agent Job does is create an entry in the Report Server's
Event table at the scheduled time. The Report Server Windows Service is
polling the Event table every 10 seconds or so - and if there are any events
to process it gets on and processes them.
So what you do is either include in your long running stored procedure a
call that will create the required entry in the Event table directly - or a
call that fires the SQL Agent Job.
- One word of warning though if you start editing the schedule in the Report
Manager, then the Report Manager can end up re-creating the SQL Agent Jobs -
and you lose reference to the actual Job.
However if you are disciplined enough then this approach works fine -
(Schedule in the past, have your own process force the SQL Agent Job to run)
Peter Blackburn
Hitchhiker's Guide to SQL Server 2000 Reporting Services
http://www.sqlreportingservices.net
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:OWMxVAoxEHA.3080@.TK2MSFTNGP14.phx.gbl...
> Is it possible to schedule a report based on a flag or stored procedure
> completing. Currently have an overnight load process which must complete
> before the report starts. Any suggestions would be most appreciated
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
> supports Post Alerts, Ratings, and Searching.

Friday, March 23, 2012

Scheduler node deadlock message.

Hi:

We seem to be hitting a performance problem on SQL Server 2005. We encounter the following message frequently in the event log. We have update stats, reindexing and everything else in place. However this message keeps getting logged.

All schedulers on Node 0 appear deadlocked due to a large number
of worker threads waiting on LCK_M_IS. Process Utilization 25%%

MS Experts (Product Gurus)/MVPs can you please offer some explanation or insight into the error and also a possible resolution on how to fix it. I have the following questions:

1). Is this related to poor queries performing badly and needs to be tuned?.

2). Is this a more DIsk I/O Issue and whether we need faster disks or disk arrays?

3). Is something configured wrongly on the SQL Server?

4). Are we handling our transactions badly and thus resulting in blocking or deadlocks?.

Please provide your valuable suggestions.

Thanks

Ankith

I forgot to mention the system configuration.

The Server is Windows Server 2003 (x64 Edition) with AMD Quad (4) Processors (2.2 GHZ) and has apprx 16 GB of RAM.

Awe is enabled.

|||

This message indicates that there are some pretty long blocking chains on your server.

Have a look at the blocking section in http://www.microsoft.com/technet/prodtechnol/sql/2005/tsprfprb.mspx for methods of troubleshooting blocking issues.

|||

Hi Jerome:

Thanks for the info. Is this error anyway related to Hard disk contention (because I see worker threads waiting on LCK_M_IS). Just want to get your opinion and see if we can also take a look at our hard disks.

Thanks.

|||

Based on the wait type it's highly unlikely that disk issues have anything to do with the problem. Start by looking at the connection that's holding incompatible lock and determine what it's doing.

sql

Tuesday, March 20, 2012

Scheduled job is not running successfully. Event ID: 208

SQL server standard edition version 8.00.2039 [SP4] on MSWindows NT 5.2
[3790] .
We have a procedure that is scheduled to run every night . It is running
fine for last few months. Last week it stopped running successfully. In
application event log we are getting warning message:
==================================== Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 6/12/2007
Time: 4:23:19 AM
User: N/A
Computer: computername1
Description:
SQL Server Scheduled Job 'abcd-Daily 1' (0xC456F221DE41D5469B869BA1657DDDC0)
- Status: Failed - Invoked on: 2007-06-12 04:00:00 - Message: The job failed.
The Job was invoked by Schedule 6 (6.x schedule). The last step to run was
step 1 (Step 1).
====================================
No error message in sql server errorlog.
--
ontario, canadaHI
Do this
Enterprise manager->Management->sql Server agent->jobs
select your job and click the job history from the drop down menu
this will open up job history dialog box, click the show step details, you
can see the actual error message there, post that error message
Regards
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"db" <db@.discussions.microsoft.com> wrote in message
news:DA7F4D29-8754-4A40-ABAD-AEFE4890BB41@.microsoft.com...
> SQL server standard edition version 8.00.2039 [SP4] on MSWindows NT 5.2
> [3790] .
> We have a procedure that is scheduled to run every night . It is running
> fine for last few months. Last week it stopped running successfully. In
> application event log we are getting warning message:
> ====================================> Event Type: Warning
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 208
> Date: 6/12/2007
> Time: 4:23:19 AM
> User: N/A
> Computer: computername1
> Description:
> SQL Server Scheduled Job 'abcd-Daily 1'
> (0xC456F221DE41D5469B869BA1657DDDC0)
> - Status: Failed - Invoked on: 2007-06-12 04:00:00 - Message: The job
> failed.
> The Job was invoked by Schedule 6 (6.x schedule). The last step to run
> was
> step 1 (Step 1).
> ====================================> No error message in sql server errorlog.
> --
> ontario, canada|||============================================Its a permission error in step1.
Executed as user: username. SELECT permission denied on object
'a_bb_REQUEST_RESOURCE', database 'databasename', owner 'dbo'. [SQLSTATE
42000] (Error 229). The step failed.
============================================--
ontario, canada
"vt" wrote:
> HI
> Do this
> Enterprise manager->Management->sql Server agent->jobs
> select your job and click the job history from the drop down menu
> this will open up job history dialog box, click the show step details, you
> can see the actual error message there, post that error message
> Regards
> VT
> Knowledge is power, share it...
> http://oneplace4sql.blogspot.com/
> "db" <db@.discussions.microsoft.com> wrote in message
> news:DA7F4D29-8754-4A40-ABAD-AEFE4890BB41@.microsoft.com...
> > SQL server standard edition version 8.00.2039 [SP4] on MSWindows NT 5.2
> > [3790] .
> >
> > We have a procedure that is scheduled to run every night . It is running
> > fine for last few months. Last week it stopped running successfully. In
> > application event log we are getting warning message:
> >
> > ====================================> > Event Type: Warning
> > Event Source: SQLSERVERAGENT
> > Event Category: Job Engine
> > Event ID: 208
> > Date: 6/12/2007
> > Time: 4:23:19 AM
> > User: N/A
> > Computer: computername1
> > Description:
> > SQL Server Scheduled Job 'abcd-Daily 1'
> > (0xC456F221DE41D5469B869BA1657DDDC0)
> > - Status: Failed - Invoked on: 2007-06-12 04:00:00 - Message: The job
> > failed.
> > The Job was invoked by Schedule 6 (6.x schedule). The last step to run
> > was
> > step 1 (Step 1).
> > ====================================> >
> > No error message in sql server errorlog.
> >
> > --
> > ontario, canada
>
>|||It points to permission error.
Executed as user: abc. SELECT permission denied on object
'a_bb_REQUEST_RESOURCE', database 'databasename', owner 'dbo'. [SQLSTATE
42000] (Error 229). The step failed.
--
ontario, canada
"vt" wrote:
> HI
> Do this
> Enterprise manager->Management->sql Server agent->jobs
> select your job and click the job history from the drop down menu
> this will open up job history dialog box, click the show step details, you
> can see the actual error message there, post that error message
> Regards
> VT
> Knowledge is power, share it...
> http://oneplace4sql.blogspot.com/
> "db" <db@.discussions.microsoft.com> wrote in message
> news:DA7F4D29-8754-4A40-ABAD-AEFE4890BB41@.microsoft.com...
> > SQL server standard edition version 8.00.2039 [SP4] on MSWindows NT 5.2
> > [3790] .
> >
> > We have a procedure that is scheduled to run every night . It is running
> > fine for last few months. Last week it stopped running successfully. In
> > application event log we are getting warning message:
> >
> > ====================================> > Event Type: Warning
> > Event Source: SQLSERVERAGENT
> > Event Category: Job Engine
> > Event ID: 208
> > Date: 6/12/2007
> > Time: 4:23:19 AM
> > User: N/A
> > Computer: computername1
> > Description:
> > SQL Server Scheduled Job 'abcd-Daily 1'
> > (0xC456F221DE41D5469B869BA1657DDDC0)
> > - Status: Failed - Invoked on: 2007-06-12 04:00:00 - Message: The job
> > failed.
> > The Job was invoked by Schedule 6 (6.x schedule). The last step to run
> > was
> > step 1 (Step 1).
> > ====================================> >
> > No error message in sql server errorlog.
> >
> > --
> > ontario, canada
>
>|||Its a permission error.
Executed as user: abc. SELECT permission denied on object
'a_bb_REQUEST_RESOURCE', database 'databasename', owner 'dbo'. [SQLSTATE
42000] (Error 229). The step failed.
--
ontario, canada
"vt" wrote:
> HI
> Do this
> Enterprise manager->Management->sql Server agent->jobs
> select your job and click the job history from the drop down menu
> this will open up job history dialog box, click the show step details, you
> can see the actual error message there, post that error message
> Regards
> VT
> Knowledge is power, share it...
> http://oneplace4sql.blogspot.com/
> "db" <db@.discussions.microsoft.com> wrote in message
> news:DA7F4D29-8754-4A40-ABAD-AEFE4890BB41@.microsoft.com...
> > SQL server standard edition version 8.00.2039 [SP4] on MSWindows NT 5.2
> > [3790] .
> >
> > We have a procedure that is scheduled to run every night . It is running
> > fine for last few months. Last week it stopped running successfully. In
> > application event log we are getting warning message:
> >
> > ====================================> > Event Type: Warning
> > Event Source: SQLSERVERAGENT
> > Event Category: Job Engine
> > Event ID: 208
> > Date: 6/12/2007
> > Time: 4:23:19 AM
> > User: N/A
> > Computer: computername1
> > Description:
> > SQL Server Scheduled Job 'abcd-Daily 1'
> > (0xC456F221DE41D5469B869BA1657DDDC0)
> > - Status: Failed - Invoked on: 2007-06-12 04:00:00 - Message: The job
> > failed.
> > The Job was invoked by Schedule 6 (6.x schedule). The last step to run
> > was
> > step 1 (Step 1).
> > ====================================> >
> > No error message in sql server errorlog.
> >
> > --
> > ontario, canada
>
>|||Hi
ok..Now give the proper permission and try..
Regards
Vt
Knowledge is power;Share it
http://oneplace4sql.blogspot.com
"db" <db@.discussions.microsoft.com> wrote in message
news:9AE94423-FD7C-4552-BFB5-4EDA062914D8@.microsoft.com...
> ============================================> Its a permission error in step1.
> Executed as user: username. SELECT permission denied on object
> 'a_bb_REQUEST_RESOURCE', database 'databasename', owner 'dbo'. [SQLSTATE
> 42000] (Error 229). The step failed.
> ============================================> --
> ontario, canada
>
> "vt" wrote:
>> HI
>> Do this
>> Enterprise manager->Management->sql Server agent->jobs
>> select your job and click the job history from the drop down menu
>> this will open up job history dialog box, click the show step details,
>> you
>> can see the actual error message there, post that error message
>> Regards
>> VT
>> Knowledge is power, share it...
>> http://oneplace4sql.blogspot.com/
>> "db" <db@.discussions.microsoft.com> wrote in message
>> news:DA7F4D29-8754-4A40-ABAD-AEFE4890BB41@.microsoft.com...
>> > SQL server standard edition version 8.00.2039 [SP4] on MSWindows NT 5.2
>> > [3790] .
>> >
>> > We have a procedure that is scheduled to run every night . It is
>> > running
>> > fine for last few months. Last week it stopped running successfully. In
>> > application event log we are getting warning message:
>> >
>> > ====================================>> > Event Type: Warning
>> > Event Source: SQLSERVERAGENT
>> > Event Category: Job Engine
>> > Event ID: 208
>> > Date: 6/12/2007
>> > Time: 4:23:19 AM
>> > User: N/A
>> > Computer: computername1
>> > Description:
>> > SQL Server Scheduled Job 'abcd-Daily 1'
>> > (0xC456F221DE41D5469B869BA1657DDDC0)
>> > - Status: Failed - Invoked on: 2007-06-12 04:00:00 - Message: The job
>> > failed.
>> > The Job was invoked by Schedule 6 (6.x schedule). The last step to run
>> > was
>> > step 1 (Step 1).
>> > ====================================>> >
>> > No error message in sql server errorlog.
>> >
>> > --
>> > ontario, canada
>>|||It worked. Thanks vt.
--
ontario, canada
"Vt" wrote:
> Hi
> ok..Now give the proper permission and try..
>
> Regards
> Vt
> Knowledge is power;Share it
> http://oneplace4sql.blogspot.com
>
> "db" <db@.discussions.microsoft.com> wrote in message
> news:9AE94423-FD7C-4552-BFB5-4EDA062914D8@.microsoft.com...
> > ============================================> > Its a permission error in step1.
> > Executed as user: username. SELECT permission denied on object
> > 'a_bb_REQUEST_RESOURCE', database 'databasename', owner 'dbo'. [SQLSTATE
> > 42000] (Error 229). The step failed.
> > ============================================> > --
> > ontario, canada
> >
> >
> > "vt" wrote:
> >
> >> HI
> >>
> >> Do this
> >>
> >> Enterprise manager->Management->sql Server agent->jobs
> >>
> >> select your job and click the job history from the drop down menu
> >> this will open up job history dialog box, click the show step details,
> >> you
> >> can see the actual error message there, post that error message
> >>
> >> Regards
> >> VT
> >> Knowledge is power, share it...
> >> http://oneplace4sql.blogspot.com/
> >> "db" <db@.discussions.microsoft.com> wrote in message
> >> news:DA7F4D29-8754-4A40-ABAD-AEFE4890BB41@.microsoft.com...
> >> > SQL server standard edition version 8.00.2039 [SP4] on MSWindows NT 5.2
> >> > [3790] .
> >> >
> >> > We have a procedure that is scheduled to run every night . It is
> >> > running
> >> > fine for last few months. Last week it stopped running successfully. In
> >> > application event log we are getting warning message:
> >> >
> >> > ====================================> >> > Event Type: Warning
> >> > Event Source: SQLSERVERAGENT
> >> > Event Category: Job Engine
> >> > Event ID: 208
> >> > Date: 6/12/2007
> >> > Time: 4:23:19 AM
> >> > User: N/A
> >> > Computer: computername1
> >> > Description:
> >> > SQL Server Scheduled Job 'abcd-Daily 1'
> >> > (0xC456F221DE41D5469B869BA1657DDDC0)
> >> > - Status: Failed - Invoked on: 2007-06-12 04:00:00 - Message: The job
> >> > failed.
> >> > The Job was invoked by Schedule 6 (6.x schedule). The last step to run
> >> > was
> >> > step 1 (Step 1).
> >> > ====================================> >> >
> >> > No error message in sql server errorlog.
> >> >
> >> > --
> >> > ontario, canada
> >>
> >>
> >>
>
>

Scheduled job is not running successfully. Event ID: 208

Tuesday, February 21, 2012

Schedule and Delivery processor cannot connect

Hello,
I'm getting the following error on the application log of the event viewer:
Schedule and Delivery processor cannot connect to the report server database.
However I have no trouble to test some reports (e.g. the sample reports provided with reporting services).
What could be wrong with my configuration?
Thanks
CesarCan you look in the reportserverservice<date>.log files for more
information.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Cesar" <Cesar@.discussions.microsoft.com> wrote in message
news:BAF05421-386E-4712-8503-A304A1626C24@.microsoft.com...
> Hello,
> I'm getting the following error on the application log of the event
viewer:
> Schedule and Delivery processor cannot connect to the report server
database.
> However I have no trouble to test some reports (e.g. the sample reports
provided with reporting services).
> What could be wrong with my configuration?
> Thanks
> Cesar|||Hello daniel,
On one line of the log says:
"Cannot open database requested in login 'Report Server'. Login fails"
How can I fix that ?
But I had no errors during set up when I configured the account with which reporting services would use to connect to the database.
"Daniel Reib [MSFT]" wrote:
> Can you look in the reportserverservice<date>.log files for more
> information.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Cesar" <Cesar@.discussions.microsoft.com> wrote in message
> news:BAF05421-386E-4712-8503-A304A1626C24@.microsoft.com...
> > Hello,
> >
> > I'm getting the following error on the application log of the event
> viewer:
> >
> > Schedule and Delivery processor cannot connect to the report server
> database.
> >
> > However I have no trouble to test some reports (e.g. the sample reports
> provided with reporting services).
> >
> > What could be wrong with my configuration?
> > Thanks
> > Cesar
>
>

Monday, March 26, 2012

Scheduling a Report based on an event

Friday, March 23, 2012

Scheduler node deadlock message.

Tuesday, March 20, 2012

Scheduled job is not running successfully. Event ID: 208

Scheduled job is not running successfully. Event ID: 208

Scheduled job is not running successfully. Event ID: 208

Tuesday, February 21, 2012

Schedule and Delivery processor cannot connect

T-SQL Script

Blog Archive

About Me