sorry, let's try it again...

Enterprise manager->server name->management->SQL Server Agent --right click, property -->Job system.

This works on SQL 7 and SQL 2000.

mom

Here is how you can look at what is current set up for job history:

Enterprise Manager-->Server of interest -->management -->job system

This will show the number of maximum job history...

This is really weird. How about login as sa and try to execute your same command. I just wonder if it still give you that error. We...

It depends. Are you a development dba or production dba. development dba are usually very busy working on current project with other people to make sure table and...

Have you tried to schedule it and have sa or the service account for SQL Agent own that task.

The otherway to go arround it is to give your...

Have you try to send mail out using query analyser and check to see if it still give you the same error?

We do hardware replacement every year. we usually have 2 servers to work with. The old server 'A' with old hardware and the new server 'AX1' with new...

I used to be a janitor when I am 7 yrs old.

My first job in the morning is to clean the bathroom. I also went to market to buy...

I haven't got to 30 yet but working on it.

Married with 2 babies (2yrs girl and 13 months boy). I am a full time mom/wife/general contractor as well as...

It is quiet possible, but we have a strick guidline as far as what software can be install in any server. I have not try change the service account...

We don't have that software install on any of our system. I also went out and search for that file in binn directory on local server as well as...

Error from sql server log:

Cannot load the DLL xp_logattach.dll, or one of the DLLs it references. Reason: 126(The specified module could not be found.).

We are trying to experiment with this idea as well.

1st Create a complety new login domain service account.

2nd we added that user to the local user group.

3rd...

Jonathan,

I think we post about the same time. As for your recommendation It works as well but I have never taken that approach.

mom

create PROCEDURE test_sp

@SchoolNum int=NULL --sorry I like integer instead nvarchar(3). I think it is more efficient.

AS

if (@SchoolNum is null)

Begin

select @SchoolNum = '190'

end

select @SchoolNum

go

exec test_sp

--will give you result...