DOWNLOAD PDF SQL SERVER 2005 FOR DEVELOPERS

Size: px

Start display at page:

Download "DOWNLOAD PDF SQL SERVER 2005 FOR DEVELOPERS"

Tracey Palmer
5 years ago
Views:

1 Chapter 1 : SQL Server Upgrade Considerations for DBAs and Developers Microsoft SQL Server Compact Edition (SQL Server Compact Edition) is designed for developers who need light weight, in process relational database solution for their applications that can be developed and deployed on desktop, tablet PC and mobile devices. Experience in implementing business logic usingtriggers, Indexes, Views and Stored procedures. Extensive Knowledge of advance query concepts e. Experienced hands inquery tuning and performance tuning. Transformation of data from one server to other servers using tools like bulk copy program BCP, data transformation services, data conversions from legacy systems tosql server. Excellent analytical, communication and interpersonal skills. Proficient in technical writing and presentations and a good team player. Prepare detailed statistical reports in MS Access and MS Excel to track progress of weekly, monthly and quarterly customers and sales growth. Reviewed existing business procedures and recommended and implemented changes. Responsible for setting preferences for various ad-hoc requests and distribution of tasks. Maintained Windows Server for small business. Trouble shoot problems with the sales terminal including network related issues. CMS helps the Delta agent to help the customer to book the flights tickets, as well as it maintains customer profile account, feature bookings, enquires etc. Gathered requirements from business analyst. Developed physical data models and created DDL scripts to create database schema and database objects Designed data models using Erwin. Wrote user requirement documents based on functional specification. Created new tables, written stored procedures, triggers for Application Developers and some user defined functions. Created SQL scripts for tuning and scheduling. Involved in performing data conversions from flat files into a normalized database structure. Developed source to target specifications for Data Transformation Services. Developed functions, views and triggers for automation Extensively used Joins and sub-queries to simplify complex queries involving multiple tables and also optimized the procedures and triggers to be used in production. Provided disaster recovery procedures and policies for backup and recovery of Databases. Created DTS package to schedule the jobs for batch processing. Involved in performance tuning to optimize SQL queries using query analyzer. Created indexes, Constraints and rules on database objects for optimization. Managing historical data from various heterogeneous data sources i. Used linked tables, pass through queries and many other access features also wrote code in Visual Basic to perform some complex reporting tasks. Page 1

2 Chapter 2 : Upgrading from SQL Developer Edition SQL Server is pretty much the Microsoft standard for server based relational databases. I bought this product in conjunction with Microsoft Visual Studio standard edition, and they are a good pair. This problem might occur when you use any program to connect to SQL Server. An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. This problem might occur when SQL Server is not configured to accept remote connections. To configure SQL Server to allow remote connections, you must complete these steps: Enable remote connections on the instance of SQL Server that you want to connect to from a remote computer. This article describes how to complete each of these steps. To do this, follow these steps: On the Surface Area Configuration for Services and Connections page, expand Database Engine, click Remote Connections, click Local and remote connections, click the appropriate protocol to enable for your environment, and then click Apply. Note Click OK when you receive the following message: Changes to Connection Settings will not take effect until you restart the Database Engine service. Important These steps may increase your security risk. These steps may also make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We recommend the process that this article describes to enable programs to operate as they are designed to, or to implement specific program capabilities. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this process in your particular environment. If you choose to implement this process, take any appropriate additional steps to help protect your system. We recommend that you use this process only if you really require this process. Click Start, and then click OK. Note When you run the SQL Server Browser service on a computer, the computer displays the instance names and the connection information for each instance of SQL Server that is running on the computer. If you are using a different firewall, see your firewall documentation for more information. To obtain an instance ID, follow these steps: To open Windows Firewall, click Start, click Run, type firewall. In the Add a Program window, click Browse. Repeat steps 1 through 3 for each instance of SQL Server that needs an exception. Page 2

3 Chapter 3 : PPS on SQL Server Developer Edition Hi all, I have a question - can SQL Server Developer Edition be used as a test environment for developing/testing applications. According to MS documentation the Developer is licensed for a. Appendix Introduction The goal of business intelligence BI systems is to enable better, more informed, and faster decisions. Hence any discussion of real-time business intelligence must be in the context of how close to real time the information must be to support those decisions. What constitutes real-time information can vary widely for different business activities, even within a single enterprise. For example, considering a chain of retail outlets: An analyst using historical data as input to the sales forecast for the next period would likely only need information as of the last month. A marketing manager evaluating the success of a campaign, and responsible for deciding how long the campaign should run, would need much more timely information, probably no more than one day old. A store manager might be making frequent decisions during the day; for example, deciding when to put a perishable item on sale. The manager would need information that was certainly no more than a few hours out of date. Many times a combination of up-to-date and historical information is necessary. For example, while it may be useful for the store manager to know the number of sales of a particular item so far this morning, it is more useful if he can put that information in the context of the average number sales of that same item on the same day of the week over the last year. Reports can include data from different systems. However, this means we no longer have "one version of the truth. These include the consolidations that were applied, the treatment of discounts, and the approach to currency conversions. This means that the business rules embodied in the DW load process must also be embodied in the reports or applications that combine data from the two systems. This can result in a less agile and more error-prone system. This could lead to the making of decisions that are based on incorrect information. Ideally, we want a single source that produces data that is close enough to real time to support all decision makers in the different scenarios. So what are the barriers that prevent business intelligence BI systems from supplying truly real-time data? Barriers to Obtaining Real-Time BI It should be stressed that there are many formidable challenges to obtaining real-time BI data, some of which are not addressable by technology. It is important to keep this in mind, as many presentations of Enterprise Information Interchange EII technologies appear to trivialize the extent of the problem. Barriers to obtaining data that is truly real-time include the following: It is necessary to provide an historical view. Often, the original source systems do not provide historical data at all; therefore, it is necessary to maintain a separate copy of the data, with full history, in a DW. It is necessary to coordinate with business processes and across systems. It might be meaningless to perform a particular analysis until certain business processes are complete. For example, in our simple retail chain example, store-to-store comparisons might not be meaningful until all stores, in all time zones, have closed. Similarly, the mechanisms by which some legacy systems are updated might set a lower limit on the latency that is achievable. Frequently the data must go through a transformation process to enforce data quality. Depending on the complexity of those transformations and the volume of data, it might simply not be cost effective to reduce the load time below a certain level. It is often necessary to integrate data from multiple data sources, which, even in the absence of significant transformations, might commonly be handled by transformation processes, thereby creating a separate store. The goal of providing satisfactory user performance is often at odds with true real-time results. Reporting directly from the source system certainly provides real-time information, but generally the common aggregate-level queries do not perform well against the systems that are orientated for frequent update. Nor could we often tolerate such a query load being placed on our transactional systems. Thus, often a separate store must be maintained, with special attention paid to providing precomputed aggregates likely using Analysis Services. Maintaining those aggregates on each update to the source data takes time. Continually reporting on data from a system that is constantly being updated requires that we consider the issue of data consistency. Even if the data in a report is sufficiently up-to-date, how do we ensure that the report is immediately delivered to the necessary decision makers when they need it? Such considerations mean that the user is often a long way from the original source data, as shown in Figure 1. Each Page 3

4 link in the chain introduces an additional time delay. Barriers to real-time BI The source transactional systems in each store are updated immediately from point-of-sale registers. Every day, data from all stores is consolidated, and extensive transformations applied to clean the data before it is loaded into a DW. Once loaded, a process is initiated to reprocess the Analysis Services cubes that are used for all user access. After the cube is processed on a staging server, it is validated and then transferred to the production server where it is available for user reporting. Sometime after the cube is refreshed, the relevant manager runs a report against the cube, sees the changed information, and finally! Breaking Down the Barriers Although some barriers are difficult to address by technology, there are a number of features in both SQL Server Analysis Services and other components of the SQL Server product that facilitate providing more timely information to end-users. Pushing data into Analysis Services. This means that the same task that extracts and cleans the data can directly refresh the cube. Combining heterogeneous data sources. An Analysis Services cube can be sourced from data drawn from different heterogeneous sources. The data is combined by Analysis Services and presented in a unified manner to the user. The SQL Server relational engine includes an additional transaction isolation level allowing the reader to obtain a snapshot view of the data. This is exploited by Analysis Services. This means that a cube can be processed, such that even if the process takes many minutes, a consistent view of the data is seen through the cube. Updating the Analysis Services cube incrementally. As in Analysis Services, it is possible to reduce the time required to refresh the Analysis Services cube through the use of partitions, where the impact of updates can be limited so that only a small part of the cube is actually affected. In addition, it is possible to process a cube incrementally so that new fact rows can be added to the existing cache. Analysis Services builds on this by also allowing the incremental update of dimensions, catering for the case where new dimensions records are only added, and never updated. Analysis Services introduces the ability to define how the cube should be refreshed to reflect changes to the source data. These proactive caching policies allow the business demands for up-to-date data to be balanced against the need for high performance. Obtaining notification from Analysis Services. By means of integration with Notification Services, it is possible to subscribe to data changes of interest. These technologies can be used in isolation or in tandem. In many cases they will make it easier to provide real-time BI. An example of a simplified architecture, applicable in some simple cases, is shown below, where the Analysis Services cube is built directly over the source databases. A simplified architecture Note: Even in such simple cases, it is often a better practice to build the cube over a database that is a replicated copy of the actual source OLTP database. The cost of maintaining such a replica is outweighed by the advantage of relieving the transaction system from extra overhead. The source transactional systems in each store are updated immediately from point-of-sale registers. Every twenty minutes, proactive caching policies ensure that the cube is incrementally refreshed to reflect the new data. If a user has subscribed to a KPI that has changed status, then an message containing a URL to the relevant report is sent directly to them. The remainder of this paper goes into detail on these features, focusing on those that are new to Analysis Services Analysis Services is included as one of the possible destinations, allowing the transformed data to be piped directly to a cube. This covers the load of both partitions and dimensions, and includes the ability to load data incrementally. New to Analysis Services, dimensions can be loaded incrementally. This is particularly relevant for those cases where dimension rows are only added, not updated, as is the case for type II dimensions. A client that starts such a transaction is guaranteed that all the data they read during the course of the transaction is as it was at the start of the transaction, even if updates are being committed concurrently by other users. Processing a cube over changing data can be problematic if it is not isolated from changes of other users. For example, the Product dimension might be processed, and then before partition processing completes, a new product might be entered, along with a sale for that product. The sale might then get picked up in the partition processing, leading to an apparent referential integrity error. Analysis Services can, at the discretion of the developer, exploit snapshot isolation. If a data source has this policy set, then Analysis Services starts a snapshot transaction at the start of processing, and all objects are processed from that same snapshot. It should be noted that there is no large, fixed overhead required to obtain a snapshot. There is, however, a cost that is incurred by a slight overhead on all updates made during the course of the transaction. For example, while Product and Sales data might come Page 4

5 from the main enterprise DW, the Quotas might be drawn from a small, departmental database. Analysis Services will issue the necessary queries to join the data across the different sources. The SQL Server database need not contain any dataâ for example, there might be data from two Oracle databases joined together using the query processor of a third SQL Server database. Top Of Page Defining Caching Policies Analysis Services provides high query performance by maintaining a cache of the underlying data in a form optimized for analytical queries, often including precomputed aggregations. The presence of such a cache raises a number of important questions: What should be done when the underlying data changes, and therefore the cache becomes stale? How often should the cache be refreshed? How should queries be answered while the cache refresh is underwayâ from the stale cache, or by instead reverting to the underlying source, which would result in poorer query performance but up-to-date data? How do we even know that a change has occurred to the source data? How often do we check? The new Analysis Services proactive caching feature provides a way for the cube designer to define policies that balance the business needs for performance against those for real-time data. The available policy settings allow for a variety of system behaviors. Also, due to the strong need for up-to-date data, if the cache refresh is not completed within a short period of time, the system will revert to relational OLAP ROLAP mode, sending queries directly to the underlying database until the cache refresh completes. The cube has been processed from the data in the relational database. An update occurs to the underlying database. Analysis Services is notified later via an event. Chapter 4 : Where to download MS SQL Server Developer Edition? - Super User Hi everyone, I have uninstalled the version of SQL Server and used an advanced version of SQL Express I have been successful in configuring remote connections and enabling Named Pipes and TCP/IP using this version. Chapter 5 : Get Free SQL Server Developer Edition By Microsoft My Tec Bits Once the program is open click SQL Server Services. Look for an entry named SQL Server (YOUR INSTANCE NAME HERE). Copy and try to go into Managment Studio and login as localhost\your INSTANCE NAME HERE and see what happens. Chapter 6 : Install SQL Server Developer on WINDOWS 8 - CodeProject SQL Server Developer Edition System Requirements Published: November 7, The following system requirements cover SQL Server Developer Edition on bit and x64 platforms, as well as Itanium-based systems. Chapter 7 : SQL Server Developer Edition - Licensing I then uninstalled SQL Server from the server and rebooted the server. Once this was complete, I reinstalled the Developer Edition onto the Server and made sure that I kept the exact same install paths for all of my instances (4 of them). Chapter 8 : MS SQL Server Developer Resume Phoenix, AZ - Hire IT People - We get IT done Find great deals on ebay for sql server developer. Shop with confidence. Chapter 9 : Developer's Guide to SQL Server, A InformIT Discover how Microsoft SQL Server offers database developers the optimal combination of a tightly integrated development and data management platform. The rich and flexible programming environment in SQL Server allows you to leverage your existing skills and utilize familiar tools to build robust, secure, scalable applications. Page 5

This tutorial will help computer science graduates to understand the basic-to-advanced concepts related to data warehousing.

This tutorial will help computer science graduates to understand the basic-to-advanced concepts related to data warehousing. About the Tutorial A data warehouse is constructed by integrating data from multiple heterogeneous sources. It supports analytical reporting, structured and/or ad hoc queries and decision making. This