I found the error and was able to get the script to run on SQL Server 2008 R2. I needed to change every occurrence of 'path' to 'T.[path]'.

Thanks!

Thanks for those suggestions, but I am getting a syntax error when I try to run them. Could you please send me the entire script with the change.

Thanks

The script is very useful. I know it was designed for SQL 2005, however it also seems to work on SQL 2008. I have tried it on several...

Yes, that is essentially correct. The developers have dbo rights in the development databases, which implicitly gives them all necessary rights on stored procedures i.e., execute, view definition, etc.

However...

I think you are missing the point. I do script out object level permissions with the Create\Alter script. However the view definition permission does not exist for the...

That is the way it occurs except that in this case the dba scripts out the stored procedures and permissions. The problem is that there is no view definition...

Unfortunately, a user is still unable to grant explicit view definition permissions to themselves using this method, so there is no apparent solution other than globally granting permissions on...

Thanks for the input. It does look like granting permissions at the schema level is the best option. In most cases, this will probably work globally for all...

I tried disabling Forescout and running Processmon while I attempted a re-install of SP2. Unfortunately, it failed again and this is running in production.

Since I am unfamiliar with processmon,...

I know it does seem like a permissions issue, but I set all those as you mentioned and still got the error. The files are in the same directory...

Unfortunately, after checking all the file and directory permissions I was still unable to install SP2.

I got the same error as before. But doesn't the execution of the SP...

The client connections that fail are those from an MS Access front end using ODBC and from within SSMS itself. The first connection attempt tends to fail and then...

I seemed to have solved the problem by restarting SSIS and SQL Server Agent. I thought I had at least re-started the SSIS service after making my changes, but...

Finally, I broke down and restarted SQL Server over lunch. That did the trick and everything seems to be working normally once again. Just for completeness, I'm running...

Finally, I broke down and restarted SQL Server over lunch. That did the trick and everything seems to be working normally once again.

Thanks