msdb and model are on the same Plan, so the job will report a failure even if it did successfully backup the model transaction log, as it failed with msdb....

Hi,

Could you not just stop the SQL Agent?

Cath

Hi mlimp,

To find the name of the account that is running the SQL Agent, look in Windows Services. That's the account that needs permissions on the folder. You...

Have a look in the properties for those databases, you'll find that they're both in Simple recovery model, which means you can't backup the transaction log. If you want...

Hi Dave,

VARCHAR(MAX) was only introduced in SS2K5, so you won't be able to use it in 2K.

Cath

Hi Cookie,

You could create your trace and put it into a scheduled job. In the Schedule tab of the job you can drop down the box just beneath the...

Hi Sandy,

Chris's command will only work in SS2K5 and then only for databases that have a compatibility of 90. The database you restored from SS2K will have a compatibility...

Gail's already answered that - (re)read the last two lines of her last email.

Hi,

There is no Agent for Express. Microsoft suggests using Windows Scheduled Tasks and there's a free tool at http://www.lazycoding.com/products.aspx. There are probably a lot more solutions...

Hi,

Was it SQL Server Express you installed? If so, it doesn't have the Agent. If not Express, have you tried rerunning setup?

Have you checked the Agent Properties yet? If you know for sure that no-one has deleted anything from msdb and you have the correct permissions to view job history...

Check out PIVOT in BOL. Your query would look something like this:

SELECT Number

, [1] AS Station1

, [2] AS Station2

, [3] AS Station3

FROM

(SELECT Number

, Station

, [Value]

FROM Stations) s

PIVOT

(SUM([Value]) FOR...

Hi,

Check how the job history has been configured. In SSMS right click on the SQL Server Agent node and select Properties, then click the History tab.

Hope that...

I know what you mean, it's kind of comforting to have two sets of backups. If that's what you want, you could take your native SQL backups, then have...

That happened to a few of the servers I administer recently. It turned out to be a problem with DNS rather than SQL Server. Have you had a...