Superior Spotlight Blog
Sneak Preview: The Best of SQL Server 2012 from the Microsoft Development Team
We’ve made it to December, which means 2012 is just around the corner. With the coming of the new year also comes a new release of SQL Server. The SQL Server 2012 release adds a number of innovative features to the SQL Server platform. After working with early versions of this new release for over a year now, we at SCS are extremely excited about the capabilities coming down the pike.
To get Microsoft’s take on the SQL Server 2012 release, SCS took time to touch base with two important figures in its creation.
 T.K. Anand is the Principal Group Program Manager responsible for Analysis Services and PowerPivot. He has been with Microsoft for 15 year, contributing to every major SQL Server release since SQL Server 7.0.
 Thierry D’Hers is the Principal Group Program Manager responsible for Reporting Services. He is one of Microsoft’s main BI evangelists and has been with Microsoft since 1999.
We asked T.K. and Thierry a series of questions to discover their views on the business impact of the upcoming SQL Server release.
____________________________________________________________________________________
1. What new features of SQL Server 2012 offer the most opportunities, will have the greatest impact, and/or provide the greatest return for organizations?
 Thierry: SQL Server 2012 is a very feature rich release for SQL Server. It provides many great new benefits for all personas.
 T.K.: Some of the features that I expect will have huge impact on our customers and partners:
- SQL Server AlwaysOn is an integrated high availability and disaster recovery solution that will deliver uptime and data protection for the most mission critical OLTP applications.
- The ColumnStore index (based on the Vertipaq™ technology introduced in PowerPivot) can improve data warehouse query performance by orders of magnitude.
- Power View is a brand new data exploration, visualization and reporting experience that will enable end users to gain insights from their data and have fun while doing it.
- The BI Semantic Model represents the next generation of Analysis Services and is the BI platform that all end user experiences (including Power View) will be based upon.
- Master Data Services and Data Quality Services will enable enterprises to better manage the quality and consistency of their business data.
There are a lot more features in SQL Server 2012 than what I can possibly talk about in this blog post. I encourage readers to visit http://www.microsoft.com/sqlserver to learn more.
2. We have heard it said that SQL Server 2012 democratizes business data (intelligence). Can you explain what that means and how SQL Server achieves that?
 Thierry: Thank you for asking this question which allows me to talk about one of our great innovations in this release: Project Crescent, officially named Power View. Power View is an ad hoc reporting and visual exploration capability that enables any end users to answer business questions and gain insights from its data with two to three clicks to results.
 T.K.: Since the introduction of Analysis Services and Reporting Services, SQL Server has been instrumental in democratizing BI by making it possible for Developers and IT Professionals to build and manage BI solutions with low TCO [Total Cost of Ownership]. SQL Server 2012 takes this to the next level with Power View by offering business users an immersive experience for exploring and visualizing their data to gain insights. Bringing Analysis Services and Reporting Services together with PowerPivot and Power View, SQL Server 2012 offers a compelling BI platform and experience for both IT and business users. I believe this will help increase the reach of BI to a much larger user population.
3. BI tools are often thought of as Enterprise Solutions (tools for big corporations). How has Microsoft designed BI for small and mid-size businesses?
 Thierry: Microsoft has focused this release on making access to insights available to an even larger set of business users no matter what level of sophistication and “technical savvy-ness” they have. This means that it reduces the need for IT to design and build datamarts, or Data models and develop reports on behalf of its users. IT can focus its resources on managing the corporate data sets, making them available, curated, secured, cleaned which is very often a large cost center that is very painful on small and Mid-size businesses. But we are taking our focus on small and mid-size business even further, by taking our Reporting Services assets and making them available as SQL Azure services. This means that small and mid-Size businesses do not need to invest in on premise software deployment to get access to the same powerful and sophisticated Reporting Services infrastructure large enterprises use. They can simply subscribe to get access to this service in SQL Azure.
4. What feedback are you hearing from SQL Server 2012 early adopters?
 T.K.: The feedback on SQL Server 2012 has been great. We released the last Community Technology Preview (CTP3) in July and the Release Candidate (RC0) a couple of weeks back. We’ve been working closely with a lot of early adopters (customers, partners, MVPs) who have been using SQL Server 2012 to build new applications or improve their existing applications. The overwhelming feedback is that SQL Server 2012 is a game changer with features like AlwaysOn and Power View.
 Thierry: The BI Semantic model is a big hit as it extends the ease of use and power of PowerPivot to IT scenarios on the server. IT now feels they can also reap the benefits of the PowerPivot technology (Vertipaq), but in a real professional environment and leveraging powerful servers. But the most surprising feedback we hear is about Power View. I am very excited about the enthusiasm I hear from our early adopter customers about the fun, slick and extremely intuitive user experience Power View provides. A good place to read more about these is from our blog: http://blogs.msdn.com/b/sqlrsteamblog/archive/2011/11/17/what-s-new-in-power-view.aspx.
5. How will organizations be better equipped to leverage the Cloud through SQL Server 2012?
 T.K.: Microsoft offers a symmetric data platform for on-premises and cloud with SQL Server 2012 and SQL Azure. This enables a lot of useful scenarios that will help customers move to the cloud. For example, you can use the SQL Server Data Tools and the Data-tier Application (DAC) Framework to develop apps once and deploy to SQL Server or SQL Azure. You can use SQL Server Management Studio to manage your SQL Servers as well as SQL Azure subscriptions. You can synchronize data between on-premises and cloud using SQL Azure DataSync. Business users can use PowerPivot and Power View to mash up and visualize data from SQL Server, SQL Azure and other sources.
 Thierry: In this wave we are making Reporting services 2008 R2 functionality available as a service in the cloud with SQL Azure. But we are building the infrastructure in SQL 2012 to make SQL 2012 functionality available to the cloud within a few months of SQL 2012 RTM.
 T.K.: Having these bridges between the cloud and on-premises is crucial for customers to take the leap and embrace the cloud.
6. Where do you see Microsoft SQL Server heading beyond the 2012 release?
 Thierry: Data is becoming the new currency that determines which businesses succeed and prevail or fail. The demand for easy to use data exploration and presentation tools has never been stronger and everything suggests that it will keep increasing at an exponential rate. How do we allow a few hundred millions information workers to be able to gain insights from the data they have in order to optimize their business decision making in the same way they use simple productivity tools like Outlook, Excel or PowerPoint to send an email, manage a list of items or build a presentation? How do we enable IT to become more efficient at discovering and providing the much needed data their users need in an agile way, whether that data resides inside the corporate firewall or out in the cloud? These increasingly interesting questions are defining the constraints and expectations for the next generation of Business Insights experiences….
 T.K.: As we put the wraps on SQL Server 2012, we’ll start planning for the next release wave. While it’s too early to comment on what will be in that release, a few things should be clear.
- Microsoft is making a huge bet on the cloud with Azure and Office 365 and that will strongly influence the direction of SQL Server. You can already see this with the updates to SQL Azure and upcoming release of SQL Azure Reporting.
- Customers are faced with ever increasing volumes of data and new types of data – real-time, unstructured, semi-structured, text, images, web logs, etc. The SQL Server data platform needs to evolve to meet these customer needs. The recent announcement of the SQL Server Hadoop Connector is an example of this.
- With the explosion of smartphones and tablets, more and more customers want their BI solutions delivered on mobile devices. At the PASS conference in October, we announced our Mobile BI roadmap. This is another area where you will see us making a lot of investment in.
We have a lot more up our sleeve, but you’ll have to wait to hear about them J.
____________________________________________________________________________________
T.K. and Thierry already have us looking forward to the next release of SQL Server. In the meantime, the variety of new tools and features available in SQL Server 2012 make this release extremely exciting -not only for us techies, but also for business users looking to harness their data for better decision making.
A big thank you to T.K. and Thierry for taking time out of their busy pre-release schedules to share their thoughts!
Posted in Business Intelligence & Reporting, Custom Business and IT Services, Microsoft Solutions, Uncategorized
|
Tagged analysis services, BI, business intelligence, ColumnStore, development, Microsoft, Power View, PowerPivot, PowerView, Reporting Services, SQL, sql 2012, SQL Azure, sql server, Vertipaq
|
The primary analysis effort for new software architecture always revolves around the computer hardware and software structure and new software technologies. But it’s surprising how much the software architecture is really influenced by and dependent on the people in the business organization rather than the latest technology.
Imagine that you’ve worked long hours on gathering an initial set of requirements for a new project. Then you used those requirements to research the latest technology that will run on the computer systems you have or envision you will purchase.
Then you create software architecture for the project based on the research and the hardware requirements. You even document the architecture using diagrams and fine prose.
It’s perfect! It fits the technical requirements just right. Now it is time to plan out the development of the project.
But wait a minute. You find out that the development staff doesn’t have the required skills to carry out the assignments. The new architecture made sense according to your own experience and the latest technology trends. However, the staff doesn’t have the same knowledge base as you and they are not familiar with the latest technology.
Also, you may have some contractors at the ready. But should they create software that the staff can’t maintain? Also, from an organization standpoint, do the users have the skills to use the new system? Is the development staff organized in teams already that match the type of software components you want to develop?
In the book Software Architecture in Practice by Len Bass, Paul Clements, and Rick Kazman, it says, “Software architecture is a result of technical, business, and social influences. Its existence in turn affects the technical, business and social environments that subsequently influence future architectures. We call this cycle of influences, from the environment to the architecture and back to the environment, the Architecture Business Cycle (ABC).”
So the software architecture is not totally driven by a written set of requirements. It’s much more influenced by the social environment (business users using the system, organization into groups, developers, managers) than we usually think when creating an architecture.
Sometimes the social environment may be at least as important as the requirements, if not more important. Just think about a few of these relationships between the software architecture and people.
The software development organization, and to an extent the company’s total organization structure must support the new architecture. The software development people are organized around tasks that are required to develop software that fits the architecture. Users may also be organized somewhat related to the architecture of the software.
The full-time employees of the organization need the skills to develop or maintain the software that’s developed according to the new architecture.
Even if you utilize contractors, the full-time employees that will support and maintain the system must have the required skills. This means that the employees may require training in new technologies before starting development or before taking over support and maintenance.
The organization of business people who will be using the system probably had a lot of input into the new system, and thus the new architecture. In turn, they will have to understand how best to use the new system, and may require training (there is a limit as to how intuitive or self-evident the system can be).
Once the business uses the new system the awareness and skill level of users will increase, and they will ask for more features. The requests for new features will lead to requirements for the next system.
So the next time you set out to create a new software architecture, new system, or just a new enhancement, take some time to consider the human side of software development up front to avoid surprises when it comes to implementing the new software.
SSRS is a great tool for quickly retrieving data and presenting the data to the user at a run-time decided format. One area where SSRS often falls short is when the underlying data needs to come from several different sources. Perhaps we want to retrieve data from the General Ledger which is in Oracle, and join that against a list of departments and employees which are stored in SQL Server for us to display in one table. When this happens, it is quite often not possible to join them into one dataset, and we are stuck with some difficult design problems for the report.
Here is a sample SSRS DPE (Data Processing Extension) project SCS has put together on Code Project as a starting point for any interested developers to work from. Depending on the specific needs of the project additional development will be required, but we have created a starting point for anybody that needs to use SSRS to report data coming from two or more different databases.
http://www.codeproject.com/KB/reporting-services/SSRSMultiDataSourceDPE.aspx
This month’s tip comes from Jade Hildahl, Business Intelligence Consultant with Superior:
In Microsoft SQL Server Reporting Services 2008, the Tablix data region can be unwieldy when you’re wanting to turn on the feature where “keep headers visible while scrolling” is being used. This causes table headers to remain in place while the user scrolls down through rows, or right through columns on the report.
What if there aren’t any group headers, where table grouping gives you an option to add a header or a footer row?
As a result even if you select the option to keep headers visible from the Tablix properties dialog, the “headers” don’t remain visible because they’re not defined as a group headers. To get around this, fixed rows in a table can be treated as a header or other non-scrolling area by
- Go to the advanced options for the column groupings in the Tablix(the quite-hard-to-locate drop-down in the upper –right corner of the Tablix groups area), and then then select the “Static” row grouping that is associated with the text boxes in the Tablix that you want to treat as “header” row(s).
- Next, select the “Static” row group for the header row and from its “Properties” pane, toggle “FixedData” to be “True” for the entire row.
(This may not apply to every situation where one wishes to do this, but at this point, one may also want to make sure the option to “Keep Column Headers Visible While Scrolling” is NOT enabled from the Tablix Properties window otherwise you will get a row/column conflict error when trying to build the report)
At this point, after deploying, you’ll have scrolling detail rows with fixed headers. However, the detail row data will still be visible in the background behind the header rows, because the default setting for new text boxes in a Tablix is to have no background color. To get around this,
- Selected all the text boxes making up header rows, and set their background to a non-transparent color, such as “White”.
After deploying, the rows to be treated as “header rows” are fixed and opaque as desired, without having defined a parent group or “header” row, or for that matter, any groupings of any kind in the Tablix beyond my standard “detail” row.
Quick steps:
1. Select a text box in the row you wish to have not scroll
2. Click on the “Advanced Mode” drop-down arrow to the right of your Column Groupings
3. Click on the now visible “Static” row under your “Row Groups”
4. Ensure the first text box in your desired, non-scrolling row is automatically highlighted at this point
5. In the properties pane for the Static Row Group, toggle the “FixedData” option to “True”
6. (Optional: in the Tablix Properties dialog, make sure that you have not also selected the “Column Headers” option to “Keep header visible while scrolling” or it will conflict with the new configuration to keep your Row Headers visible while scrolling)
7. Select all your header row text boxes, and in their shared properties dialog, ensure that their background color is anything aesthetically pleasing other than “transparent”
Hopefully these tips help you in your development. If you have further questions, or are in need of assistance, please contact us directly and we would be happy to help!
JavaScript is a very powerful tool to enhance the user experience. However, poorly optimized JavaScript can have a very negative effect due to increased page load time. This becomes particularly apparent as the number of elements on a page increases thanks to controls bound to increasingly large data sets.
For those that are new to jQuery, assuming we have two divs (div_drag and div_drop), we can add drag and drop functionality by registering listeners during our form load:
$(“#div_drag”).draggable();
$(“#div_drop”).droppable({
accept: “#draggable”
});
Now instead let’s assume we have two lists – active & inactive. We want to be able to drag items from left to right and back again. With a maximum height and overflow, we will have scrollbars on our list for when the length of the items extends beyond 400px.
This will work perfectly fine for a relatively small number of items in our list. However, in the above code, every div that is to be draggable or droppable is registered at the same time (the document read event). Once the number of draggable or droppable items in the list gets too high (upwards of 100) the performance of attaching the event listeners becomes very noticable in IE based browsers (several seconds to several minutes). To combat this slow, unwieldy page load, we decided to defer the event registration as long as possible.
In the below sample, we only want to register the items that are currently visible. As we scroll up and down on the containing lists, we will then register the draggable events to the newly visible items. jQuery will maintain which elements have already been registered more efficiently than we will be able to easily do so, so the responsibility of double registration is left to jQuery.
When the page loads, we will register our two droppable divs (the headers of each list) and initialize the currently visible draggable divs as draggable. Only when the scroll bar moves other divs into visibility will they be registered. We can now have a virtually unlimited number of draggable divs in our panel and feel no performance penalty on form load.
$(document).ready(function(){
$(“#bktInactivate”).droppable({
accept: “.DrgActive”,
hoverClass: “drop-state-hover”,
drop: function(event, ui) {
alert(‘deactivate!’)
});
$(“#bktActivate”).droppable({
accept: “.DrgInactive”,
hoverClass: “drop-state-hover”,
drop: function(event, ui) {
alert(‘activate!’);
}
});
SetDraggable(document.getElementById(‘ActiveItems’));
SetDraggable(document.getElementById(‘InactiveItems’));
}
function SetDraggable(draggableUL) {
var scrollTop = draggableUL.scrollTop;
// Activate li items currently visible
for (var index = 0; index < draggableUL.childNodes.length; index++) {
var child = draggableUL.childNodes[index];
if (child.offsetTop scrollTop + 400) // stop after we pass visible level
break;
$(“#” + child.id).draggable({
helper: “clone”
});
}
}
With the recent release of the Community Technology Preview (CTP) 3 of SQL Server 2012 (codenamed ‘Denali’) we wanted to point out and highlight some of the key items that are related to Business Intelligence and provide very compelling reasons for evaluating and considering the next release of the product.
So here we go with the top 10 BI reasons to upgrade to SQL Server 2012:
10. Integrations Services (SSIS) Enhancements – lots of usability enhancements have been made such as ability to undo and redo, a new SSIS Toolbox, grouping capabilities in the data flow, simplified data viewer configurations, new data flow source and destination assistants (wizards), and improved data flow designer experience with mapping and resolving errors. Other modifications were made so it is easier to compare and merge packages, and you have the ability to view object dependencies in SQL Server Management Studio.
9. Master Data Services (MDS) Enhancements – improvements in the user interface (UI), performance improvements with the UI, ability to incorporate data quality services into the workflow process, and a new Excel add-in client that will provide the ability to edit Master Data and publish it back to MDS and even create a model in Excel.
8. New Feature: Data Quality Services (DQS) – this is a new product offering that has been added that allows you to create a knowledge base repository of data related items that can then be used to incorporate and use for data cleansing. This will allow you to profile, improve the quality, and monitor the on-going health of your data. This new feature can be added into your Integration Services and Master Data Services processes.
7. New Feature: Database Columnstore Indexes – the VertiPaq engine first introduced with PowerPivot has now been brought to the database engine and is available to use to create indexes on columns in the relational store. This will provide a wonderful opportunity for users leveraging ROLAP technology to greatly improve the performance on the query processing. This index groups and stores the data for each column versus the row. This can alleviate having to use pre-aggregated data and summary tables.
6. New Feature: Reporting Services (SSRS) Shared SharePoint Service – the SSRS integration with SharePoint will now be setup as a Shared SharePoint service just like Excel Services and PerformancePoint Services. Everything will be managed completely through SharePoint and there will no longer be a separate SSRS Windows Service running.
5. New Feature: Reporting Services (SSRS) Data Alerts – new self-service data-driven alerting capabilities have been added to allow end-users the ability to setup and define alerts using existing Reporting Services reports. These alerts can be setup based on defined criteria and scheduled as needed to provide a mechanism to notify the user without them having to manually execute the report on their own. This new feature is only provided in the SharePoint Integrated mode of Reporting Services.
4. PowerPivot Enhancements – with version 2 of PowerPivot there have been some major additions which include features like a new diagram view of the model, hierarchy and KPI support, ability to sort a column based on another column, multiple relationships (like role playing dimensions kind of – can access through DAX), image support, add values to rows and columns (very cool – flexibility provided in the PivotTables), reporting properties (will be leveraged by Power View codenamed ‘Crescent’), ability to format measures, field list sorted alphabetically (instead of how they were added to the model), and most importantly…show details (drillthrough support – this will be fabulous when using with PerformancePoint).
3. DAX Enhancements – new functions have been added to help simplify and provide additional capabilities like DISTINCTCOUNT, Rank, Standard Deviation, TOPN, table functions, LOOKUPVALUE, parent-child relationship functions, SWITCH, and more.
2. New Feature: Analysis Services Tabular – the PowerPivot experience in Excel has also been added into the Business Intelligence Development Studio (BIDS) introducing a new Tabular project option. This will allow you to take the PowerPivot model and convert it to a Tabular project and deploy the solution at the server level for a corporate/enterprise level solution that will scale and handle large volumes of data. With the Tabular models you will have the same options as in PowerPivot along with additional capabilities like partitioning, incremental updates, and role based security.
1. New Feature: Power View (codenamed Project ‘Crescent’) – this is a brand new browser based Silverlight report authoring tool. This new tool will replace the Report Builder 1.0 application that leveraged Report Models and will be able to leverage the Tabular BI Semantic Models (BISM) that you will be able to create with PowerPivot for SharePoint and Analysis Services Tabular projects. This will be a highly interactive reporting experience that will allow you to access, explore, and visualize your data and have fun doing so in the process. This tool will enhance the existing Microsoft BI toolset and provide a very friendly self-service reporting solution for end-users to leverage. The new feature is only provided in the SharePoint Integrated mode of Reporting Services.
If you have any questions or would like to meet with SCS to discuss how Business Intelligence can help your business please give us a call or visit or website to learn more about how we can help at www.teamscs.com.
For additional information in regards to SQL Server 2012 check out the following list of resources:
Superior Consulting Services Senior Business Intelligence Consultant Dan English was informed today that he has again received the Microsoft SQL Server MVP award for 2011. This award is given to the best and brightest of the Microsoft community for their extensive knowledge and skills, as well as sharing that knowledge with the surrounding community. Dan was the Minnesota SQL Server user group (PASSMN) President/Chair in 2009 and 2010 and is currently on the Leadership board for the MN Microsoft BI User Group. His Microsoft MVP Profile can be found here: https://mvp.support.microsoft.com/profile/Dan.English , and information on the Microsoft MVP program can be found at http://mvp.support.microsoft.com/. Thanks Dan for your continued efforts, and congratulations on the Microsoft MVP award!
This posting is intended to provide a brief overview comparison of reporting tools which Microsoft has positioned as possible options for end-user ad-hoc reporting. By ad-hoc reporting, we mean the ability for business users who are experts in their subject area, and are not technical; to construct their own reporting ad-hoc based rather than request the report from IT. The tools we’ll examine specifically are Microsoft SQL Server Report Builder 3.0, and Microsoft Office Excel 2010 pivot tables.
Report Builder and Excel
Report Builder is a scaled down visual design interface for constructing Microsoft SQL Server Reporting Services reports. Being scaled down, it resembles many facets of the Microsoft Visual Studio interactive development environment, with a set of capabilities that is intended to allow a somewhat sophisticated user to create a basic table- or chart-based report from various sources of data.
On the other hand, Microsoft Excel is the tool Microsoft has specifically intended to be used by a wide user-base to create ad-hoc reports. Excel itself is a sophisticated tool; but it has gained an almost universal prevalence among the basic skills of business users. It has limits of its own, such as number of rows per sheet, and simplicity of data definition and formatting. However, some of these limitations are giving way to solutions involving added technology such as PivotTables, PowerPivot, and corresponding server-based software such as Excel Services within SharePoint
But Excel does not afford a number of the features that make Reporting Services a robust report writing and delivery solution, such as subscriptions, data-driven subscriptions, caching and snapshot execution, native security (outside of document passwords, and network access control), and access and development versatility. Herein, SharePoint provides a solution to many of these issues, and SharePoint integration with Excel is evolving rapidly.
Notes Concerning PowerPivot
PowerPivot is a topic that occasionally comes up in the context of discussing Excel as a reporting solution. PowerPivot is an end-user data modeling tool. Much like Analysis Services organizes and manages data around a dimensional model, PowerPivot uses a powerful data manipulation engine to let users obtain data from various sources, filter it, format it, relate it, and bring it into Excel in a table-based model.
PowerPivot is not an ad-hoc reporting tool, per se, but it can provide helpful data access capability in Excel as part of ad-hoc report development. It also is not nearly as robust as Analysis Services for modeling data on an enterprise scale.
SCS continues to be a leader in recommending and providing reporting solutions to our clients, including the complete array of ad-hoc reporting alternatives available using Microsoft tools.
Who should do backups? Anyone that has data they cannot afford to lose, whether that is a small business, large enterprise, or a single person with one laptop. If you have data you don’t want to lose, you should be doing backups.
What should be backed up? Simple answer, the data from above that you can’t afford to lose. Longer answer, this is something that should be discussed. Do you only want to back up the data, to save both time and storage? Or do you want to back up the entire computer to make recovery easier in the event of a failure?
Where should it be backed up? A good school of thought is that it isn’t really backed up unless there are at least two copies, and at least one of them is stored at a location some distance from your computer. It does not do much good if you only have one backup, it is stored right next to your computer, and a fire burns down the building. Both the original and backup would be gone. In case of natural disasters, it may make sense to keep backups in separate cities, or even states.
Why should it be backed up? Another simple answer, you have decided to back it up because you cannot afford to lose it, whether that be emotionally (wedding pictures, video of the kids, etc.) or monetarily (work files, etc.).
When should backups be done? Backups should be done when they cause the least amount of inconvenience, or when nobody is changing the data. For most backups, this means doing them at night. For others, special backup procedures and programs need to be in place to make sure data that is being used and changed all the time can be properly backed up. As for how often backups should be done, it comes down to one simple question. How much data are you willing to lose? If you can stand to lose no more than a week, then weekly backups may be for you. If you cringe at the thought of losing minutes of data, perhaps having real-time backups may be in order. It really is up to the individual.
How should backups be done? This question usually gets answered as you answer the rest of the questions. If you need real-time backups, this limits how they need to be done. If you only need to backup one small computer once a month, there are far more options available to you.
Hopefully these questions have helped shed a little light into backups, and hopefully they make you question your current backup strategies. Are they where they should be? Do they work? What really would happen if I had an outage right now? If you need help answering these questions, SCS can help!
Dan English was recently voted by RPC Magazine as one of the top ten Microsoft MVP’s in the world! Dan has also attained the “Senior Consultant” role with Superior Consulting Services. Congratulations on both fronts Dan!
http://rcpmag.com/articles/2011/05/01/top-10-microsoft-partner-mvps.aspx
|
|
