There are mamy reasons to achieve consolidation, includes but not limited to

• Reducing hardware and infrastructure cost
• Making space for additional hardware
• Centralizing

Lets first understand what consolidation is; consolidation means combining small units of resources into one large single unit. If we talk about in terms of database then a simple example would be brining all dispersed databases from multiple machines into one single machine, again it depends on the circumstances. In the coming paragraphs we will talk the consolidation in detail.

DBCC SHOW_STASTISTICS ('table_name', 'index_name')

Last week I was writing web front end using PHP and SQL Server 2005, after finishing writing the application I planned to deploy the same over my client's web hosting provider.

While writing the application I forgot that this application is supposed to be deployed on a shared hosting environment where database attach is not possible and running SCRIPT is the only option available.

To make sure that the database will go AS-IS as part of deployment I tried using the SQL Server Scripting Wizard but :( instead of generating script for schema and data it simply generated the scheme, another bad luck.

Time was very limited so I had to find some option to make this happen as I worked very hard over the night to finish the application.

I searched over the internet and found "SQL Server Data Publishing Wizard", which generates single SQL script file which can be used not only re-create the database schema, objects but also populate the database with the data. The best part was that the publishing wizard can write directly to the target location instead of creating a script file.

Reference link: http://www.microsoft.com/download/en/confirmation.aspx?id=5498

• ADM (Architecture Development Method)—A process for creating an enterprise architecture that is part of the TOGAF standard.
• application architecture—The architecture of a specific application.
• architect—One whose responsibility is the design of an architecture and the creation of an architectural description.
• architectural artifact—A specific document, report, analysis, model, or other tangible that contributes to an architectural description.
• architectural description—A collection of products (artifacts) to document an architecture.
• architectural framework—A skeletal structure that defines suggested architectural artifacts, describes how those artifacts are related to each other, and provides generic definitions for what those artifacts might look like.
• architectural methodology—A generic term that can describe any structured approach to solving some or all of the problems related to architecture.
• architectural process—A defined series of actions directed to the goal of producing either an architecture or an architectural description.
• architectural taxonomy—A methodology for organizing and categorizing architectural artifacts.
• architecture—The fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution (from IEEE-1471-2000).
• business architecture—An architecture that deals specifically with business processes and business flow.
• business reference model (BRM)—An FEA term that gives a business view of the various functions of the federal government.
• business services segment—An FEA term that refers to a segment that is foundational to most, if not all, political organizations, such as financial management.
• CIO—Chief Information Officer, the executive in charge of information technology in a corporation.
• CIO Council—A council consisting of CIOs from each of the federal governmental agencies that coordinates work related to common interests.
• Clinger-Cohen Act of 1996—See Information Technology Management Reform Act.
• common-systems architectures—A TOGAF term referring to an architecture that is common to many (but not all) types of enterprises, in contrast to foundation architectures and industry architectures.
• component reference model (CRM)—An FEA term that gives an IT view of systems that support business functionality.
• data architecture—The architecture of the data (typically stored in databases) owned by the enterprise.
• enterprise architect—An architect who specializes in enterprise architectures.
• enterprise architecture—An architecture in which the system in question is the whole enterprise, especially the business processes, technologies, and information systems of the enterprise.
• enterprise service—An FEA term referring to a well-defined function that spans political boundaries, such as security management.
• FEA—See Federal Enterprise Architecture (FEA).
• FEAF—See Federal Enterprise Architectural Framework (FEAF).
• FEAPMO—The organization within the OMB that owns and administers the Federal Enterprise Architecture.
• Federal Architecture Program EA Assessment Framework—A benchmark used by the OMB to measure the effectiveness of governmental bodies in using enterprise architecture.
• Federal Enterprise Architectural Framework (FEAF)—An enterprise-architectural framework used by the U.S. federal government to describe how the various governmental agencies and their IT systems are related to each other.
• Federal Enterprise Architecture (FEA)—An architectural description of the enterprise architecture of the U.S. federal government that includes various reference models, processes for creating organizational architectures that fit in with the federal enterprise architecture, and a methodology for measuring the success of an organization in using enterprise architectures.
• foundation architecture—A term used by TOGAF to refer to the most generic of architectures that can be used by any IT organization, in contrast to common systems architectures.
• GAO—See General Accountability Office (GAO).
• Gartner—An IT research and advisory organization.
• gateway—A transfer point of an autonomous system from which messages from the outside world are received or through which messages to the outside world are sent.
• General Accountability Office (GAO)—A branch of the U.S. Government that is responsible for monitoring the effectiveness of different organizations within the U.S. Government.
• industry architecture—A TOGAF term that refers to a architecture that is common to most enterprises within an industry, in contrast to a common-systems architecture and an organizational architecture.
• Information Technology Management Reform Act—An act passed by the U.S. Congress in 1996 that requires all governmental organizations to use effective strategies and frameworks for developing and maintaining IT resources.
• OMB (Office of Management and Budget)—Part of the Executive Office of the President of the U.S. that serves the function of presidential oversight on federal agencies.
• The Open Group Architectural Framework—See TOGAF (The Open Group Architectural Framework) 8.1.
• organizational architecture—A TOGAF term that applies to an architecture that is specific to a particular organization, in contrast to an industry architecture.
• performance reference model (PRM)—An FEA term that gives standard ways of describing terms related to measuring value.
• Return on Investment (ROI)—A measure (in percent) of the business value of a project, based on the increase in profit (either because of increased income or decreased expenses) divided by the cost of the project. For example, a project with a cost of $100,000 that returned $200,000 in increased profit has an ROI of 200 percent.
• ROI—See Return on Investment (ROI).
• segment—An FEA term that refers to a major line-of-business functionality, such as human resources, that might be shared across organizations.
• standards information base (SIB)—A TOGAF term that refers to a collection of information about standards, particularly in the area of open-source.
• TAFIM (Technical Architecture Framework for Information Management)—An architectural framework developed by the Department of Defense and officially discontinued in 2000.
• technical architecture—Usually refers to the architecture of the technical infrastructure within which applications run and interact.
• technical reference model (TRM)—Part of TOGAF, a reference model that gives a common language for various pieces of IT architecture. This term is also used for a similar meaning within FEA.
• TOGAF (The Open Group Architectural Framework) 8.1—An architectural methodology that is controlled by The Open Group.
• Zachman Framework for Enterprise Architectures—An architectural framework in which an enterprise is modeled as 30 or 36 cells, each of which represents an intersection between a stakeholder perspective and an abstraction.