* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download Tampa Bay Division
Survey
Document related concepts
Microsoft Access wikipedia , lookup
Oracle Database wikipedia , lookup
Extensible Storage Engine wikipedia , lookup
Microsoft Jet Database Engine wikipedia , lookup
Database model wikipedia , lookup
Clusterpoint wikipedia , lookup
Relational model wikipedia , lookup
Team Foundation Server wikipedia , lookup
Open Database Connectivity wikipedia , lookup
Healthcare Cost and Utilization Project wikipedia , lookup
Transcript
Bright House Networks Tampa Bay Division Visual Source Save Development Server File Structure Usage Documentation @ = folders forced to the top for convenience @databases = all sql code divided by server and then by database @shared = shared by programs [USE CAUTION CHANGES TO THES FILES AFFECT ALL PROGRAMS!!] @working_folders = container folder for each developer’s working folder @share = a working folder for passing files from one developer to another across the network @projects = container folder for each project the developer works on USE DESCRIPTIVE lower case NAMES WITH WORDS DIVIDED BY UNDERSCORES _ FOR ALL FOLDERS AND FILES i.e. folder_name – file_name.txt EXCEPT SQL DB NAMES (USE DB CASE) VSS Development Server 1) @working_folders - the top level folder containing the folders used by individual developers a. @share - a folder for passing files from one developer to another across the network b. developer_name - the individual developers top level folder i. @projects - the top lever folder containing a separate folder for each project the developer works on (see template descriptions below) ii. any other folders the developer desires that will not be used by all developers 2) dev_software - developer software installation and update files 3) templates - generic file structures and files to be used to save work and help maintain consistency a. platform_name - the top level folder for templates for the specific platform (see template descriptions below) i. template_name - the name of the template which the folders and files below it describe 4) vss_dbs - the top level folder containing the folders for the Visual SourceSafe databases a. project_name - the individual project VSS database folders Web Development Server 1) vss_shadow_folders - the top level folder containing the folders for the individual shadow folders a. project_name - the individual project VSS shadow folders Web Server 1) site_name - the top level folder containing the folders for each web site a. apps - the top level folder for all the applications on the site i. app_name - the individual application folders 6/26/2017 11:40 PM Page 1 of 5 Template Descriptions General 1) template_name – a descriptive name of the generic file structures and files to be used to save work and help maintain consistency a. dev_samples - code whether working or not that demonstrates concepts needed for the project i. platform - the individual folder for each specific platforms samples b. dev_utilities - working code that is used to make development easier c. docs – documents d. platform – the top level folder for files specific to a development platform i. code_type – the individual folder for each specific type of code e. schema – the database schema for the project Cold Fusion 2) @shared - the top level folder containing the folders and files used (or potentially used) by any application a. dev_samples - working code that is used to make development easier i. cold_fusion – - the cold_fusion specific samples ii. java – the java specific samples iii. sql – the sql specific samples b. dev_utilities - working code that is used to make development easier c. docs – documents d. media – the top level folder contain the folders for each type of media i. media_type – the individual media type folder e. platform - the top level folder for files specific to a development platform i. cold_fusion – the top level folder for files specific to Cold Fusion 1. cfc – cold fusion components 2. ctrl – control level code 3. dsp – display level code a. media – the top level folder contain the folders for each type of media i. media_type – the individual media type folder 4. pagelet – pagelets for use in master pages 5. tag – custom tags 6. udf – user defined functions ii. java – the top level folder for files specific to Java 1. ejb – enterprise java beans iii. sql – the top level folder for files specific to SQL 1. dev – files containing SQL code that are in development a. indexes – files that automate the creation of indexes b. other_sql – files that don’t fall into any of the other subfolders c. spp – stored procedures called by the program except reports (spr) d. spr – stored procedures that only return data for a report e. spu – stored procedures that are used for administration or maintenance of the database f. triggers – files that automate the creation of triggers g. views – files that automate the creation of views 2. prod – files containing SQL code that is in production (or is the most stable currently available prior to the release of the project) a. indexes – files that automate the creation of indexes b. other_sql – files that don’t fall into any of the other subfolders c. spp – stored procedures called by the program except reports (spr) 6/26/2017 11:40 PM Page 2 of 5 i. stored_procedure_name – a subfolder used to store previously used revisions of the stored procedure 1. 001_stored_procedure_name.sql – files containing sequentially numbered revisions d. spr – stored procedures that only return data for a report i. stored_procedure_name – a subfolder used to store previously used revisions of the stored procedure 1. 001_stored_procedure_name.sql – files containing sequentially numbered revisions e. spu – stored procedures that are used for administration or maintenance of the database i. stored_procedure_name – a subfolder used to store previously used revisions of the stored procedure 1. 001_stored_procedure_name.sql – files containing sequentially numbered revisions f. triggers – files that automate the creation of triggers g. views – files that automate the creation of views 3) project_name_basic - the top level folder containing the folders and files used in a basic application a. dev_samples - working code that is used to make development easier i. cold_fusion – - the cold_fusion specific samples ii. java – the java specific samples iii. sql – the sql specific samples b. dev_utilities - working code that is used to make development easier c. docs – documents d. media – the top level folder contain the folders for each type of media i. media_type – the individual media type folder e. platform - the top level folder for files specific to a development platform i. cold_fusion – the top level folder for files specific to Cold Fusion 1. cfc – cold fusion components 2. ctrl – control level code 3. dsp – display level code a. media – the top level folder contain the folders for each type of media i. media_type – the individual media type folder 4. pagelet – pagelets for use in master pages 5. tag – custom tags 6. udf – user defined functions ii. java – the top level folder for files specific to Java 1. ejb – enterprise java beans iii. sql – the top level folder for files specific to SQL 1. dev – files containing SQL code that are in development a. indexes – files that automate the creation of indexes b. other_sql – files that don’t fall into any of the other subfolders c. spp – stored procedures called by the program except reports (spr) d. spr – stored procedures that only return data for a report e. spu – stored procedures that are used for administration or maintenance of the database f. triggers – files that automate the creation of triggers g. views – files that automate the creation of views 2. prod – files containing SQL code that is in production (or is the most stable currently available prior to the release of the project) a. indexes – files that automate the creation of indexes 6/26/2017 11:40 PM Page 3 of 5 b. other_sql – files that don’t fall into any of the other subfolders c. spp – stored procedures called by the program except reports (spr) i. stored_procedure_name – a subfolder used to store previously used revisions of the stored procedure 1. 001_stored_procedure_name.sql – files containing sequentially numbered revisions d. spr – stored procedures that only return data for a report i. stored_procedure_name – a subfolder used to store previously used revisions of the stored procedure 1. 001_stored_procedure_name.sql – files containing sequentially numbered revisions e. spu – stored procedures that are used for administration or maintenance of the database i. stored_procedure_name – a subfolder used to store previously used revisions of the stored procedure 1. 001_stored_procedure_name.sql – files containing sequentially numbered revisions f. triggers – files that automate the creation of triggers g. views – files that automate the creation of views f. schema – the database schema for the project 4) sql - the top level folder containing the folders and files used in databases and sql a. @databases – the top level folder containing folders and files used in databases i. database_server_name (in the case of the database server name i.e. UPPER, lower, MixEd) 1. database_name (in the case of the database server name i.e. UPPER, lower, MixEd) a. sql - use the sql template below b. sql – the top level folder for files specific to SQL i. dev – files containing SQL code that are in development 1. indexes – files that automate the creation of indexes 2. other_sql – files that don’t fall into any of the other subfolders 3. spp – stored procedures called by the program except reports (spr) 4. spr – stored procedures that only return data for a report 5. spu – stored procedures that are used for administration or maintenance of the database 6. triggers – files that automate the creation of triggers 7. views – files that automate the creation of views ii. prod – files containing SQL code that is in production (or is the most stable currently available prior to the release of the project) 1. indexes – files that automate the creation of indexes 2. other_sql – files that don’t fall into any of the other subfolders 3. spp – stored procedures called by the program except reports (spr) a. stored_procedure_name – a subfolder used to store previously used revisions of the stored procedure i. 001_stored_procedure_name.sql – files containing sequentially numbered revisions 4. spr – stored procedures that only return data for a report a. stored_procedure_name – a subfolder used to store previously used revisions of the stored procedure i. 001_stored_procedure_name.sql – files containing sequentially numbered revisions 5. spu – stored procedures that are used for administration or maintenance of the database a. stored_procedure_name – a subfolder used to store previously used revisions of the stored procedure 6/26/2017 11:40 PM Page 4 of 5 i. 001_stored_procedure_name.sql – files containing sequentially numbered revisions 6. triggers – files that automate the creation of triggers 7. views – files that automate the creation of views 6/26/2017 11:40 PM Page 5 of 5