Re: The importance of fully qualifying database objects in Queries, Functions etc.

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Even with Administrators, you should always use dbo. prefix for a (slight)
better performance: the SQL-Server will recompile the stored procedures in
its cache much less often and it will take a little less time to compile.

Also and unless you are able to read the futur, you never know when you will
have to crank up the security of your system and start using things such as
user defined SPs and Views for filtering and limiting the access to the data
in the tables.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC


"Patrick Wolf" <ppjwolf@xxxxxxxxxxx> wrote in message
news:uAuRkUyUFHA.580@xxxxxxxxxxxxxxxxxxxxxxx
> Environment: WinXP / SQL Server 2000 (Integrated Authentication) /
> Access 2003 / ADP Access Project
> -------------------------------------------------------------------------------------------------------------
>
> Hi,
>
> -the people developing the database are Administrators who are seemingly
> automatically in the db_owners group.
> -the people using the database are in all kind of groups and will not be
> creating queries, tables, stored procedures etc. but just use an Access
> Project which in turn will access SQL Server.
>
> What is the importance in this setup of fully qualifying database objects
> with owner.table (dbo.table) in queries, views, functions etc.?
> What problems could we run into in the future if we don't do it now (at
> the moment it is working fine for both developers and users)?.
>
> Thank you very much for your suggestions
> Patrick
>


.

Relevant Pages

  • Re: Multilayer applications
    ... > you from being able to make the direct database calls from your GUI. ... I supposed that GUI and the busuness logic layer are different instances. ... I use Sql Queries from my business ... Do you always use the Stored Procedures and never an implemented SQL code? ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: XP COMPATABILITY WITH ACCESS
    ... "DAVE" wrote in message: ... 2002 which only uses queries. ... It seesm that several of the stored procedures did not convert over, ... all i get when i try to open my database is a lot of debug errors. ...
    (microsoft.public.windowsxp.help_and_support)
  • ADO.NET timeout
    ... I have all kinds of stored procedures and queries need to run on the SQL ... Because the database is big, most of the stored procedures and ... seconds to finish, no matter I use ExecuteNonQuery, ExecuteReader, or fill ...
    (microsoft.public.dotnet.framework.adonet)
  • Stored Procedures Vs Views
    ... base over to a SQL Server 2000 database. ... started to move the queries over as stored procedures. ...
    (microsoft.public.access.externaldata)
  • The importance of fully qualifying database objects in Queries, Functions etc.
    ... -the people developing the database are Administrators who are seemingly ... creating queries, tables, stored procedures etc. but just use an Access ... Project which in turn will access SQL Server. ...
    (microsoft.public.access.adp.sqlserver)