>>>One note - it is a good idea to always provide schema in the FROM section even if your default schema is dbo. Also, in the future versions of SQL Server two parts name will be required.
>>
>>Yes, I was just trying to explain in my rough words why sometimes you see those double (or even triple dots). In my case I try to always use DB.Schema.Table in all my queries, and try to have schemas other than dbo (sometimes I am lazy in this one, but in my heart I know I shouldn't)
>
>We're using default dbo schema and I'm fixing the forms as I'm working on them to add dbo. to the tables. If we ever change schema to something more meaningful for better separation, lots of forms /code I already fixed will broke.
We try to have schemas for applications, for example HumanResources, Vehicles, Purchases etc all have their own schema, but we are just migrating to SQL so we are re-writing anyways, but I understand that changing once it is working is very complicated (or at least tedious and error-prone :)
"The five senses obstruct or deform the apprehension of reality."
Jorge L. Borges?
"Premature optimization is the root of all evil in programming."
Donald Knuth, repeating C. A. R. Hoare
"To die for a religion is easier than to live it absolutely"
Jorge L. Borges