How I lay out my T-SQL source code

I have used similar methods of storing my source code, but not to the sophistication that you use.  At one employer, I stored SQL objects in individual and combined files in a version control system.  Each statement needed a sanity check before it to ensure it would be a valid statement.  A C# program was built that combined a tree of changes into a single SQL file which became the deployment code.

I like your use of the C++ preprocessor to define Macros.  I have been wanting something like that and knew of the C++ tool, but had not thought enough outside the box to figure out a way to use it in my projects.  Thanks for the tip.

I have found that it is really helpful to step away from SSMS to write code.  It is too easy to make changes and loose them.  With that said; as I have seen in the last 10 - 15 projects I have been involved in, the biggest hurdle is "how do I get my existing database under control" and the second biggest is - "once I decide on how to control this, how do I get the rest of the people that have access to change objects on boarder with the protocol & procedures".

I appreciate the gentle prodding on this topic Alex.  If you call yourself a professional in the realm of software or databases, this should be a no-brainer to answer.

if object_id(N'objectname') is not null

begin

--create the object

end

go

alter object

or

if it is data manipulation then ensuring the value you are manipulating is not already in place.

Regarding the C++ preprocessor.  I had thought at 1 point of using sqlcmd variables in my code for the marcos in place of your defines.  So in version control much like your suggestion you would see $(MACRONAME) and then just using sqlcmd to deploy with the appropriate variables.  But because the values are only known at run time, now there is another file that needs to be stored in version control.  e.g. the sqlcmd deployment commands.

I am curious if you have explored this option at all.

Thanks,

FindTim

Handy function you've made using the C++ preprocessor. I did not know that was possible!

Where do we report errors we find in the book?

On page 285 it reads "to convert a strong to an integer."  It should read "to convert a string to an integer."  Just the type of error a spell checker will not find.

I use an almost identical solution by using the PPWizard tool from Dennis Bareis (http://www.dennisbareis.com). This is based on REXX scripting and allows me to re-use SQL code. I'll put some examples on my website in September