Hi Marios

I like the way you handled this task and the great information it provides. However, I had some errors on the 2000 script thats making me do a lot...

My issue was due to the AD name in active directory and the case SQL was authenticating. Again this is a non default set up and the server is case...

It does go away with SQL or SA account. But the AD user is a SYSadmin account also so permissions is not the issue.

version product_level edition

-------------------- -------------------- ------------------------------

9.00.3175.00 ...

keep the ideas coming!!

For more clarification.....

If I try to create a login right now, there is no way to create it except by using uppercase as shown below.

USE [master]

GO

CREATE LOGIN [EBEbird] FROM WINDOWS...

Yes but it does not fix the problem, just hides it.

No matter what I type to add the login, it has to be uppercase. If I try creating it with lower case, it does not find a AD user and...

When I try to change user to lower case it errors and states invalid characters. Must be because of the case sensitive.

Keep the ideas comming.....

When I change the job owner to lower case it automaticlly changes it back to upper case. This is due to my login all uppercase which is also brought in...

I'm having the same permission problems. I use to put my agent operators in the sqlAgentOperatorRole in the msdb database. Thisa would allow them to go under the jobs and...

I was able to add the user to the Distributed COMN Users group and it started working.

Thanks

Sorry I failed mention this but I already have them in sysadmin role. This is more to a issue with security on the server (windows 2003 server) rather then in sql server.

Thanks

If the sheet has a true name, you would use it for the name. I have seen the default sheet name as sheet1$ too.

Here is an article that might help...

[sheet 1$] is the default name of the first excel work sheet. I am select everthing in the sheet and trowing it in a temp table. the hdr=yes tell SQL...