Job requirements

This is taken directly from a job requirement (names are not mentioned to protect the ignorent...I meant Innocent):

The employee must occasionally lift and/or move up to 25 pounds. While performing the duties of this job, the employee is frequently required to stand; walk; sit; talk or hear; use hands to finger, handle, or feel; reach with hands and arms; climb or balance; stoop, kneel, crouch, or crawl.Wow. I didn't realize that the L.A. "freeze" on the adult industry had had that much effect across the country!

-PatP|||The part about "Stoop, crouch, kneel, and crawl" only applies at performance review time.|||OmG you guys...thats too funny.|||By the way, the requirements in the original post apply to an existing job opening for Senior SQL Server DBA, so don't make any mistake, - it is not for construction worker or anything ;)


The difficult ones I find are of course the ones that relate to the review time, though I am not sure that those abilities need to be demonstrated while having to hear or talk ;)|||There's a lesson to be learned here: never ever become a senior! :)|||never ever become a senior! :)or seniorita, as the case may be

Job Names Created for Subscriptions

Hi All,
I'm new to Reporting Services and have just created my first data-driven
subscription for a report. In the SQL Enterprise Manager, the job name seems
to take the shape of a GUID. Is there a way around this so administration is
easier and these names are "human readable"?
Thanks in advance!
Kind regards - FredI'd also like to know the answer to this. The DBAs here likes to keep a
close eye on the jobs and they seem really annoyed by these GUIDs. I pointed
out that they could see it was a Reporting Services job and they could sort
on that column to put them all together but they didn't really consider that
a good solution.sql

Job and Stored Procedure Problems

I've written 2 stored procedures.
Proc 1, cycles through the system table and pulls out the names of all DB's.
Proc 2 is called by Proc 1, after it grabs 1 of the database names. It then
performs a type of backup based on a flag:
F = Full, D = Differential, and T = Transaction Logs.
I capture any errors and return them to Proc 1, so I can formulate an email
giving status.
At the end of Proc 1, I generate an email and ship off, giving the status of
each of the backups.
The process works just fine, if you do the TSQL statement through a query
window, reporting the status of the backup or error message. The problem I
am having, is when i schedule the job. To test it, I took one of my DB's
offline. When I run it through the Query Window, all errors and successes
report just fine.
When I run it through the Job, it fails at the offline database and kills
the entire job. Since the email isn't sent till the end of proc 1, the
email is never being generated, because upon failure of proc 2, it aborts
the entire job with an error.
It still backs up all the databases, just doesn't finish the email portion
of the process.
I've played with the job options, to continue to next step, even though one
doesn't exist, exit with success, doesn't do it, I've even played with SET
XACT_ABORT OFF
Thanks.Hi Kevin
You should be checking the status of the database in sysdatabases to exclude
offline one.
John
"Kevin Antel" wrote:

> I've written 2 stored procedures.
> Proc 1, cycles through the system table and pulls out the names of all DB'
s.
> Proc 2 is called by Proc 1, after it grabs 1 of the database names. It th
en
> performs a type of backup based on a flag:
> F = Full, D = Differential, and T = Transaction Logs.
> I capture any errors and return them to Proc 1, so I can formulate an emai
l
> giving status.
> At the end of Proc 1, I generate an email and ship off, giving the status
of
> each of the backups.
> The process works just fine, if you do the TSQL statement through a query
> window, reporting the status of the backup or error message. The problem
I
> am having, is when i schedule the job. To test it, I took one of my DB's
> offline. When I run it through the Query Window, all errors and successes
> report just fine.
> When I run it through the Job, it fails at the offline database and kills
> the entire job. Since the email isn't sent till the end of proc 1, the
> email is never being generated, because upon failure of proc 2, it aborts
> the entire job with an error.
> It still backs up all the databases, just doesn't finish the email portion
> of the process.
> I've played with the job options, to continue to next step, even though on
e
> doesn't exist, exit with success, doesn't do it, I've even played with SET
> XACT_ABORT OFF
> Thanks.
>
>