Post reply

Windows Security login and creating dbo.TheView

  • October 6, 2006 at 8:18 pm

    #174372

    We have a consultant whom we have given access into our SQL Server 2000 databases to develop views and stored procs for reporting purposes (intranet website and various crystal reports). Her login is a Windows Security login, tied to her domain account. When she creates a view/proc/UDF, she can not create it as dbo.ReportView1 (for example), instead she has to create it as jdoe.ReportView1 (Jane Doe). This makes it very difficult to manage the crystal reports' security, and it forces all the consumers of these database objects to use the fully qualified name, instead of just ReportView1.

    Am I doing something wrong with her security config? Would making her a member of the db_owner db role allow her to create dbo.ReportView1? Is there a better way to manage all this?

    Thanks!

    Gary

  • October 9, 2006 at 8:00 am

    This was removed by the editor as SPAM

  • October 12, 2006 at 7:04 am

    #665463

    Yup she needs to be a dbo and prefix her code with the dbo. prefix when creating objects. Or pass the scripts to someone who is dbo. Do you really allow development against a live environment??

    [font="Comic Sans MS"]The GrumpyOldDBA[/font]
    www.grumpyolddba.co.uk
    http://sqlblogcasts.com/blogs/grumpyolddba/

  • October 12, 2006 at 7:14 am

    #665466

    Thanks for the reply. We'll add her to db_owner to facilitate this development.

    Also, she's developing her views and procs on a reporting server/database, not our production OLTP db.

    Thanks!

    Gary

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply