dbo. in vs generated code for stored procedures.

From: Rod Snyder (rod_at_rcsnyder.com)
Date: 10/07/04

  • Next message: Mythran: "Re: dbo. in vs generated code for stored procedures." 
    Date: Thu, 7 Oct 2004 16:06:47 -0400

    We have a team development environment and we just moved to vs.net 2003
    Enterprise so we are now able to create stored procs right out of visual
    studio. In the past we had to use enterprise manager. Our normal procedure
    for db access was to set up a sql user based on the application and use that
    to connect to the application to only execute stored procedures. When we
    created the stored procedures in enterprise manager they defaulted to dbo.
    as the owner/creator. This always caused an error when running the
    application until we physically deleted the two references to
    dbo.[storedproc] out of the vb code. Has anyone else experienced this? I
    have searched extensively and can't find anything similar. We thought moving
    to vs.net2003 and doing the stored procedures there might address this
    issue.

    However, now I'm not sure about the best way to have the stored procedures
    created in Visual Studio. We don't want to use the application connection
    since we only
    want that one to have execute permissions. If we use Windows authentication,
    other developers don't appear to have access to the stored procedure. Also,
    vs.net 2003 -- instead of dbo.[stored proc] inserts
    WindowsAccountName.[storedproc] so I don't think this will alleviate the
    first problem.

    Any suggestions or ways this is handled in other shops.

    Rod

  • Next message: Mythran: "Re: dbo. in vs generated code for stored procedures."

    Relevant Pages

    • sql server connections/user identities
      ... We have a team development environment and we just moved to vs.net 2003 ... In the past we had to use enterprise manager. ... to connect to the application to only execute stored procedures. ... created the stored procedures in enterprise manager they defaulted to dbo. ...
      (microsoft.public.vsnet.general)
    • Re: Fragen zur Applikations-Architektur
      ... > ist - den Ansatz über Enterprise Services oder eben eine ... prüfen ob ich das noch in die Stored Procedures integrieren könnte. ...
      (microsoft.public.de.german.entwickler.dotnet.asp)
    • Re: Getting rid of stored procedures
      ... >> Have an opinion on the effectiveness of Microsoft Embedded newsgroups? ... > The OP's point is that stored stored procedures have their place. ... people either used stored procs all the time or none at all. ... > build a proper CRUD command. ...
      (microsoft.public.dotnet.framework.adonet)
    • Re: Stored procedure;1
      ... "warway" wrote in message ... > and the Enterprise Manager view of the stored procedures don't have ... Sorry - I have seen multiple stored procs with the same name like this ... Do these other PCs have Enterprise Manager? ...
      (microsoft.public.sqlserver.programming)
    • Re: Advatages of Stored Procedures?
      ... stored procedures, you have to know the good and bad. ... stored procs are retained in the procedure cache and the SQL ... Maintenance, as your application ages and needs changed, some stored procs ...
      (microsoft.public.dotnet.framework.adonet)