我一直在测试从8月和SQL Server 2008 R2 CTP与SQL Server功能执行试验多服务器管理从一个中央服务器上。你也可以监控数据层应用程序和数据库服务器上他们的活动。Visual Studio 2010允许您创建一个DAC(数据层应用程序组件)是一个应用程序需要的数据对象的定义。这可能包括明显的数据库对象,如表、视图和存储过程,也像登录服务器级别对象。它给了一个方便的应用程序的部署单位。VS 2010生成一个新的文件扩展名,即.dacpac。想法是,开发团队可以定义这个在开发应用程序,以便它可以移交给DBA团队部署应用程序。登台服务器的部署可能会最终进入生产阶段之前系统和集成测试。以前,我们必须准确填写表单定义的数据库和应用程序之间的依赖关系容易出错,因为断开连接。如果你已经有一个数据库定义您可以创建一个使用ssm .dacpac回顾性2008 R2(数据库/任务)。 This will gather together the database objects and server logins for deployment. Either way, you can then use the new Deploy Data-tier Application wizard to actually deploy those objects (without the data) to your staging server for final testing. You will have to organize another method for pumping the data across but SSIS is perfect for this. Once the DAC has been deployed to the staging server you can then monitor performance of that Data-tier application through the SQL Server Utility, in a similar way to Managed Instances are monitored. The SSU, new in R2, provides a centralized dashboard view of the health of your servers and database applications. You can drill down to view individual storage utilization or focus in on the most common queries and their performance metrics using provided reports that you can customize or create yourself. Once deployed to production, the idea is that you can do the same with your production servers. If you use the Data Collector on the database server, even more information will find its way to the UMDW, the Utility Management Data Warehouse. To me, this is the Enterprise Performance Data Warehouse, used to analyse performance of our multiple servers and applications. The way this is done, is that jobs are setup on the Managed Instances to collect performance data through Perfmon and running DMVs. These metrics are then uploaded to the UCP (Utility Control Point) that hosts the UMDW. Recommend a separate server for this database...I was only testing for a while and it grew to 16GB before I knew it! Of course, you have to evaluate the extra overhead of the "collect and upload" process running on each server (by default this process runs every 15 minutes). But at the end of the day you have a dedicated Data Warehouse that is populated with all the general performance metrics you would need to evaluate the health of your servers and databases. One major drawback: The CTP requires that the Managed Instances and Data-tier Applications be present on 2008 R2 Servers using the Enterprise edition but that will surely change in future CTPs. Otherwise, it wouldn't be health care for all, would it? cheers Brian
在所有SQL 2008 R2卫生保健?
SQL Server
版权©2009 IDG通信公司。Raybet2