First Service Pack of SQL Server 2008

May 5, 2009 by 3 Comments

SQL Server 2008 First Service Pack (SP1) is now available. Service Pack 1 (SP1) focused on essential updates only, primarily roll-ups of cumulative updates 1 to 3 and fixes to issues reported through the SQL Server community. SP1 eases deployment and management of Service Packs by introducing Slipstream, Service Pack Uninstall, and Report Builder 2.0 Click Once capability.

List of the bugs that are fixed in SQL Server 2008 Service Pack 1

KB Article Title
944390 FIX: Error message when you connect to a named instance of SQL Server on a client computer that is running Windows Vista or Windows Server 2008: “Specified SQL server not found” or “Error Locating Server/Instance Specified”
955769 FIX: The Shared Memory protocol for an instance of SQL Server 2008 is always enabled and the VIA protocol for the instance is always disabled after you repair the instance
956021 FIX: The About, Execute, and Close buttons are missing when you run the Execute Package Utility in the Chinese (Taiwan) version of Microsoft SQL Server 2008
956031 FIX: Error message when you estimate the compression on a table in SQL Server 2008: “Subquery returned more than 1 value”
956427 You cannot add a cluster node when you install SQL Server 2008 Analysis Services and you do not install the SQL Server 2008 Database Engine
958778 FIX: The default instance name is set incorrectly to SQLEXPRESS when you install SQL Server 2008 Express
959001 FIX: The Log Reader Agent skips some transactions when the Log Reader Agent runs to replicate transactions for a transactional replication in SQL Server 2005 and in SQL Server 2008
959025 FIX: Error message when you call a stored procedure that returns a rowset which has the DBPROP_MAXROWS rowset property or the SSPROP_MAXBLOBLENGTH rowset property specified: “The incoming tabular data stream (TDS) protocol stream is incorrect”
959026 FIX: Error message when you run a DB2 query that uses the WITH UR query hint in SQL Server 2005 Analysis Services and in SQL Server 2008 Analysis Services: “OLE DB error: OLE DB or ODBC error: An unexpected token “WITH” was found following “<Query>”"
961126 FIX: Error message when you run a maintenance plan in SQL Server 2008: “The SQL Server Execute Package Utility requires Integration Services to be installed”
961271 FIX: In a SQL Server 2008 Reporting Services report that contains several levels, some items disappear when you collapse another item
961633 FIX: A SQL Server 2008 Reporting Services report is displayed incorrectly in Mozilla Firefox if the report is displayed by using the ReportViewer control
962900 FIX: Error message when you run a query that involves an outer join operation in SQL Server 2008: “Attempting to set a non-NULL-able column’s value to NULL”
963070 FIX: You cannot edit or debug an SSIS package in BIDS when SQL Server 2008 Enterprise Edition, Standard Edition, Developer Edition, or Evaluation edition is installed without the SSIS feature
963658 FIX: PAGE compression is removed from a SQL Server 2008 data table after you shrink the database
967470 FIX: Error message when you perform an update or a delete operation on a table that does not have a clustered index created in SQL Server 2008: “The operating system returned error 1450″
967984 FIX: When you process a full-text catalog in SQL Server 2008, the operation stops responding
968587 FIX: The aggregate value is incorrect when you design a query that contains some entity groups by using the Report Model Query Designer in SQL Server 2008 or in SQL Server 2005
968599 FIX: Error message when you try to specify the SQL Server 2008 Reporting Services account as the credential for a report server in SharePoint Central Administration: “Unable to connect to Report Server WMI provider”
968693 FIX: A query that uses parameters and the RECOMPILE option returns incorrect results when you run the query in multiple connections concurrently in SQL Server 2008
968829 FIX: Error message when you try to upgrade an instance of SQL Server 2005 to SQL Server 2008: “Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes”
968830 FIX: An incorrect version is displayed on the Instance Selection page when you use SQL Server 2008 Setup to upgrade an instance of SQL Server 2008
968828 FIX: The system objects may not be checked as expected when you use different policy evaluation modes in SQL Server 2008

For full reference of bug list fixed in service pack 1.

You can download SQL Server 2008 SP1 from the Microsoft Download Center.

Filed Under: Microsoft, Technology Tagged With:

Business Process Modeling

January 19, 2009 by Leave a Comment

A business process modeling is a collection or group of related activities or business processes that produce a specific service or product. Business processes are visually represented as diagrams of simple box with arrow graphics and text labels, better known as Business Process Models.

Business Process Modeling Overview:

Business Process Modeling(IDEF0) is the first step in Business Modeling and it is followed by Process Flow Modeling(IDEF3) and Data Flow Diagrams(DFD). In Business Process Modeling, an organization’s functions are represented by using boxes and arrows. Here boxes represent activities and arrows represent the information associated with an activity. Input arrow, Output arrow, Mechanism arrow and Control arrow are the different types of arrows that are used in business process modeling.

The business process modeling is started with a context diagram and it provides a brief overview about the organization’s activity. In order to understand the activities of an organization in a detailed manner, the context diagram is then decomposed into many sub activities diagrams.

Similarly decomposition of context diagram is done in process flow modeling and data flow diagrams. Context diagram is similar to a conceptual data model in data modeling. The following example gives the layout of the context diagram.

 

Ref: www.learndatamodeling.com

Filed Under: Business, Technology

Business Process Management

January 15, 2009 by 1 Comment

Business Process Management, a set of activities, is essential for a new or existing business in a way that it helps an organization to optimize current business processes and future organizational and operational changes.

Business process management is done with the help of different tools that help in capturing, modeling, designing, integrating, deploying, testing, measuring and maintaining several business activities. The success or failure of each company depends on how good or bad it is able to manage the entire life cycle of its processes.

Need for Business Process Management:

  • To plan for a new business or for a new change in the business.
  • To avoid the common mistakes that happens in a project.
  • To document business processes in a common language to help IT and non-IT team members.
  • To draw business modeling and data modeling diagrams and to capture business rules in a way we want them.
  • To implement enterprise architecture or enterprise integration architecture (EAI) or ETL architecture.
  • To measure data by using business intelligence tools.
  • To enhance business to business transactions.

Advantages of Business Process Management (BPM):

BPM Models:

  • BPM’s activities like Modeling, Automating, Monitoring, Analyzing, and improving the business processes helps an organization to get good profits in less time.
  • BPM’s business process models visualize the activities within the organization and business-to-business transactions.
  • BPM’s process flow models visualize the process flows within the organization and business-to-business transactions and the relationships between process flow.
  • BPM’s data flow models visualize the data flow within the organization and business-to-business transactions.
  • BPM’s decomposition diagrams for business process modeling, process flow diagrams and data flow diagrams visualize the processes and activities in a detailed manner.

Workflow:

  • BPM’s workflow helps to define, create, execute, automate and manage processes within the organization and business-to-business-transactions to get more productivity.

Documentation:

  • The entire business process procedures can be documented in a shared multi user repository. This provides technical and non-technical persons to understand the different processes that occur in each departments of the organization, its performance and the outcome of each business processes.

Quality:

  • BPM increases quality and quantity of a product or a service provided by the organization.

Reports:

  • BPM reports can be very useful to the topmost executives of an organization and whoever needs it.

Resources:

  • BPM reduces the working hours of the employees.

Exceptions:

  • BPM reduces the errors and exceptions when compared to a manual process.

Regulations:

  • BPM helps an organization to abide by the regulations of the government.

Business-to-Business Transactions (B2B):

  • BPM is the core of B2B transactions to gain leverage with vendors, customers, consumers, and suppliers.

Competition:

  • Provides significant competitive advantage over competitors.

Simulation:

  • Simulation techniques with different scenarios can be used on business processes to explore the effect of change.
Filed Under: Business, Technology

Data Warehouse and its need

January 12, 2009 by Leave a Comment

Introduction

These days there are so many companies trying to build data warehouses and there are a lot of companies selling Business intelligence products. The new version of SQL Server 2005 has the Business Intelligence Development Studio and this is one of its main upgrade from SQL Server 2000. It enhanced the DTS environment and changed its name to Integration Services (SSIS), which is similar to an ETL tool. It integrated with .NET so it can easily build reports or online applications. Microsoft is definitely putting its energy in the data warehouse business.

Also SQL Server is gaining on the market share of other RDBMSs and most experts said it was because of the BI integration. However, does your company need a data warehouse? And how do you choose the right BI product for your company?

First it must be the business direction that produces the driving force to build the data warehouse and not the IT department. The company must identify the goals and objectives of ‘why install a data warehouse’.

For example, my old company was a bank; it decided to build a data warehouse so it could keep track of a loan from the application process until repayment. One objective was the business wanted to find out how long it took the loan from application status to approval status, and if the loan got denied, they wanted to find out what the reason was. However when the company decided to build the data warehouse, the IT department helped the organization to understand the scope of the project. The business has to identify what the enterprise needs. It has to decide how much they want to spend on the project, what kind of data they want to capture, etc. This helps to determine what kind of hardware, operating system, communication links, RDBMS and application program IT needs. The business also has to understand that it is a continuous project, both business and IT has to decide who is responsible to fix problem, who is responsible for new requests and who is responsible for tuning. It needs continuous support from the business.

The IT department has to know what they need in order to build a successful data warehouse. First they need to understand the business data. It needs an implementation plan, a realistic timeline, a team of people with knowledge to build the data warehouse – a data architect, a data modeler, business analyst, data quality administrator, meta data administrator, security administrator and good database developers. The scope of the project has to be reasonable; sometimes the business tends to ask too much at once, the IT manager has to understand one thing – never takes on too much too fast. It tends to fail.

Data Quality

Data is an important asset to the business; it helps the business to make daily decision and direction of the organization. Data quality is the most important element of the data warehouse. Data quality and integrity can directly affect many decisions. The data warehouse is not just capturing data. It can also minimize data redundancy, increase customer satisfaction, improve data quality, and provide good customer reports. So the business needs to set up a metrics to measure if the data warehouse is successful. The response time, the quality of the data, the satisfaction of the customers are some of the measurements the business needs to look at. If the data is incorrect and no one trusts the data warehouse, it becomes a whole bunch of tables sitting in a database.

In a lot of companies, the data can come from ERP systems, legacy systems, outside sources and even may be Excel sheets on someone’s PC. The data warehouse team has to take responsibility to validate the data, to work with the business to set up business rules and to work with data owner to set up security for the data. This is part of the ETL process.

For example, the ERP system had a customer name ‘John Doe’; the legacy system had a customer name ‘Johnny Doe’. Are they the same person? Did they have the same address? It they did, that meant they were the same person. This is part of the cleansing process. It is important because the customer count will be off if the data is not validated. It may mess up the reports for marketing, sales and the finance departments.

The database has to be well designed to eliminate redundant data. The data has to be standardized and consistent. It also needs to have business rules to process certain data. For example if the customer has an invalid zip code, should it be put in the data warehouse or should it be put in an error report until the data gets corrected. Meta data is one way to standardize the data; it also documents the source of the data, where the data stores in the database, the definition of the data and the business rule of the data. In this way, the IT department can easily identify if the data is in the wrong database or comes from the wrong source; it can also explain the definition of data to the customer.

Business Intelligence Products

So now the company decides to build the data warehouse, how do you find the right tool? First the company has to evaluate what RDBMS to use for the data warehouse. You have to know how much data does the company have, how often does the company need to load into the data warehouse and how fast it needs to load the data. There are SQL Server, Oracle, Teradata, DB2, and others. The hardware, the communication links and the support is also an important factor to consider choosing the right database. After serious consideration, my company decided to use SQL Server 2000 for our data warehouse because of the size of our data warehouse and the cost. We also look ahead the new features of SQL Server 2005 and its integration with .NET for future development.

Then we have to choose the ETL tool. There are a lot of ETL tools in the market, for example Ab Initio, Informatica Power Center, IBM WebSphere as well as good old DTS packages in SQL Server. One of the data warehouse experts had said that the important part of ETL is that the people must understand the data. The best tool is the tool that you can retrieve and load the data efficiently and correctly and is the most cost effective for the company. Do not just look at all the fancy and expensive tools, evaluate every aspect. Is the tool easy to set up? Is the tool easy to learn to use? If it takes a developer six months to learn to use the tool, is it worth the time and effort?

I used Ab Initio to move the same amount of data from Oracle 9i to SQL Server 2000 and at the same time I used DTS package to do the same thing. The response time was almost the same. But Ab Initio costs a lot of money and DTS package is free. I am not saying Ab Initio is not a good product, if the company has to retrieve zillions of data everyday, it is definitely a good product to consider. Just liked I go from place A to place B (approximately 10 miles) and I go there driving a Honda Civic. It is cheap and reliable. At the same time I can also go there driving a Hummer. Do I prefer a Honda Civic than a Hummer? Of course I would like to drive a Hummer if I am as rich as Bill Gates, but my bank account tells me a Honda Civic is good enough! But if I have to drive up to Mount Rushmore in South Dakota in December, I may consider another vehicle. In my case we use good old DTS packages and stored procedures to extract, cleanse and load our data warehouse and it is doing a very fine job.

A business intelligence tool is used to help the customers to access and analyze the data in the data warehouse. After you build the data warehouse, then you have to choose BI tool. It must be the one provide the most benefits to the business and match the business expectations. The tool has to provide security and privacy of the data. The users can access it and learn to use it fast. If it does, then it is a good business intelligence tool. As I said before SQL server 2005 has Business Intelligence Development Studio to do the job. There is also a lot of other companies selling BI products; for example Cognos, Hyperion, and MicroStrategy. The business and IT have to evaluate which product works the best for the customers. Right now we use Cognos for reporting, but with the rising cost of Cognos and with the new features in SQL Server 2005, who knows, anything can change in the future.
Well, does your company need BI and DW? You have to ask your CIO and CTO, and it is up to you to explain to them the importance of a data warehouse to your company, also you have explain all the pros and cons of choosing the right product.

Ref: http://www.sqlservercentral.com/articles/Design/doyouneedadatawarehouse/2460/

Filed Under: Business, Microsoft, Technology Tagged With: , , , , ,
«Older Posts