Thanks you so much! That did it.

Thanks

Tried that, but got the below error:

PS SQLSERVER:\> $server.DetachDatabase("dbPSXTest", FALSE)

At line:1 char:36

+ $server.DetachDatabase("dbPSXTest", FALSE)

+ ...

All very odd 🙂

Thanks for your comments.

I've solved it by adding the proc to one of my SSIS packages, so it's definitely running as Domain\SQLJobs now and running fine.

Would love...

Cool, thanks for the article.

If this were true, then the job would not fail giving the error 🙂

The server principal "Domain\SQLServerAgent" is not able to access the database "Database1" under...

Nope, service account has no permissions at all.

The job is executing a stored proc that is not in msdb anyway, thus would need more than permissions to msdb anyway.

OK sure, but if there is no proxy set and the AgentServiceAccount Domain\SQLServerAgent does not have access to SQL, what account does the job then run under when it successfully...

Some more info after lots of testing:

The problem is with the email part of the stored proc. And because it is in an if statement, it is the first time...

Thank you Mack

Yes, they are terribly spoilt and they don't know it 🙂

Unfortunately I won't be able to take away their rights 🙁 Would looove to though LOL

Will probably have...

Great, thank you Grant. Found cached_time in sys.dm_exec_procedure_stats - exactly what I was looking for.

Thank you. That makes perfectly sense, didn't think about it like that 🙂

I will definately bug MS on it.

Thanks Paul. I will look into your suggestions.

Jim, yes, it is the actual setting for the max memory that changed. 🙂 It is also very odd that it was set...

Memory was set with sp_configure.

Services was not stopped and started as it is not required, SQL immediately adjusts memory when using reconfigure in 2008, which it did with no problem...

Thanks guys. Think there might have been open transactions or replication that were not allowing me to shrink the file to less than the initial size. 🙂

You would think that if you cannot shrink the file below the initial size they'd at least give us the possibility to be able to decrease the initial size then.......

I need to shrink the database files to less than the current initial size of the database. Shrinkfile, shrinkdatabase and logbackup only shrinks to the initial size of the database...