Can't set the owner to the current login

I'm using express edition, compatibility set to 2005.

I'm logged in as DOMAIN\user, using windows authentication.

When I try to set the owner to this login, I get a "login does not exist on the server" error. Setting the owner to sa works fine.

Any fix to this problem ? Also - can I just work with the owner set to sa or can this cause problems in the future ?

Thanks.

If you could supply a little code that reproduces the error we could probably get an answer for you. What objects are you trying to own?

Yes, you can set the owner to sa, but then you have to work with the object as that login. It would be better to have that object owned by someone with only the rights that they absolutely need.

|||

The property that I'm trying to set is the database owner - in the database properties' files page. I need to do this in order to use diagrams, which are not available without a valid owner.

|||I see. Express doesn't allow diagrams.|||

Buck,

Thank you for trying to help.

The diagrams work fine - but the thing is that I have to set the owner to sa in order to work with them. The problem is that although I am logged in as DOMAIN\user, the server claims there is no such login when I try to set the database owner to that login.

|||

u may be login as Domain/User but in the database the user mapped to this login may be different .. check that...

SP_helpLogins 'Domian/Username' -- to get all the users mapped to this login

Madhu

|||

You know what - you're right! I was working on the older Express versions.

http://blogs.msdn.com/vsdata/archive/2004/09/30/236215.aspx

They have indeed put the diagrams back into Express.

Anyway, you seem to have a different issue, then. Have you tried putting the domain\user in the sysadmins group in SQL Server? I don't suggest leaving them there, but that might help you narrow the problem down. You only need to be in the db_owner role, but you can go high and bring the user account to that role later.

What message are you getting in the logs about this?

|||

I'm sorry, but I'm a newbie to sqlserver.

I guess I need to do some more reading before I can try to do these things (like putting the domain\user in the sysadmins group or using SP_helpLogins). I'm using Mannagement Studio Express and I can't find the correct way to do it.

sql

Cant see the username in the Owner Combo box during job creation

Hi
use dbname
go
Select * from sysusers
"Double_B" <bharatbutani@.gmail.com> wrote in message
news:1150966319.684458.270690@.i40g2000cwc.googlegroups.com...
> Hi All
> Am trying to schedule a job , but when I try selecting the username for
> the Owner... I dont see the username in th list , I cant even type the
> name of the user in the combo box ...
> The username exists in the logins of my SQL Server...
>
> Could you please help !!!!!!!
>
> Thanks
>What version of SQL Server?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Double_B" <bharatbutani@.gmail.com> wrote in message
news:1150966319.684458.270690@.i40g2000cwc.googlegroups.com...
> Hi All
> Am trying to schedule a job , but when I try selecting the username for
> the Owner... I dont see the username in th list , I cant even type the
> name of the user in the combo box ...
> The username exists in the logins of my SQL Server...
>
> Could you please help !!!!!!!
>
> Thanks
>|||Hi All
Am trying to schedule a job , but when I try selecting the username for
the Owner... I dont see the username in th list , I cant even type the
name of the user in the combo box ...
The username exists in the logins of my SQL Server...
Could you please help !!!!!!!
Thanks|||Hi
use dbname
go
Select * from sysusers
"Double_B" <bharatbutani@.gmail.com> wrote in message
news:1150966319.684458.270690@.i40g2000cwc.googlegroups.com...
> Hi All
> Am trying to schedule a job , but when I try selecting the username for
> the Owner... I dont see the username in th list , I cant even type the
> name of the user in the combo box ...
> The username exists in the logins of my SQL Server...
>
> Could you please help !!!!!!!
>
> Thanks
>|||What version of SQL Server?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Double_B" <bharatbutani@.gmail.com> wrote in message
news:1150966319.684458.270690@.i40g2000cwc.googlegroups.com...
> Hi All
> Am trying to schedule a job , but when I try selecting the username for
> the Owner... I dont see the username in th list , I cant even type the
> name of the user in the combo box ...
> The username exists in the logins of my SQL Server...
>
> Could you please help !!!!!!!
>
> Thanks
>sql

Cant see the username in the Owner Combo box during job creation

Hi All
Am trying to schedule a job , but when I try selecting the username for
the Owner... I dont see the username in th list , I cant even type the
name of the user in the combo box ...
The username exists in the logins of my SQL Server...
Could you please help !!!!!!!
ThanksHi
use dbname
go
Select * from sysusers
"Double_B" <bharatbutani@.gmail.com> wrote in message
news:1150966319.684458.270690@.i40g2000cwc.googlegroups.com...
> Hi All
> Am trying to schedule a job , but when I try selecting the username for
> the Owner... I dont see the username in th list , I cant even type the
> name of the user in the combo box ...
> The username exists in the logins of my SQL Server...
>
> Could you please help !!!!!!!
>
> Thanks
>|||What version of SQL Server?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Double_B" <bharatbutani@.gmail.com> wrote in message
news:1150966319.684458.270690@.i40g2000cwc.googlegroups.com...
> Hi All
> Am trying to schedule a job , but when I try selecting the username for
> the Owner... I dont see the username in th list , I cant even type the
> name of the user in the combo box ...
> The username exists in the logins of my SQL Server...
>
> Could you please help !!!!!!!
>
> Thanks
>

can't see DB on SQL 2005 with SQL management studio

I am having a strange issue with SQL Management studio express. I can
log via the front end, but I do not see the DB for which this user is
"owner"
This is not the odd part. The odd part is that if I log in through a
3rd party front end such as EMS sql manager lite I do see the database
I own, and can manipulate it as I please. Can anyone suggest a reason
for this. Here are details of the setup just in case. The DB server
only has one DB other then the default system DB's. The owner of the db
I am having issue with has full permissions on the DB, but is not a
member of ANY server roles. There is a firewall on the machine but it
is allowing tcp connections on 1433. I have not set any connection
restrictions. The only major security change done on the server was to
use:
use master
Revoke View any database from public
go
AND
use *db I am working with*
Exec Sp_changedbowner ' *user that will own the db I am working with* '
Hi
Have you logged out/in since changing the owner of the database? Have you
tried to create a new database as that login, and can you see it? Have you
applied SP1?
John
"pr0f1t" wrote:

> I am having a strange issue with SQL Management studio express. I can
> log via the front end, but I do not see the DB for which this user is
> "owner"
> This is not the odd part. The odd part is that if I log in through a
> 3rd party front end such as EMS sql manager lite I do see the database
> I own, and can manipulate it as I please. Can anyone suggest a reason
> for this. Here are details of the setup just in case. The DB server
> only has one DB other then the default system DB's. The owner of the db
> I am having issue with has full permissions on the DB, but is not a
> member of ANY server roles. There is a firewall on the machine but it
> is allowing tcp connections on 1433. I have not set any connection
> restrictions. The only major security change done on the server was to
> use:
> use master
> Revoke View any database from public
> go
> AND
> use *db I am working with*
> Exec Sp_changedbowner ' *user that will own the db I am working with* '
>
|||that is a fantastic suggestion. I don't knwo why I did not try this
first. Yes the new DB is visible if I make this user owner. So why is
the origional DB not visible if this user is owner of that as well? Any
thoughts
John Bell wrote:[vbcol=seagreen]
> Hi
> Have you logged out/in since changing the owner of the database? Have you
> tried to create a new database as that login, and can you see it? Have you
> applied SP1?
> John
> "pr0f1t" wrote:
|||that is a fantastic suggestion. I don't knwo why I did not try this
first. Yes the new DB is visible if I make this user owner. So why is
the origional DB not visible if this user is owner of that as well? Any
thoughts
|||Hi
That sounds like the change of ownership has not been reflected in the other
database. For the new database did you create the database as the login or
change the database to be owned by the login?
If you log in as a sysadm you should be able to see that database?
Try changing the owner again to a different login and then change it back.
If you run SELECT * FROM master.sys.databases what does it return?
Try regranting the VIEW ALL DATABASES to public and then just deny it to
specific logins.
What version of SQL 2005 are you using?
John
"pr0f1t" wrote:

> that is a fantastic suggestion. I don't knwo why I did not try this
> first. Yes the new DB is visible if I make this user owner. So why is
> the origional DB not visible if this user is owner of that as well? Any
> thoughts
>
> John Bell wrote:
>
|||*dbname*5NULL0xC1F615C4866765479D8B0AD5FD9FDEAA2006-10-31
14:53:43.06080SQL_Latin1_General_CP1_CI_AS0MULTI_USER0000ONLINE0000OFF03SIMPLE1TORN_PAGE_DETECTION1100000000000000000000009063F0BE-B2B1-4A45-9036-8775AAB1B47A00NOTHING0
is the result of SELECT * FROM master.sys.databases
I am running SQL Server 9.0.2047. I tried to change the ownership of
the DB but it only results in errors pretaining to object and schema
ownershipo, but I cannot seem to change the ownership to another user.
Ifs there a way to do this with TSQL? I have one user that essentially
needs to hve ownership of the DB, and access via a front end
porefereably Microsoft SQL managment studio express.
John Bell wrote:
|||Hi
Can you post the exact error number and message that occurs when you try to
change the owner? I assume you are using sp_changedbowner to do this?
Try creating a new user and changing the schema ownership to them
John
"pr0f1t" wrote:

> *dbname*5NULL0xC1F615C4866765479D8B0AD5FD9FDEAA2006-10-31
> 14:53:43.06080SQL_Latin1_General_CP1_CI_AS0MULTI_USER0000ONLINE0000OFF03SIMPLE1TORN_PAGE_DETECTION1100000000000000000000009063F0BE-B2B1-4A45-9036-8775AAB1B47A00NOTHING0
>
> is the result of SELECT * FROM master.sys.databases
> I am running SQL Server 9.0.2047. I tried to change the ownership of
> the DB but it only results in errors pretaining to object and schema
> ownershipo, but I cannot seem to change the ownership to another user.
> Ifs there a way to do this with TSQL? I have one user that essentially
> needs to hve ownership of the DB, and access via a front end
> porefereably Microsoft SQL managment studio express.
>
> John Bell wrote:
>

can't see DB on SQL 2005 with SQL management studio

I am having a strange issue with SQL Management studio express. I can
log via the front end, but I do not see the DB for which this user is
"owner"
This is not the odd part. The odd part is that if I log in through a
3rd party front end such as EMS sql manager lite I do see the database
I own, and can manipulate it as I please. Can anyone suggest a reason
for this. Here are details of the setup just in case. The DB server
only has one DB other then the default system DB's. The owner of the db
I am having issue with has full permissions on the DB, but is not a
member of ANY server roles. There is a firewall on the machine but it
is allowing tcp connections on 1433. I have not set any connection
restrictions. The only major security change done on the server was to
use:
use master
Revoke View any database from public
go
AND
use *db I am working with*
Exec Sp_changedbowner ' *user that will own the db I am working with* 'Hi
Have you logged out/in since changing the owner of the database? Have you
tried to create a new database as that login, and can you see it? Have you
applied SP1?
John
"pr0f1t" wrote:

> I am having a strange issue with SQL Management studio express. I can
> log via the front end, but I do not see the DB for which this user is
> "owner"
> This is not the odd part. The odd part is that if I log in through a
> 3rd party front end such as EMS sql manager lite I do see the database
> I own, and can manipulate it as I please. Can anyone suggest a reason
> for this. Here are details of the setup just in case. The DB server
> only has one DB other then the default system DB's. The owner of the db
> I am having issue with has full permissions on the DB, but is not a
> member of ANY server roles. There is a firewall on the machine but it
> is allowing tcp connections on 1433. I have not set any connection
> restrictions. The only major security change done on the server was to
> use:
> use master
> Revoke View any database from public
> go
> AND
> use *db I am working with*
> Exec Sp_changedbowner ' *user that will own the db I am working with* '
>|||that is a fantastic suggestion. I don't knwo why I did not try this
first. Yes the new DB is visible if I make this user owner. So why is
the origional DB not visible if this user is owner of that as well? Any
thoughts
John Bell wrote:[vbcol=seagreen]
> Hi
> Have you logged out/in since changing the owner of the database? Have you
> tried to create a new database as that login, and can you see it? Have you
> applied SP1?
> John
> "pr0f1t" wrote:
>|||that is a fantastic suggestion. I don't knwo why I did not try this
first. Yes the new DB is visible if I make this user owner. So why is
the origional DB not visible if this user is owner of that as well? Any
thoughts|||Hi
That sounds like the change of ownership has not been reflected in the other
database. For the new database did you create the database as the login or
change the database to be owned by the login?
If you log in as a sysadm you should be able to see that database?
Try changing the owner again to a different login and then change it back.
If you run SELECT * FROM master.sys.databases what does it return?
Try regranting the VIEW ALL DATABASES to public and then just deny it to
specific logins.
What version of SQL 2005 are you using?
John
"pr0f1t" wrote:

> that is a fantastic suggestion. I don't knwo why I did not try this
> first. Yes the new DB is visible if I make this user owner. So why is
> the origional DB not visible if this user is owner of that as well? Any
> thoughts
>
> John Bell wrote:
>|||*dbname* 5 NULL 0xC1F615C4866765479D8B0A
D5FD9FDEAA 2006-10-31
14:53:43. 060 80 SQL_Latin1_General_CP1_CI_AS 0 MU
LTI_USER 0 0 0 0 ONLINE 0 0
0 0 OFF 0 3 SIMPLE 1 TORN_PAGE_DETECTIO
N 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 9063F0BE-B2B1-4A45-9036-8775AAB1B47A 0 0 NOTHING 0
is the result of SELECT * FROM master.sys.databases
I am running SQL Server 9.0.2047. I tried to change the ownership of
the DB but it only results in errors pretaining to object and schema
ownershipo, but I cannot seem to change the ownership to another user.
Ifs there a way to do this with TSQL? I have one user that essentially
needs to hve ownership of the DB, and access via a front end
porefereably Microsoft SQL managment studio express.
John Bell wrote:|||Hi
Can you post the exact error number and message that occurs when you try to
change the owner? I assume you are using sp_changedbowner to do this?
Try creating a new user and changing the schema ownership to them
John
"pr0f1t" wrote:

> *dbname* 5 NULL 0xC1F615C4866765479D8B0A
D5FD9FDEAA 2006-10-31
> 14:53:43. 060 80 SQL_Latin1_General_CP1_CI_AS 0 MU
LTI_USER 0 0 0 0 ONLINE 0
0 0 0 OFF 0 3 SIMPLE 1 TORN_PAGE_DETECT
ION 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 9063F0BE-B2B1-4A45-9036-8775AAB1B47A 0 0 NOTHING 0
>
> is the result of SELECT * FROM master.sys.databases
> I am running SQL Server 9.0.2047. I tried to change the ownership of
> the DB but it only results in errors pretaining to object and schema
> ownershipo, but I cannot seem to change the ownership to another user.
> Ifs there a way to do this with TSQL? I have one user that essentially
> needs to hve ownership of the DB, and access via a front end
> porefereably Microsoft SQL managment studio express.
>
> John Bell wrote:
>

can't see DB on SQL 2005 with SQL management studio

I am having a strange issue with SQL Management studio express. I can
log via the front end, but I do not see the DB for which this user is
"owner"
This is not the odd part. The odd part is that if I log in through a
3rd party front end such as EMS sql manager lite I do see the database
I own, and can manipulate it as I please. Can anyone suggest a reason
for this. Here are details of the setup just in case. The DB server
only has one DB other then the default system DB's. The owner of the db
I am having issue with has full permissions on the DB, but is not a
member of ANY server roles. There is a firewall on the machine but it
is allowing tcp connections on 1433. I have not set any connection
restrictions. The only major security change done on the server was to
use:
use master
Revoke View any database from public
go
AND
use *db I am working with*
Exec Sp_changedbowner ' *user that will own the db I am working with* 'Hi
Have you logged out/in since changing the owner of the database? Have you
tried to create a new database as that login, and can you see it? Have you
applied SP1?
John
"pr0f1t" wrote:
> I am having a strange issue with SQL Management studio express. I can
> log via the front end, but I do not see the DB for which this user is
> "owner"
> This is not the odd part. The odd part is that if I log in through a
> 3rd party front end such as EMS sql manager lite I do see the database
> I own, and can manipulate it as I please. Can anyone suggest a reason
> for this. Here are details of the setup just in case. The DB server
> only has one DB other then the default system DB's. The owner of the db
> I am having issue with has full permissions on the DB, but is not a
> member of ANY server roles. There is a firewall on the machine but it
> is allowing tcp connections on 1433. I have not set any connection
> restrictions. The only major security change done on the server was to
> use:
> use master
> Revoke View any database from public
> go
> AND
> use *db I am working with*
> Exec Sp_changedbowner ' *user that will own the db I am working with* '
>|||that is a fantastic suggestion. I don't knwo why I did not try this
first. Yes the new DB is visible if I make this user owner. So why is
the origional DB not visible if this user is owner of that as well? Any
thoughts
John Bell wrote:
> Hi
> Have you logged out/in since changing the owner of the database? Have you
> tried to create a new database as that login, and can you see it? Have you
> applied SP1?
> John
> "pr0f1t" wrote:
> > I am having a strange issue with SQL Management studio express. I can
> > log via the front end, but I do not see the DB for which this user is
> > "owner"
> > This is not the odd part. The odd part is that if I log in through a
> > 3rd party front end such as EMS sql manager lite I do see the database
> > I own, and can manipulate it as I please. Can anyone suggest a reason
> > for this. Here are details of the setup just in case. The DB server
> > only has one DB other then the default system DB's. The owner of the db
> > I am having issue with has full permissions on the DB, but is not a
> > member of ANY server roles. There is a firewall on the machine but it
> > is allowing tcp connections on 1433. I have not set any connection
> > restrictions. The only major security change done on the server was to
> > use:
> >
> > use master
> > Revoke View any database from public
> > go
> >
> > AND
> >
> > use *db I am working with*
> > Exec Sp_changedbowner ' *user that will own the db I am working with* '
> >
> >|||that is a fantastic suggestion. I don't knwo why I did not try this
first. Yes the new DB is visible if I make this user owner. So why is
the origional DB not visible if this user is owner of that as well? Any
thoughts|||Hi
That sounds like the change of ownership has not been reflected in the other
database. For the new database did you create the database as the login or
change the database to be owned by the login?
If you log in as a sysadm you should be able to see that database?
Try changing the owner again to a different login and then change it back.
If you run SELECT * FROM master.sys.databases what does it return?
Try regranting the VIEW ALL DATABASES to public and then just deny it to
specific logins.
What version of SQL 2005 are you using?
John
"pr0f1t" wrote:
> that is a fantastic suggestion. I don't knwo why I did not try this
> first. Yes the new DB is visible if I make this user owner. So why is
> the origional DB not visible if this user is owner of that as well? Any
> thoughts
>
> John Bell wrote:
> > Hi
> >
> > Have you logged out/in since changing the owner of the database? Have you
> > tried to create a new database as that login, and can you see it? Have you
> > applied SP1?
> >
> > John
> >
> > "pr0f1t" wrote:
> >
> > > I am having a strange issue with SQL Management studio express. I can
> > > log via the front end, but I do not see the DB for which this user is
> > > "owner"
> > > This is not the odd part. The odd part is that if I log in through a
> > > 3rd party front end such as EMS sql manager lite I do see the database
> > > I own, and can manipulate it as I please. Can anyone suggest a reason
> > > for this. Here are details of the setup just in case. The DB server
> > > only has one DB other then the default system DB's. The owner of the db
> > > I am having issue with has full permissions on the DB, but is not a
> > > member of ANY server roles. There is a firewall on the machine but it
> > > is allowing tcp connections on 1433. I have not set any connection
> > > restrictions. The only major security change done on the server was to
> > > use:
> > >
> > > use master
> > > Revoke View any database from public
> > > go
> > >
> > > AND
> > >
> > > use *db I am working with*
> > > Exec Sp_changedbowner ' *user that will own the db I am working with* '
> > >
> > >
>|||*dbname* 5 NULL 0xC1F615C4866765479D8B0AD5FD9FDEAA 2006-10-31
14:53:43.060 80 SQL_Latin1_General_CP1_CI_AS 0 MULTI_USER 0 0 0 0 ONLINE 0 0 0 0 OFF 0 3 SIMPLE 1 TORN_PAGE_DETECTION 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 9063F0BE-B2B1-4A45-9036-8775AAB1B47A 0 0 NOTHING 0
is the result of SELECT * FROM master.sys.databases
I am running SQL Server 9.0.2047. I tried to change the ownership of
the DB but it only results in errors pretaining to object and schema
ownershipo, but I cannot seem to change the ownership to another user.
Ifs there a way to do this with TSQL? I have one user that essentially
needs to hve ownership of the DB, and access via a front end
porefereably Microsoft SQL managment studio express.
John Bell wrote:|||Hi
Can you post the exact error number and message that occurs when you try to
change the owner? I assume you are using sp_changedbowner to do this?
Try creating a new user and changing the schema ownership to them
John
"pr0f1t" wrote:
> *dbname* 5 NULL 0xC1F615C4866765479D8B0AD5FD9FDEAA 2006-10-31
> 14:53:43.060 80 SQL_Latin1_General_CP1_CI_AS 0 MULTI_USER 0 0 0 0 ONLINE 0 0 0 0 OFF 0 3 SIMPLE 1 TORN_PAGE_DETECTION 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 9063F0BE-B2B1-4A45-9036-8775AAB1B47A 0 0 NOTHING 0
>
> is the result of SELECT * FROM master.sys.databases
> I am running SQL Server 9.0.2047. I tried to change the ownership of
> the DB but it only results in errors pretaining to object and schema
> ownershipo, but I cannot seem to change the ownership to another user.
> Ifs there a way to do this with TSQL? I have one user that essentially
> needs to hve ownership of the DB, and access via a front end
> porefereably Microsoft SQL managment studio express.
>
> John Bell wrote:
>

Can't run my scheduled job which accesses a linked server: other options?

In SQL 2000, change the job owner to sysadmin.
In SQL 2005, change the job security context.
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
<ryan_willow@.hotmail.com> wrote in message
news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...
>I have a stored procedure in a database on a server, and this stored
> procedure uses a linked server.
> The login I was given is only granted DBO permissions on this database.
> I am trying to set this up so that the above stored procedure runs once
> per month, so I naturally tried to set up a Job which would do this.
> I have discovered from another group that:
> "You cannot access a linked server from a TSQL jobstep if you aren't
> sysadmin."
> So: How can I automatically run this stored procedure once per month
> under these conditions?
> Thanks,
> Ryan
>I'm in SQL 2000.
I cannot change the job owner because my permissions do not allow this.
Apparently a dbo user named 'User' can only create a job with owner
'User'. I am trying to implement this without having to step outside
my dbo security level. Is this going to be possible, and if so how?
Thanks.
Arnie Rowland wrote:[vbcol=seagreen]
> In SQL 2000, change the job owner to sysadmin.
> In SQL 2005, change the job security context.
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another certification Exam
>
> <ryan_willow@.hotmail.com> wrote in message
> news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...|||That will not be possible without coordination with the server
administrator. Since Jobs have the potential for significant performance
issues as well as security issues for the server, the security context for
Jobs is sysadmin. (in SQL2000).
And of course a SQL Server Administrator is probably not going to allow you
to have permission to create or change a job because of the potential that
it could execute any code or activity under the sysadmin security context.
Jobs are a 'Server' level activity -NOT a database level activity. Even if a
job is confined to a single database, it still operates as a server level
activity.
That changes with SQL 2005.
--
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
"Ryan" <ryan_willow@.hotmail.com> wrote in message
news:1151017863.128715.208750@.g10g2000cwb.googlegroups.com...
> I'm in SQL 2000.
> I cannot change the job owner because my permissions do not allow this.
> Apparently a dbo user named 'User' can only create a job with owner
> 'User'. I am trying to implement this without having to step outside
> my dbo security level. Is this going to be possible, and if so how?
> Thanks.
> Arnie Rowland wrote:
>|||Very informative, thanks Arnie.
Arnie Rowland wrote:[vbcol=seagreen]
> That will not be possible without coordination with the server
> administrator. Since Jobs have the potential for significant performance
> issues as well as security issues for the server, the security context for
> Jobs is sysadmin. (in SQL2000).
> And of course a SQL Server Administrator is probably not going to allow yo
u
> to have permission to create or change a job because of the potential that
> it could execute any code or activity under the sysadmin security context.
> Jobs are a 'Server' level activity -NOT a database level activity. Even if
a
> job is confined to a single database, it still operates as a server level
> activity.
> That changes with SQL 2005.
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another certification Exam
>
> "Ryan" <ryan_willow@.hotmail.com> wrote in message
> news:1151017863.128715.208750@.g10g2000cwb.googlegroups.com...|||I have a stored procedure in a database on a server, and this stored
procedure uses a linked server.
The login I was given is only granted DBO permissions on this database.
I am trying to set this up so that the above stored procedure runs once
per month, so I naturally tried to set up a Job which would do this.
I have discovered from another group that:
"You cannot access a linked server from a TSQL jobstep if you aren't
sysadmin."
So: How can I automatically run this stored procedure once per month
under these conditions?
Thanks,
Ryan|||In SQL 2000, change the job owner to sysadmin.
In SQL 2005, change the job security context.
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
<ryan_willow@.hotmail.com> wrote in message
news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...
>I have a stored procedure in a database on a server, and this stored
> procedure uses a linked server.
> The login I was given is only granted DBO permissions on this database.
> I am trying to set this up so that the above stored procedure runs once
> per month, so I naturally tried to set up a Job which would do this.
> I have discovered from another group that:
> "You cannot access a linked server from a TSQL jobstep if you aren't
> sysadmin."
> So: How can I automatically run this stored procedure once per month
> under these conditions?
> Thanks,
> Ryan
>|||I'm in SQL 2000.
I cannot change the job owner because my permissions do not allow this.
Apparently a dbo user named 'User' can only create a job with owner
'User'. I am trying to implement this without having to step outside
my dbo security level. Is this going to be possible, and if so how?
Thanks.
Arnie Rowland wrote:[vbcol=seagreen]
> In SQL 2000, change the job owner to sysadmin.
> In SQL 2005, change the job security context.
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another certification Exam
>
> <ryan_willow@.hotmail.com> wrote in message
> news:1151015746.073933.305090@.r2g2000cwb.googlegroups.com...|||That will not be possible without coordination with the server
administrator. Since Jobs have the potential for significant performance
issues as well as security issues for the server, the security context for
Jobs is sysadmin. (in SQL2000).
And of course a SQL Server Administrator is probably not going to allow you
to have permission to create or change a job because of the potential that
it could execute any code or activity under the sysadmin security context.
Jobs are a 'Server' level activity -NOT a database level activity. Even if a
job is confined to a single database, it still operates as a server level
activity.
That changes with SQL 2005.
--
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
"Ryan" <ryan_willow@.hotmail.com> wrote in message
news:1151017863.128715.208750@.g10g2000cwb.googlegroups.com...
> I'm in SQL 2000.
> I cannot change the job owner because my permissions do not allow this.
> Apparently a dbo user named 'User' can only create a job with owner
> 'User'. I am trying to implement this without having to step outside
> my dbo security level. Is this going to be possible, and if so how?
> Thanks.
> Arnie Rowland wrote:
>|||Very informative, thanks Arnie.
Arnie Rowland wrote:[vbcol=seagreen]
> That will not be possible without coordination with the server
> administrator. Since Jobs have the potential for significant performance
> issues as well as security issues for the server, the security context for
> Jobs is sysadmin. (in SQL2000).
> And of course a SQL Server Administrator is probably not going to allow yo
u
> to have permission to create or change a job because of the potential that
> it could execute any code or activity under the sysadmin security context.
> Jobs are a 'Server' level activity -NOT a database level activity. Even if
a
> job is confined to a single database, it still operates as a server level
> activity.
> That changes with SQL 2005.
> --
> Arnie Rowland, YACE*
> "To be successful, your heart must accompany your knowledge."
> *Yet Another certification Exam
>
> "Ryan" <ryan_willow@.hotmail.com> wrote in message
> news:1151017863.128715.208750@.g10g2000cwb.googlegroups.com...