April 21, 2012 at 3:35 pm
I am very new to SQL Server programming and am finding lots of tutorials and information on the SQL language itself. I have played around a bit with the Microsoft SQL Server Mangement Studio (Express Version) and know the basics of creating tables and queries with the graphical tools.
I'm finding that most of the on-line examples use scripts to create tables and relationships so I'm supposing that's the way most programmers work.
But what I'm not clear on and can't find much information on is how real-life developers working on serious projects manage all these scripts. Do you have a separate file for the scripts for each table? What about stored procedures? How are they handled?
I would appreciate some pointers on where to find more information (on-line or books) on some practical real-world development examples.
Thanks,
Lorne
April 21, 2012 at 4:09 pm
lorne 64075 (4/21/2012)
I am very new to SQL Server programming and am finding lots of tutorials and information on the SQL language itself. I have played around a bit with the Microsoft SQL Server Mangement Studio (Express Version) and know the basics of creating tables and queries with the graphical tools.I'm finding that most of the on-line examples use scripts to create tables and relationships so I'm supposing that's the way most programmers work.
But what I'm not clear on and can't find much information on is how real-life developers working on serious projects manage all these scripts. Do you have a separate file for the scripts for each table? What about stored procedures? How are they handled?
I would appreciate some pointers on where to find more information (on-line or books) on some practical real-world development examples.
You are correct, (most) serious organizations use scripts. The reason why is very simple, serious organizations rely on some flavour of the Three-Tier Development Model where new objects and changes to existing objects are first applied to the Development environment, after basic testing are applied to the Test environment and after user acceptance testing are applied to the Production environment. Scripting is the only way you can ensure that exactly the same change was applied to each environment.
Code is managed relying on Version Control software - plenty of information on the net.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.April 21, 2012 at 7:19 pm
I'll second everything Paul said, and add that most serious developers rely heavily on tools to help them in developing scripts and interacting with source control, many times all those functions are integrated into the same tool.
SQL Server Management Studio (SSMS) is the de facto development tool for T-SQL, but Visual Studio is also a great option. Both can integrate with various version control systems. In the case of SSMS additional software is needed to integrate with a version control system, e.g. redgate SQL Source Control[/url].
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
April 22, 2012 at 5:58 am
This might help a bit: http://www.simple-talk.com/books/sql-books/the-red-gate-guide-to-sql-server-team-based-development/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply