Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
There is nothing to email... We do all of our SQL work in Microsoft Query Analyzer 2000, a tool that is part of the SQL 2000 installation. What i pointed out is that if everything in the database is created in code (in this case Transact-Sql) then it can be version controlled easily using CVS. But if you start doing the design and changes in Enterprise Manager and then you script out the result you will get a nightmarish type of source files where it is not really possible to do meaningful diffs to see what happened between revisions. /Bo -----Original Message----- From: Vitaly Krivosheev [mailto:vk at liga.net] Sent: den 11 november 2003 10:44 To: bo.berglund at telia.com Subject: RE: [cvsnt] Re: Managing SQL Server source with CVS? Hello, Bo. Can you email me your app ? Thanks in advance. ---- WBR, Shatl -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] Sent: Monday, November 10, 2003 10:06 PM To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: [cvsnt] Re: Managing SQL Server source with CVS? we have decided to do it this way: 1. *ALL* of the database definitions are done in Transact-SQL 2. We separate them in various sql files depending on purpose/target: - Security, like logins, users, passwords etc (master) - Backup stuff, we schedule automatic backups (master) - Structural info like table design and indexes etc (user) - Views (user) - Stored procedure definitions (user) - System data, fixed definitions etc (user) - Metadata, language dependent strings etc (user) 3. These sql files are written in QueryAnalyzer, tested there and then saved as sourcecode. 4. We have stored these files under CVS version control (of course) 5. We also have created a Delphi app that takes a list of these files and connects to the SQL server and then executes them to set up the database correctly. NOTE: The scripts we do are fully rerunnable, that means we make sure that all changes are done in a non-destructive way on live databases. The procedures are dropped then reinserted, columns are never dropped etc. When we started out we tried using Enterprise Manager but soon found that it was a nightmare to manage and support this code so we hired an SQL sexpert and restarted it from scratch. Now we are in good shape. /Bo (Bo Berglund, developer in Sweden) _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs