new to notifications services and want example of setting up email notifications

I am new to SQL 2005 and want to setup a notification service to email me when a job fails. How do I begin to set that up? Any basic examples I can check out?

This forum is dedicate to SQL Server Notification Services; you'll probably have more luck getting responses in the SQL Server Tools forum (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=84&SiteID=1) or the microsoft.public.sqlserver.server newsgroup.

HTH...

sql

new to notifications services and want example of setting up email notifications

I am new to SQL 2005 and want to setup a notification service to email me when a job fails. How do I begin to set that up? Any basic examples I can check out?

This forum is dedicate to SQL Server Notification Services; you'll probably have more luck getting responses in the SQL Server Tools forum (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=84&SiteID=1) or the microsoft.public.sqlserver.server newsgroup.

HTH...

New Publication - Snapshot Error

Help!
Some genius cancelled a replication job that was very close to completing the Initial Snapshot of a database being replicated (Transactional) from one server to another.
Is the only thing necessary to do a 'Reinitialize' of this publication?
Is there any way around having the tables locked when the Snapshot is being generated?
(This is why the doofus killed the job)
Any help is greatly appreciated!
You might be able to get away with a concurrent snapshot if you are using transactional replication. On your publication properties, clcik the snapshot tab, and select concurrent access during snapshot generation.
Another Snapshot will be generated but there will be far less locking.
If you can kick all your users off the database you can DTS the data over. This is faster than a snapshot.
To get this to work you should
1) create a new database.
2) script out the tables you are replicating, and any other objects you are replicating, and run this script in the new database.
3) publish this database and objects to a second new database on the same server.
4) script out the objects and the stored procedures and then run this in the subscriber.
This way your objects will be the way replication wants them and you will have the necessary replication stored procedures. Then do your DTS and then do a no-sync subscription.
DTS can be twice as fast as a snapshot generation and distribution.
It is critical that you be able to prevent any updates from happening to your publication database while you do this.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"JLS" wrote:

> Help!
> Some genius cancelled a replication job that was very close to completing the Initial Snapshot of a database being replicated (Transactional) from one server to another.
> Is the only thing necessary to do a 'Reinitialize' of this publication?
> Is there any way around having the tables locked when the Snapshot is being generated?
> (This is why the doofus killed the job)
> Any help is greatly appreciated!
|||Thanx!
Any way to buy a copy of your book before August 15?
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:ED801206-889D-42F6-A590-663BC63F3BBA@.microsoft.com...
> You might be able to get away with a concurrent snapshot if you are using
transactional replication. On your publication properties, clcik the
snapshot tab, and select concurrent access during snapshot generation.
> Another Snapshot will be generated but there will be far less locking.
> If you can kick all your users off the database you can DTS the data over.
This is faster than a snapshot.
> To get this to work you should
> 1) create a new database.
> 2) script out the tables you are replicating, and any other objects you
are replicating, and run this script in the new database.
> 3) publish this database and objects to a second new database on the same
server.
> 4) script out the objects and the stored procedures and then run this in
the subscriber.
> This way your objects will be the way replication wants them and you will
have the necessary replication stored procedures. Then do your DTS and then
do a no-sync subscription.
> DTS can be twice as fast as a snapshot generation and distribution.
> It is critical that you be able to prevent any updates from happening to
your publication database while you do this.[vbcol=seagreen]
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
>
> "JLS" wrote:
completing the Initial Snapshot of a database being replicated
(Transactional) from one server to another.[vbcol=seagreen]
being generated?[vbcol=seagreen]
|||no. There may be some proofs out in a month.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"JLS" <jlshoop@.hotmail.com> wrote in message
news:%23qw9qmIWEHA.1380@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Thanx!
> Any way to buy a copy of your book before August 15?
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:ED801206-889D-42F6-A590-663BC63F3BBA@.microsoft.com...
using[vbcol=seagreen]
> transactional replication. On your publication properties, clcik the
> snapshot tab, and select concurrent access during snapshot generation.
over.[vbcol=seagreen]
> This is faster than a snapshot.
> are replicating, and run this script in the new database.
same[vbcol=seagreen]
> server.
> the subscriber.
will
> have the necessary replication stored procedures. Then do your DTS and
then[vbcol=seagreen]
> do a no-sync subscription.
> your publication database while you do this.
> completing the Initial Snapshot of a database being replicated
> (Transactional) from one server to another.
publication?
> being generated?
>

New Job Unable to Copy 200 Line Code Into Command Section

I have a SQL Server 2000 database, I created a new job but I am unable to
copy the 200 lines of code that I created into the command section of the job.
Is there away to expand the New Job Command section?
I cannot use another job step to resolve this issue because I have alot
variables and a cursor used in this job.
This problem is resolve in SQL Server 2005.
Please help me resolve this problem for SQL Server 2000.
Thank You,Joe K. wrote:
> I have a SQL Server 2000 database, I created a new job but I am unable to
> copy the 200 lines of code that I created into the command section of the job.
> Is there away to expand the New Job Command section?
> I cannot use another job step to resolve this issue because I have alot
> variables and a cursor used in this job.
> This problem is resolve in SQL Server 2005.
> Please help me resolve this problem for SQL Server 2000.
> Thank You,
>
200 lines of code in a single job step? That's just insane. Put that
code into a stored procedure, and then use a single EXEC statement in
the job step.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I fully agree with Tracy. If you, for some strange reason, don't want to do this, I believe the
limit is a bit higher at the TSQL level (i.e., the GUI is the limiting factor), so you could have
some more by using sp_add_jobstep.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message news:45BA5D73.3080102@.realsqlguy.com...
> Joe K. wrote:
>> I have a SQL Server 2000 database, I created a new job but I am unable to copy the 200 lines of
>> code that I created into the command section of the job.
>> Is there away to expand the New Job Command section? I cannot use another job step to resolve
>> this issue because I have alot variables and a cursor used in this job.
>> This problem is resolve in SQL Server 2005.
>> Please help me resolve this problem for SQL Server 2000.
>> Thank You,
>>
> 200 lines of code in a single job step? That's just insane. Put that code into a stored
> procedure, and then use a single EXEC statement in the job step.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

New Job Unable to Copy 200 Line Code Into Command Section

I have a SQL Server 2000 database, I created a new job but I am unable to
copy the 200 lines of code that I created into the command section of the job.
Is there away to expand the New Job Command section?
I cannot use another job step to resolve this issue because I have alot
variables and a cursor used in this job.
This problem is resolve in SQL Server 2005.
Please help me resolve this problem for SQL Server 2000.
Thank You,
Joe K. wrote:
> I have a SQL Server 2000 database, I created a new job but I am unable to
> copy the 200 lines of code that I created into the command section of the job.
> Is there away to expand the New Job Command section?
> I cannot use another job step to resolve this issue because I have alot
> variables and a cursor used in this job.
> This problem is resolve in SQL Server 2005.
> Please help me resolve this problem for SQL Server 2000.
> Thank You,
>
200 lines of code in a single job step? That's just insane. Put that
code into a stored procedure, and then use a single EXEC statement in
the job step.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

New Job Unable to Copy 200 Line Code Into Command Section

I have a SQL Server 2000 database, I created a new job but I am unable to
copy the 200 lines of code that I created into the command section of the jo
b.
Is there away to expand the New Job Command section?
I cannot use another job step to resolve this issue because I have alot
variables and a cursor used in this job.
This problem is resolve in SQL Server 2005.
Please help me resolve this problem for SQL Server 2000.
Thank You,Joe K. wrote:
> I have a SQL Server 2000 database, I created a new job but I am unable to
> copy the 200 lines of code that I created into the command section of the
job.
> Is there away to expand the New Job Command section?
> I cannot use another job step to resolve this issue because I have alot
> variables and a cursor used in this job.
> This problem is resolve in SQL Server 2005.
> Please help me resolve this problem for SQL Server 2000.
> Thank You,
>
200 lines of code in a single job step? That's just insane. Put that
code into a stored procedure, and then use a single EXEC statement in
the job step.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I fully agree with Tracy. If you, for some strange reason, don't want to do
this, I believe the
limit is a bit higher at the TSQL level (i.e., the GUI is the limiting facto
r), so you could have
some more by using sp_add_jobstep.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message news:45BA5D73.3080102@.realsqlguy.co
m...
> Joe K. wrote:
> 200 lines of code in a single job step? That's just insane. Put that c
ode into a stored
> procedure, and then use a single EXEC statement in the job step.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

New Job Sql Server Agent error *FIXED*

I am running SQL Server 2005 and recently installed Office Sharepoint Server 2007 on the same server. After the install I receive the following error message while trying to add a new SQL Server Agent Job.

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

Also when I right click on a job to view properties a new job window pops up instead.

I realised that Office Sharepoint Server 2007 installs SQL Server Express and might me causing my issues. I uninstalled Sharepoint however I am still having the same problem.

Can anyone shed some light or have any suggestions?

Installing SP2 solved the problem.|||

I am having the same error when trying to create a job in SQLServer using SSIS package. The SSIS package does a very simple two steps ftp tasks: delete the existing file on the ftp server and copy the new one. Can somebody also share experience or idea on my case as well please.

Thanks

|||

I am have the same issue as Htin. I have run all Windows updates and I am running office 2007.

TITLE: Microsoft SQL Server Management Studio

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

BUTTONS:

OK

|||This problem seems to have been resolved by running the SQL Server SP2.|||

Hi I got the same error but after I install SP 2 for SQL 2005

Any idea how to resolve this problem ?:-)

|||I have succeeded in getting a job deployed but I accessed the Management Studio whilst on the Server so it looks like it's the tools not the server itself where the problem lies.|||I have SQL SERVER 2005 (SP2). I'm having the same problem. I upgraded the server via command prompt (c:/>setup SKUUPGRADE = 1). Still I'm having the same problem. Can any one tell me how to resolve this problem.

New Job Sql Server Agent error

I am running SQL Server 2005 and recently installed Office Sharepoint Server 2007 on the same server. After the install I receive the following error message while trying to add a new SQL Server Agent Job.

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

Also when I right click on a job to view properties a new job window pops up instead.

I realised that Office Sharepoint Server 2007 installs SQL Server Express and might me causing my issues. I uninstalled Sharepoint however I am still having the same problem.

Can anyone shed some light or have any suggestions?

Installing SP2 solved the problem.|||

I am having the same error when trying to create a job in SQLServer using SSIS package. The SSIS package does a very simple two steps ftp tasks: delete the existing file on the ftp server and copy the new one. Can somebody also share experience or idea on my case as well please.

Thanks

|||

I am have the same issue as Htin. I have run all Windows updates and I am running office 2007.

TITLE: Microsoft SQL Server Management Studio

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

BUTTONS:

OK

|||This problem seems to have been resolved by running the SQL Server SP2.|||

Hi I got the same error but after I install SP 2 for SQL 2005

Any idea how to resolve this problem ?:-)

|||I have succeeded in getting a job deployed but I accessed the Management Studio whilst on the Server so it looks like it's the tools not the server itself where the problem lies.

New Job Sql Server Agent error

I am running SQL Server 2005 and recently installed Office Sharepoint Server 2007 on the same server. After the install I receive the following error message while trying to add a new SQL Server Agent Job.

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

Also when I right click on a job to view properties a new job window pops up instead.

I realised that Office Sharepoint Server 2007 installs SQL Server Express and might me causing my issues. I uninstalled Sharepoint however I am still having the same problem.

Can anyone shed some light or have any suggestions?

Installing SP2 solved the problem.|||

I am having the same error when trying to create a job in SQLServer using SSIS package. The SSIS package does a very simple two steps ftp tasks: delete the existing file on the ftp server and copy the new one. Can somebody also share experience or idea on my case as well please.

Thanks

|||

I am have the same issue as Htin. I have run all Windows updates and I am running office 2007.

TITLE: Microsoft SQL Server Management Studio

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

BUTTONS:

OK

|||This problem seems to have been resolved by running the SQL Server SP2.|||

Hi I got the same error but after I install SP 2 for SQL 2005

Any idea how to resolve this problem ?:-)

|||I have succeeded in getting a job deployed but I accessed the Management Studio whilst on the Server so it looks like it's the tools not the server itself where the problem lies.

New job opportunities

One of our clients is in need of following requirements .

OM Designer:-

Location: Mountainview,CA
Duration: Long-term
Startdate: ASAP
No of positions: 6

Skills
8 years of experience
Strong Functional Skills in Order Management and Distribution Modules.
Atleast 3 Implementation experience in Order Management.
Proven experience in designing Business solutions to Customer in OM
based on Business problems or requirements

OM & AR Techno-Functional:-

Location: Mountainview,CA
Duration: Long-term
Startdate: ASAP
No of positions: 6

Skills
6 years of experience
Exclusive Strong Techno-Functional Skills in Order Management and
Distribution Modules & Accounts Receivables modules.
Document Technical Designs, Unit Test Cases and Code.
Maintain Software written by yourself and others
Ensure Code is high Quality.
Good verbal and written communication skills
Solid software engineering skills.
Oracle Development tools - PLSQL, Forms, Reports, Workflow,XML.
Implementation Experience in Oracle Modules: OM, AR.
Nice to have Exposure to tools: Kintana, Teamtrack

OM & SCM Techno-Functional:-

Location: Mountainview,CA
Duration: Long-term
Startdate: ASAP
No of positions: 6

Skills
Strong Techno-Functional Skills in Order Management and Distribution
Modules & Supply Chain (Inv, PO, Shipping, AR) modules.
Document Technical Designs, Unit Test Cases and Code.
Maintain Software written by yourself and others
Ensure Code is high Quality.
Good verbal and written communication skills
Solid software engineering skills.
Oracle Development tools - PLSQL, Forms, Reports, Workflow,XML.
Implementation Experience in Oracle Modules: Inventory, Purchasing(Drop
Ship PO), Third Party Order Fulfillment, EDI Integration.
Nice to have Exposure to tools: Kintana, Teamtrack
6

I2C/AR Techno-Functional:-
Location: Mountainview,CA
Duration: Long-term
Startdate: ASAP
No of positions: 4

Skills
6 years of experience
Minimum 5 years experience in AR as Techno-Functional Consultant
Project experience in and comprehensive knowledge of AR tables and
APIs.
Functional understanding of the AR flow and able to translate into
technical terms
Functional understanding of the AR flow to GL (revenue recognition,
accounting entries) and able to translate into technical terms.
Functional understanding of invoice, credit memos, debit memos,
receipts and chargebacks and able to translate into technical terms
Project experience and comprehensive knowledge of AR Tables and APIs

F2M/P2P Techno-functional:-

Location: Mountainview,CA
Duration: Long-term
Startdate: ASAP
No of positions: 6

Skills
6 years of experience
strong Techno-Functional Skills in GL, PA, CM, FA, AP, PO, iPayables

Release Coordinator:-
Location: Mountainview,CA
Duration: Long-term
Startdate: ASAP
No of positions: 1
Skills
5 years of experience
Detailed knowledge and proven experience with Oracle AOL, Kintana and
VSS(configuration management).
1
Very Good Communication & interpersonal skills
Release management for non production environments(DEV, QA and UAT)
- Coordinating DEV and QA team for Kintana releases
- Kintana Package migration activities(code deployment)
- Submitting builds for migration
- Code Retrofit activities(planning and coordination only)
- Resolving release/code migration issues by discussing with
Engineering and SCM teams
Coordination and follow up with SCM(s/w configuration mgmt) teams for
Patches and environmental issues

Performance Tuning Expert:-

Location: Mountainview,CA
Duration: Long-term
Startdate: ASAP
No of positions: 1

Skills
6 years of experience
strong experience in oracle apps 11i performance tuning with expertise
in distribution and

ATG Dynamo Developer:-

Location: Minneapolis, MN
Duration: Long-term
Startdate: ASAP.

Skills
* Strong experience in JAVA
* ATG Dynamo App framework
* JSP
* Servlets
* Personalization
* Profile management.
* Good to have (ATG Portal Admin)
* Good Communication Skills

If you are interested in the above opportunity, please send your
updated resume with followingdetails

Full Name:
Availability:
Salary/rate:
Contact No.:
Current Location:
Visa Status:

Reply ASAP,
Thanks and Regards,
Kalyan Mudda
Spectraforce Technologies Inc.
919-846-7975 x 302
919-341-8358.
kmudda@.spectraforce.com
www.spectraforce.comRadhesh Reddy (radheshreddy@.gmail.com) writes:
> One of our clients is in need of following requirements .

I hope you don't plan to ask any SQL questions for the next 90 days. In
that case, I will not see them, as you just entered my kill file.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Are you phishing for useful info by any chance? Google & Oracle don't
recruit like that!

*** Sent via Developersdex http://www.developersdex.com ***