Hire a SQL developer

Objective: Conversion of production-ready stored procedures from integration with a commonly used residential construction CRM database (Builder1440) to integration with an alternative software database for the same purpose (Sales Simplicity). Environment: Customer environment consists of multiple, distinct data sources (MS SQL and Firebird). Data access and merging is generally handled through a single, central database (MS SQL) which hosts 450+ stored procedures that query and combine data from the disparate sources. Additionally, the company consists of seven independent, geographic divisions. Each of which may have distinct configurations and requirements for various aspects of the business (commissions, home models, pricing, etc…). Job Overview: This job will require an experienced dba or skilled SQL script developer. Builder1440 (now called Sales1440) is CRM software designed for use in the residential home construction industry ([login to view URL]). Sales Simplicity is a competitive product ([login to view URL]). The customer has numerous stored procedures that query data from a Builder1440 database and combine it with materials, cost, buyer, and sales data from several other sources. The 1440 server is configured as a linked server on a central hub which is a Microsoft SQL server. In most cases, the 1440 data is accessible via views created under a custom database. In all cases where 1440 data is used, the option must exist to query the analogous Sales Simplicity data instead. Tasks: 1. Determine that subset of stored procedures that utilize Builder1440 data. 2. Analyze and compare the Builder1440 and Sales Simplicity schema and develop a comprehensive mapping of data from one database to the other. This analysis must contain a description of points of disparity between the two sources for which there is no obvious correlation. 3. For all points in the existing stored procedures at which Builder1440 data is used, design an efficient and effective method by which either Builder1440 data or Sales Simplicity data can be queried based on the results of the analysis from task 2. a. NOTE: In time, the customer will move all divisions to Sales Simplicity. However, there will be a period during which some divisions are active in Sales Simplicity while others continue to utilize Builder1440. Therefore, it is imperative that on a division basis one data source or the other can be chosen. b. A linked server solution as is currently employed with Builder1440 is preferred if feasible and at least as effective/efficient as comparable alternatives. However, if there are legitimate reasons to consider an alternative design the customer is open to the possibility. 4. Fully implement and test the Builder1440/Sales Simplicity interchange strategy based on the proposed design from task 3. This will require significant and clear communication with the software design team to ensure that any and all changes that alter the output of the existing stored procedures can be resolved in the systems consuming the data. We will be ready to provide copies of each database for the migration, with sample data loaded