January 27, 2008
@ 10:48 AM

Despite public confidence that SQL Server 2008 would ship by the end of June, Microsoft today indicated it probably is more likely to arrive toward the end of the year.

Microsoft will release SQL Server 2008 to manufacturing in the third quarter, Francois Ajenstat, Microsoft’s director of SQL Server project management, said today in a blog posting.


"Our goal is to deliver the highest quality product possible and we simply want to use the time to meet the high bar that you, our customers, expect," he wrote. "Over the coming months, customers and partners can look forward to significant product milestones for SQL Server."

A key milestone, he wrote, will be a CTP with all of the features intended for SQL Server, to be released in the second quarter. The final release to manufacturing (RTM) candidate will be released in the third quarter.

Observers were not surprised by the latest delay. "The last couple of CTPs were late and the idea that we're now only five months away from release seemed far-fetched," said Andrew Brust, chief of new technology at the consultiancy of TwentySix New York in an e-mail.

Brust, who also runs the New York .NET User Group, adds that he had been telling people that SQL Server would be pushed back at least once. "There's no point in pushing this out the door before it’s ready, especially when the financial results announced yesterday are so good," he added. "September 30 is fine. And for that matter, so would be end-of-year. Only real egg on their face is that the 'launch' of the product is next month."

Ajenstat wrote that the delay will have no impact on the Feb. 27 launch event.


 
Categories: SQL Server

November 12, 2007
@ 02:29 PM

The next preview of SQL Server 2008 with new support for spatial data types and a new Resource Governor feature is slated to hit in a week or two, according to Microsoft.

This Community Technology Preview (CTP) follows one in August and the first last June.

Microsoft execs, who had previously pledged new CTPs every sixty days, admitted that number three did not hit that deadline, but said that does not bode ill for the final release. The database is "on track" for release in the second quarter of calendar year 2008, they reiterated. The SQL news emanates from a TechEd IT Forum in Barcelona

Timing, always a sore point with Microsoft products, is particularly touchy for the database given the five-year gap between SQL Server 2000 and SQL Server 2005 -- a delay the company has sworn will not happen again.

Francois Ajenstat, director of product management for SQL Server, said the latest CTP offers important new features for developers and database administrators (DBAs). The Resource Governor, for example, promises both constituencies more granular control over what processes get priority in situations where there is contention.

"They can assign resource limits on a particular job or user. If the system's running payroll as well as reporting at the end of the month, a lot of payroll users will be doing processing and suddenly a reporting person writes some crazy report that starts soaking up memory and CPUs. This can ensure that the critical function gets priority and can be set by process ID or user," Ajenstat told Redmond Developer News.

As databases get bigger and are shared by more users and processes, this is a critical function.

"This could be very important but the jury's still out on how robust it is. We have to look at it. If it lives up to its promotional rhetoric, it will be very valuable," said Andrew Brust, chief, new technology for twentysix New York, a solution provider with SQL server and application development expertise. "In the database world there's a lot of gallows humor. The hope is this will stop BSTK, which stands for 'queries that bring the server to its knees.'"

In addition, this third CTP adds transparent data encryption that, in theory, means that database applications won't require recoding in order to take advantage of encryption.

The current SQL Server 2005 supports encryption, but requires tweaks on the application side to take advantage of it. "That's fine if you control all the applications, but in many cases you don't; transparent encryption takes care of that," Ajenstat said.

Also in this release is the promised FileStream feature that would allow storage of unstructured data in the database without converting it first into binary large objects (BLOBs).

That capability is a holdover from the long-promised-but-undelivered WinFS file system.

Brust is jazzed about that feature.

"Since the beginning, database people have tried to use databases to manage documents or digital photos but there's always been a tradeoff," Brust explained.

"The question is ";Do I put it in the database or in the file system and then put a reference to that file in the database?' And allegedly for reasons of performance, people have preferred to keep the file in the file system and the tag in the database. It's a little easier for programming and seems to make sense when doing backups, [because] you don't have to worry about database corruption. But here you can do both. It's in the file system, but the database treats it as if it were part of the database. That means if you do things and start a transaction against the database and then have to roll it back -- if an operation deletes a photo, you can roll back the transaction and the file will actually come back. You can access it as a file or as a store."

Database Support for spatial data should enable developers to more easily build location-based applications. Integration with Microsoft's Virtual Earth will be delivered via a separate SDK with the next CTP, Ajenstat said. At TechEd in Barcelona, the company will trot out a list of partners for its location-application push includingESRI, Spatial point, Space Software, and SWSoft.

Ajenstat downplayed any negative impact on developers from Microsoft's decision to hold back the ADO.NET Entity Framework, which was to ship with Visual Studio 2008, with the later SQL Server 2008 instead. (Visual Studio 2008 is due this month.)

To sync up the releases, Microsoft will ship an update to Visual Studio when SQL Server 2008 ships. The entity framework is now in beta 2 and Ajenstat expects another beta around the time Visual Studio 2008 itself ships.

The Entity Framework promises to let developers work at a higher conceptual level, so they will not necessarily have to know too much about the inner workings of the data setup.

"If you're a developer today, you need to know how the data is structured, how the tables were built. And developers are not necessarily database people," Ajenstat said.

The Entity Framework builds on Microsoft's LINQ, which lets developers work in the programming languages they know rather than with strings of database code. "The entity framework raises the abstraction layer [further], so developers can work with common sense objects," Ajenstat said.

It will also let developers use plug-ins to connect to Oracle, MySQL Sybase and other data sources.

Inclusion of the new graphical technology, acquired by Microsoft from Dundas, is also a big deal to many developers. "That's huge for us. We're a big consumer of SQL Server reporting services and we do a lot of views and charts. While the current reporting services are good, there wasn't a lot of depth to the report options. It wasn't as deep as say Crystal Reports," said Peter Hammond, CEO of Cybersavvy, a Redmond, Wash. developer.

Developers said this release is relatively incremental compared to SQL Server 2005, which represented a huge leap from the previous version.

"We're still focused on SQL Server 2005 because we need it to develop on and sell now. We see SQL Server 2008 as more evolutionary vs. revolutionary. They're putting the Dundas stuff in which is good and will help us create dashboards," said Lee Blackstone, CEO of Blackstone & Cullen, an Atlanta-based database expert.

None of these new features "are hugely revolutionary," Brust agreed. "This is a much smaller release than SQL Server 2005 and that's probably good. A lot of shops are still running the previous release and it'll be helpful that this is not as big a leap," Brust said.


 
Categories: SQL Server

ORLANDO -- Microsoft on Monday released the first community technology preview of SQL Server 2008, the official name for what was initially codenamed "Katmai." The announcement was made here at the Microsoft TechEd Conference in Orlando.

Katmai is set to ship in 2008 and the company is making it a central plank of its push into the business intelligence space. But Redmond is also building a number of developer-specific capabilities into the next-gen server release: The ADO.NET Entity Framework (EF) and the Language Integrated Query (LINQ).

Developers can use the Entity Framework to program against data defined in a conceptual way, instead of having to work with information organized in tables and columns. "With the Entity Framework, we’re essentially programming at the conceptual level rather than at a logical level or a physical level," Francois Ajenstat, director of product management, SQL Server previously told RDN.

LINQ enables developers to tap various sources from within VB.NET and C#. The LINQ to Entities specification will ship as part of the Entity Framework, and, like the EF, will be supported by Visual Studio tools.

Other improvements slated for SQL Server 2008 include added support for various data types, including spatial and unstructured data.

In related SQL Server news, Microsoft on Monday also announced it had acquired technology from Dundas Data Visualization Inc., for the creation of charting in SQL Server Reporting Services.


 
Categories: SQL Server

Microsoft declared the opening day of its first BI conference, May 9, "a new day" for business intelligence, with the same old goal every BI vendor has had for years: To make BI ubiquitous in the enterprise, used by all relevant workers, not just by executives and IT (who jigger reports for executives).

The difference with Microsoft and other BI providers is its ability to not only circulate BI technology through a massive technology stack—SQL Server, Office, other servers, tools—but to push that technology out through a ubiquitous application: Excel.

Microsoft has estimated that there are 500 million licenses of Office floating around in companies throughout the world; the company plans to tap at least a percentage of those users for its BI Platform, previewed today at Microsoft's BI conference in Seattle.

"We're one company; we can deliver the underlying platform, tools and applications that can help your company leverage BI," said Jeff Raikes, president of the Microsoft Business Division, during his keynote address at the BI conference.

"And we can build for scale ... You need to gain insight and drive decisions. That's the focus of the tools in our applications layer. We are very focused on integrating into our tools—the Microsoft Office system—and using that on top of whatever you get from SQL Server.

In its sum total, the Microsoft BI platform includes three major components: SQL Server, SharePoint Server 2007 and Microsoft Office (including Excel 2007). The final piece is PerformancePoint Server 2007, which is really the applications layer of the BI platform. To this end, Raikes outlined the next version of SQL Server, code named Katmai, that will be the basis of Microsoft's overall data platform vision.

The updated server, due in 2008, will include capabilities for large scale data warehousing and richer information delivery through Microsoft Office. "Katmai will be optimized for highly predictable performance and will include policy-based management," said Raikes. "Beyond rational database capabilities [users] will be able to store any type of data, including unstructured. It's a new data model that will enable [developers] to build richer applications faster."

Raikes also announced the acquisition of SoftArtisans, a company that develops Microsoft Office format reporting and file transfer software for managed report authoring in Office. The company's OfficeWriter software generates functional Excel spreadsheets and Word documents over the Web—without the need for Microsoft Office on the server—by populating Office documents with dynamic data from any source, according to the company's Web site.

The reports take advantage of Office 97-2003 features, from advanced charts and formulas to macros/VBA and pivot tables. Microsoft actually acquired SoftArtisans a year ago, but chose to announce the deal at its BI conference. The company's technology will show up first in Katmai, and later in PerformancePoint Server. At bottom, however, SoftArtisans represents a big step forward in the interoperability of reporting with Office by allowing users to access, modify and author reports in Office and in Word.

"We have a very strong interoperability in terms of taking reporting services and exporting that to Word, or to Excel, but [SoftArtisans] gives you the capability to start in Word or start in Excel to access information, and author reports from there," said Chris Caren, general manager of Office Business Applications at Microsoft.

With the upgrades in Katmai, Microsoft is clearly targeting the enterprise market (its line of business applications, Dynamics, will be a line to midmarket customers) and enterprise-level BI projects. The heart of this initiative, however, is the Office PerformancePoint Server 2007, now in its second community technology preview.

Based on functionality acquired from BI applications vendor ProClarity ten months ago, PerformancePoint 2007 is Microsoft's answer to Corporate Performance Management, which is functionality that allows CFO's to answer crucial questions about their business: How are we doing? Why? And what should we be doing?

Due late in the summer of 2007, PerformancePoint Server will include dashboards, score carding, analytics, performance, planning and consolidation applications.

But Microsoft is not alone in using CPM to lure chief financial officers in major corporations. SAP announced May 8 its intention to acquire OutlookSoft, a privately held company that develops planning, budgeting, forecasting and consolidation software.

SAP plans to bridge OutlookSoft's performance management software with its business intelligence platform and GRC (Governance, Risk and Compliance) suite of applications. On April 19, Oracle closed its $3.3 billion acquisition of Hyperion, an industry leader in CPM software.

Where Microsoft differs from Oracle and SAP is Office, according to Caren.

"Our approach is really different," said Caren. "While we are targeting the CFO and compliance, we've bet incredibly hard on Excel, making a place where you can work with information securely and share information securely. Our ease of use and our price point leads to much broader solutions. SAP and Oracle, typically don't go beyond the CFO; our goal is to [reach] everyone who might own a budget."

To this end, Microsoft has been building out an internal sales team for the past 18 months. "We're doubling down our efforts to make [the team] more global in focus, with people that focus on BI, SQL Server and Office," said Caren. "They're chartered with going into large customers to win big projects. And to recruit, train and work with partners."

The Microsoft BI sales team will have a dual focus on reaching what they refer to as decision makers—people in finance and sales and operations—doing financial management projects that include planning, budgeting and forecasting, areas where companies typically need to extract business intelligence. They'll also target Microsoft's typical IT buyers.

Also during his keynote, Raikes previewed three key partnerships with global system integrators: Accenture, Cap Gemini and Tata Consultancy Services. The significance of these partnerships, according to Caren, is that the each company is "betting hard" on Microsoft BI much earlier than they would a new software offering from another vendor.

"This is a new day for BI, in our view ... not only for Microsoft but for the industry as a whole," said Raikes, in Redmond, Wash. He pointed to the good news with BI, citing a Wall Street Journal report that said that 13 percent of businesses plan to make their first BI acquisition this year. In 2006 companies spent a total of $23 billion on BI technology.

"The bad news is we feel people are paying far too much for BI and not getting enough. The promise of BI is unfulfilled," Caren said.

At least one analyst, Joshua Greenbaum of Enterprise Applications Consulting, believes Microsoft's focus on tools—and on massive SI's to build out functionality—is not quite the right approach.

"Microsoft's very able BI team is producing great tools but leaving the industry-specific and role-specific functionality to their partners. And herein lies the weakness in the strategy: the partners are a mixed bag. Some are really steeped in the business and end-user requirements of specific industries, but too many are technologists more in the mold of Microsoft than not," writes Greenbaum in his blog.

"And too many of those who really grok the industry-specific issues—among them the global SIs—are not developing packaged solutions but concentrating on custom, one-off solutions that are by definition more costly than packaged alternatives."

Via Eweek


 
Categories: SQL Server

As a part of the release of SQL Server 2005 Service Pack 1, Microsoft announced the availability of a new package of SQL Server Express called Advanced Services.  Advanced Services includes SQL Server Reporting Services and Full Text Search, along with SQL Server Management Studio Express and SQL Server Express Toolkit (used to build reports).  SQL Server Express also continues to be available without the complementary features to keep a small download package for those who require it.  For a more in-depth comparison of the versions, check out the feature comparison page to decide which version of SQL Server Express is right for you.


With the introduction of Advanced Services, professional users can scale up to create more sophisticated applications and take advantage of SQL Server’s impressive Reporting Services and Full Text Search features.  To make management easier, SQL Server Express with Advanced Services comes bundled with the new SQL Server Management Studio Express, the graphical management tool for SQL Server.  SQL Server Express Tool kit includes Connectivity Components, Business Intelligence Development Studio, Management Studio Express, and a Software Development Kit for management and report creation.


In conjunction with the release of these new SQL Server Express products, you’ll also find a lot more material for support, migration, fun projects, and learning materials targeted at a variety of audiences with varying skill levels from how-to videos for the database novice to out-of-the box starter kits for the hobbyist, to more technical whitepapers on topics like migrating to SQL Server Express from other databases and file systems.  


Download page for SQL Express


SQL Server 2005 Service Pack 1


feature comparison page 
 


 
Categories: SQL Server

Kim Tripp is going to be conducting an 11 part webcast series for Technet.  The first session was on Friday March 10th and was overbooked. You can download the on demand session at the link below:


 


TechNet Webcast: SQL Server 2005 for the IT Professional (Part 1 of 11): A Fast-Paced Feature Overview and Series Introduction (Level 200)


 


You can also find supporting resources on her blog at http://www.sqlhera.com


 


Below is the schedule for the remaining sessions:


 Live Webcasts


TechNet Webcast: SQL Server 2005 for the IT Professional (Part 2 of 11): Security (Level 200)
Friday, March 17, 2006
9:30 A.M.–11:00 A.M. Pacific Time


TechNet Webcast: SQL Server for the IT Professional (Part 3 of 11): Understanding Installation Options and Initial Configuration (Level 200)
Friday, March 24, 2006
9:30 A.M.–11:00 A.M. Pacific Time


TechNet Webcast: SQL Server 2005 for the IT Professional (Part 4 of 11): Upgrade Considerations and Migration Paths (Level 200)
Friday, March 31, 2006
9:30 A.M.–11:00 A.M. Pacific Time


TechNet Webcast: SQL Server 2005 for the IT Professional (Part 5 of 11): Effective Use of the New Management Tools (Level 200)
Friday, April 7, 2006
9:30 A.M.–11:00 A.M. Pacific Time


TechNet Webcast: SQL Server 2005 for the IT Professional (Part 6 of 11): New Application Design Patterns for Scalability and Availability and the Operational Implications of Service Broker (Level 200)
Friday, April 14, 2006
9:30 A.M.–11:00 A.M. Pacific Time


TechNet Webcast: SQL Server 2005 for the IT Professional (Part 7 of 11): Technologies and Features to Improve Availability (Level 200)
Friday, April 21, 2006
9:30 A.M.–11:00 A.M. Pacific Time


TechNet Webcast: SQL Server 2005 for the IT Professional (Part 8 of 11): Implementing Database Mirroring in SQL Server 2005 (Part 1 of 2) (Level 200)
Friday, April 28, 2006
9:30 A.M.–11:00 A.M. Pacific Time


TechNet Webcast: SQL Server 2005 for the IT Professional (Part 9 of 11): Implementing Database Mirroring (Part 2 of 2) (Level 200)
Friday, May 5, 2006
9:30 A.M.–11:00 A.M. Pacific Time


TechNet Webcast: SQL Server 2005 for the IT Professional (Part 10 of 11): Recovering from Human Error (Level 200)
Friday, May 12, 2006
9:30 A.M.–11:00 A.M. Pacific Time


TechNet Webcast: SQL Server 2005 for the IT Professional (Part 11 of 11): Best Practices in Building Robust, Recoverable, and Reliable Systems (Level 200)
Friday, May 19, 2006
9:30 A.M.–11:00 A.M. Pacific Time


 


 
Categories: SQL Server

Scalable shared databases are supported by Microsoft SQL Server 2005 Enterprise Edition. This article is a preview of the "Scalable shared database" topic that will be published in a future update of SQL Server Books Online.


Scalable shared databases let you attach a read-only reporting database to multiple server instances over a storage area network (SAN). A reporting database is a read-only database that is built from one or more production databases that are used exclusively for reporting purposes. To be made into a scalable shared database, a reporting database must reside on one or more dedicated read-only volumes. The primary purpose of these read-only volumes is to host the reporting database or a coordinated set of reporting databases. These volumes are known as reporting volumes.


Read KB Article


 
Categories: SQL Server

Download an updated version of Books Online for Microsoft SQL Server 2005, the primary documentation for SQL Server 2005. The December 2005 update to Books Online contains new material and fixes to documentation problems reported by customers after SQL Server 2005 was released. Refer to "New and Updated Books Online Topics" for a list of topics that are new or updated in this version. Topics with significant updates have a Change History table at the bottom of the topic that summarizes the changes.


Books Online includes the following types of information:

























Setup and upgrade instructions.


Information about new features and backward compatibility.


Conceptual descriptions of the technologies and features in SQL Server 2005.


Procedural topics describing how to use the various features in SQL Server 2005.


Tutorials that guide you through common tasks.


Reference documentation for the graphical tools, command prompt utilities, programming languages, and application programming interfaces (APIs) that are supported by SQL Server 2005.


Descriptions of the sample databases and applications included with SQL Server 2005.


You can get the update at:


 http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx


 
Categories: SQL Server

December 1, 2005
@ 03:56 PM

For those missing the Sql Server manager utility in sql server 2005:  SQL 2005 Service Manager is a third party applet that replaces the missing sql service manager in Sql Server 2005.  You can download from the link below.


SQL 2005 Service Manager


 


 
Categories: SQL Server

With the release of SQL Server 2005, Microsoft hopes to move in on the large-enterprise database management systems market formerly dominated by Oracle, IBM's DB2 and Sybase by offering features and scalability more like theirs.


Microsoft's chief competitive strength in DBMS has been ease of use, which meant SQL Server database administrators needed less training, making them cheaper to hire and train. But as SQL Server gets more powerful, it gets more complex. Will SQL Server 2005 take a more sophisticated -- and more expensive -- kind of DBA?


It's possible, but probably not at the outset. For one thing, DBAs who are making the switch to SQL Server 2005 are making the most of training that comes for free. "I will not need to go to training," said Tcharly Florestal, DBA at Mount Sinai Medical Center in Miami Beach, Fla. "The documentation should be enough."


In addition to the documentation, Microsoft has been saturating the SQL Server community with resources that should at least get users up and running. They include free classes at events like September's Professional Association for SQL Server community gathering, workshop training as part of Microsoft's SQL Server launch tour, and even giving out vouchers to cover the cost of SQL Server certification exams.


Time is money


Although it is hard to make a direct comparison because there is so much variation in DBA jobs, analysts estimate that Oracle Corp., Sybase Inc. and IBM DBAs make 5% to 10% more, on average, than their SQL Server counterparts.


Oracle's certifications are worth more than Microsoft's, too, according to a Culpepper and Associates Inc., survey on pay trends from September. DBAs with Oracle certification were paid an average 8.4% more than uncertified DBAs, according to the study, while a Microsoft certification was worth only 4.6% more.


"The harder a database is to run, the longer the training required, and the more costly the training and certification," said Katherine Jones, an analyst in human capital management research with the Aberdeen Group, in Cambridge, Mass.


"Oracle is a very sophisticated database," Jones said. "When SQL Server first came out the door, it was the accessible database. It has changed over time, but it is still likely to be easier to use than the super heavy databases. In the grand scheme of things, it's still the easiest."


"It may be that people can take an online class or look at the documentation and say, 'I know what to do with it,' at least at first," Jones added. "But the general progression of software is toward greater sophistication. Over time, it could get sophisticated enough, to the point where more training is required. Then it could mean a SQL Server DBA could be as expensive as an Oracle DBA."


What are you going to do with it?


The kind of DBA you need isn't really a matter of which DBMS program you're using, but what you're using it for, according to Jim Shepherd, senior vice president at AMR Research Inc., in Boston, Mass. "Microsoft certainly has the perception of ease of use. Oracle has the reputation for being able to handle big, complex problems."


What's changed with the advent of SQL Server 2005 is that now a Microsoft DBMS can handle bigger and more complex problems, Shepherd said. SAP recently certified a benchmark involving 93,000 concurrent users on SQL Server 2005. That's big.


"If you have SQL Server 2005 in a 50-person company," you may not even need a DBA, Shepherd said. "If you have it in a 50,000-person company and you're using it to run SAP, you're damn sure going to need one."


"The reality," Shepherd said, "is it has very little to do with the product and more with the size and complexity of your database. It's not about the database product. It's all about the size of the installation and the complexity of your problem."


 


 
Categories: SQL Server

October 29, 2005
@ 10:42 PM

Unifying environments is a greater challenge than unifying languages, yet Microsoft is making headway. Consider the three domains of systems, data, and business rules. Each is being brought into the .NET environment in a way that will enable powerful synergy.


Specialized programming languages and their supporting environments have always been tightly coupled: SQL and the database ; business rules and the rules engine. It's tempting to wish for an uberlanguage or one syntax to rule them all, but what really matters is a common environment. At its 2005 Professional Developers Conference, Microsoft showed that it's finally putting all of its eggs into the .NET  basket.

We create specialized languages for a very good reason: to map the domains in which they operate to the mental models of programmers working in those domains.


Because every real software system involves many such domains -- for example, system administration, data management, business logic -- developers have to wear different hats and speak different syntaxes. But there's a larger issue. Our specialized languages live in different environments that don't cooperate.


To solve this problem, we typically create "wormholes" to connect one language environment to another. Embedding SQL statements in other languages is the classic case, but there are many others. Perl scripts, for example, embed shell scripts, and vice versa.


And JavaScript code embeds XSLT transforms, which may in turn use extensions to reach out to the operating system. In all such cases, the embedded code is a proxy to another environment that offers something unavailable in the host environment. But it is also a second-class citizen in that host environment.


Unifying environments is a greater challenge than unifying languages, yet Microsoft is making headway. Consider the three domains mentioned above: systems, data, and business rules. Each is being brought into the .NET environment in a way that will enable powerful synergy.


In the realm of system administration, Monad is a new shell that passes objects, rather than ASCII text, through a pipeline. Two major new initiatives in the realms of data and business rules were announced at the PDC.


LINQ (language-integrated query), the brainchild of Turbo Pascal and C# inventor Anders Hejlsberg, aims to make data management a first-class citizen of the .NET environment. The Windows Workflow Foundation aims to do likewise for workflow, but that's a longer story.


What matters here isn't the ability to operate in these domains using the same programming language; it's not having to jump through wormholes. Using LINQ, for example, a program can query the operating system for the names of running processes and can then join those names to historical data fetched from a database.


A traditional program would get the process list via shell commands and parse the returned text. Monad, which receives self-describing objects from Windows system services, can work more intelligently than that, and LINQ ups the ante even more.


It receives the same set of objects from the OS and similar ones from the database. As it operates on the merged collection, it can natively blend SQL-like data management with other activities, including system administration and workflow.


LINQ is an extraordinary innovation that turns traditional query inside out. But the bigger story from PDC 2005 is that the .NET vision of unifying many balkanized disciplines within the Microsoft ecosystem is finally becoming a reality.


Via InfoWorld


 


 
Categories: SQL Server

August 25, 2005
@ 08:59 AM

by Mike Otey


 The number of new features in SQL Server 2005 is almost overwhelming. Of all the new features, the one that has drawn the most attention from the media and DBAs alike is the integration of the CLR with the SQL Server database engine, and I can understand why. CLR integration brings with it a host of new capabilities as well as a huge potential for misuse. However, CLR integration is off by default, so you don't need to worry about it unless you decide to use it.

     While the inclusion of the CLR is an important step for Microsoft and SQL Server, it's not the most important change in the 2005 release. Instead, Business Intelligence (BI) is the big story in SQL Server 2005. At the PASS conference in 2004, Bill Baker introduced the themes of Integrate, Analyze, and Report to describe SQL Server 2005's BI functionality. Virtually every aspect of these BI areas has been either completely revamped, as with Integration Services, or significantly enhanced, as with Analysis Services and Reporting Services.

     Arguably, the biggest changes are up front, in SQL Server Integration Services (SSIS). Completely redesigned from the ground up, the new SSIS is completely different from Data Transformation Services (DTS), which it replaces. DTS was a useful tool, but it had problems with scalability and transportability. SSIS isn't just a data-transfer tool -- it's a complete workflow engine. Its performance is significantly improved, and new tasks enable looping, package execution, and enhanced flow control. The new Package Configurations feature lets you easily pass in runtime variables from the registry, XML documents, parent packages, or environment variables to make your SSIS packages more flexible and easily transportable.


The core Analysis Services component has also received many important improvements and new features. In Analysis Services 2005, OLAP cubes use the new Unified Dimensional Model (UDM), which combines the strength of OLAP and relational storage, enabling you to create a custom balance between the performance and data storage your Analysis Services cubes use. Other additions include proactive caching for cube deployment, MDX enhancements, and a new XML for Analysis (XML/A) query language. Microsoft also added several new data-mining models that provide more options for data trending and prediction.

     Changes on the reporting end of BI are every bit as significant as those in integration and analysis. The biggest change in reporting is the inclusion of Reporting Services, which provides an enterprise-oriented infrastructure that you can use to design and deploy reports across the organization. In addition, the new Report Builder feature brings the ability to design reports that are completely integrated with Reporting Services to the end user.

     At 5 years in the making, it's no surprise that SQL Server 2005 is the most feature-rich release since SQL Server 7.0 -- maybe the most feature-packed release ever. Though it contains many important enhancements, the BI portion of the 2005 release has the lion's share of the changes and new features. Many businesses were slow to adopt the BI features of the earlier SQL Server releases, but that won't be the case this time. SQL Server 2005 has broadened the definition of BI to incorporate information integration and presentation capabilities that go beyond analytical processing. The nature of the BI changes in SQL Server 2005 enable a wide cross-section of organizations to quickly put them to use. Despite the slew of new features in other areas of the product, SQL Server 2005 could easily be known as "the BI release."


 


 
Categories: SQL Server

July 13, 2005
@ 07:53 PM

Back in 1999, or possibly early 2000, I was told a rumor regarding the upcoming version of SQL Server. The rumor was that there was some experimenting going on at Microsoft, regarding the possibilities of using VBScript to write stored procedures in SQL Server. Supposedly there was a chance that this feature would be available in Shiloh (the codename for SQL Server 2000). A couple of months later the beta of SQL Server 2000 came, and then the final product, and as we all know there were no possibility to use VBScript to write stored procedures. Even though the person who told me this was definitely in a position to know about these things, I do not know exactly what truth there was to this rumor. And if it was correct I still have no idea how far this feature came.

Since then we have been waiting for a long time for a new version of SQL Server. And in November it will finally be available, the final version of SQL Server 2005 (also known as Yukon). The first official beta of Yukon was available two years ago, and since then there has been another beta and several Community Technical Preview (CTP) versions. For each version more and more people have previewed the product, and the hype and interest keeps on building. And in the middle of all this interest there is one feature --called CLR Integration or SQLCLR for short-- that is more discussed than any other. In SQL Server 2005 we will no longer be restricted to writing procedures in T-SQL; we can now use any .Net language to create database programmability objects! This is nothing short of a revolution in the SQL Server world, and many say that the complexity of this feature is the main reason why Yukon has taken so long to complete.

Heaven and hell
For an application developer who writes code using C# (or any other .Net language) this might sound like heaven. But for a DBA who have never even seen a C# program it is more likely to feel like hell. Does every SQL Server DBA need to take a crash course in C# now? Is T-SQL dead and buried with SQL Server 2005? Does my company need to buy Visual Studio licenses for all DBAs? These are common questions. Fortunately the answer to them is NO! T-SQL is not dead; it is more alive than ever with lots of new features being added to the language in SQL Server 2005. And every DBA will not need to learn C#, they will still be able to handle all their responsibilities in T-SQL and the new management tools included in SQL Server 2005. In fact, to use .Net code in SQL Server a sysadmin will first need to enable this server-wide feature. Many companies will not need to activate it at all; they can upgrade their databases to SQL Server 2005 and take advantage of all the other benefits it brings.

However, Microsoft did not add CLR Integration to SQL Server just because they had some extra time on their hands and thought it might be cool. The reality is that there are scenarios where a managed .Net procedure will perform better than one written in T-SQL. And it is definitely easier to write better code with a modern programming language such as C# than what we write with T-SQL (even though T-SQL is getting some nice new features in this area in SQL Server 2005). Many application developers who are also database developers will be interested in taking advantage of this. Visual Studio 2005 will have built-in integration with SQL Server 2005 for creating SQLCLR programmability objects. The developer can do all his work in his preferred development environment, so there is another reason for him to implement functionality with SQLCLR instead of T-SQL. But as you had probably guessed it is not as simple as just choosing between SQLCLR and T-SQL based on your preferences and skills. While I did say above that there are times when SQLCLR will perform better, there are definitely lots of scenarios where T-SQL is better. The integration of CLR brings nothing new to how data in a relational database is best managed. Declarative set-based DML always (or close to it) outperforms procedural processing here. One of the biggest concerns DBAs have regarding CLR Integration is that it will open up the doors to SQL Server for a hoard of programmers who know nothing about data management. I do not think that will happen though, why should everyone start programming database functionality just because they recognize the syntax better? But still, there is a quite possible risk that we will see a lot more procedural code, processing data row-by-row. We will also start seeing more or less exotic uses of SQL Server, such as procedures calling out to web services or working with the file system. The richness of the .Net Framework brings a lot of useful functionality, but it also means it will be much easier to do wrong --or at least questionable-- things in database code.

My personal opinion is that CLR Integration is an interesting new tool that can be helpful in some situations, but should definitely be used with care. I do not see it as the most important new feature in SQL Server 2005 (far from it), but it probably is the one that needs the most coverage to make sure that anyone who will be using it knows as much as possible about it. Developers will need to know what effects their .Net implementations will have in SQL Server, and DBAs will probably want to be able to review code that is being executed in their databases. This article is therefore the start of a series that I will publish on this matter. In the upcoming parts I will describe how CLR Integration works, what you can do with it (and of course how to do those things) and when you should or should not use it. To end this part, and start looking at CLR Integration, I will show an example of a useful user-defined scalar function implemented in C# and how to use it in SQL Server 2005.

Using CLR Integration to validate email addresses
One thing that many have asked for in SQL Server is the possibility to use regular expressions for validation purposes. Using a specially crafted regular expression it is possible to verify that a string is written according to some formatting rules that have been defined, for instance that an email address seems correct. Although SQL Server 2005 does not have this feature, the .Net Framework does. We can therefore implement a user-defined function in C# that takes a string and validates it against a regular expression. This is an example of a good use of the CLR Integration in SQL Server 2005. As most probably already know, implementing a function in C# does not mean that we write C# code inside a T-SQL DDL statement such as CREATE FUNCTION. Instead we need to create a .Net assembly containing a class with a method that will act as the user-defined function. We could do this using only a text editor such as Notepad, the C# compiler and T-SQL statements to define the function inside SQL Server. I will save that for a later article though. Here I will instead simply outline the steps necessary to build and deploy the function using Visual Studio 2005 and the integration with SQL Server.

First of all we need to make sure that CLR Integration is activated in SQL Server 2005. This can be done using sp_configure or we can use the new configuration tool called SQL Server Surface Area Configuration. Check that the feature called CLR Integration has a checkmark in 'Enable CLR Integration'.

Now, in Visual Studio 2005, create a new project. Choose the folder Visual C# Projects and the project type called SQL Server Project. Note that this project type is only available in Visual Studio 2005 Professional Edition and above. Name the project as you like, for instance StringHelper.

When the project is being created you will be asked for a database reference. Specify a SQL Server 2005 server and a database. This is the database where you want the functionality to be created.

Add a new item by right-clicking the project and selecting Add New Item, User-defined Function. Name the function RegExValidate.

Now there is a new file called RegExValidate.cs in the project. Edit it with the following code (just clear everything in it and copy-paste this code):

using System.Data.SqlTypes;
using System.Text.RegularExpressions;
using Microsoft.SqlServer.Server;

public partial class UserDefinedFunctions
{
[Microsoft.SqlServer.Server.SqlFunction]
public static SqlBoolean RegExValidate(
SqlString expressionToValidate, SqlString regularExpression)
{
Regex regex = new Regex(regularExpression.Value);

return regex.IsMatch(expressionToValidate.Value);
}
}


More than a year ago, Microsoft released SQL Server 2000 Reporting Services as an add-on to SQL Server 2000. Today, Microsoft announced the newest features in Reporting Services Service Pack 2 (SP2), so I thought now would be a good time to clear up a few misconceptions about Reporting Services 2005. Half the people I talk to think that the next Reporting Services release will be a whole new product with dramatic core changes. The rest of the people I talk to think that because we've seen so much added functionality in Reporting Services 2000 SP1 and SP2, Reporting Services 2005 will be the same as Reporting Services 2000. Although Reporting Services' core architecture isn't changing, the next release has plenty to get excited about. Recently, I talked to Microsoft Group Program Manager for Reporting Services Brian Welcker, who confirmed that the company is adding lots of functionality to Reporting Services 2005; it's worth the upgrade.


You can consider Reporting Services 2005 an entirely new product because it's finally fully integrated with SQL Server 2005--the platform it was originally paired with. Welcker talked about how Reporting Services integrates deeply with the Analysis Services Unified Dimensional Model (UDM) to offer true enterprise reporting from OLAP. (I covered this integration last month in "Analysis Services Integrates with Reporting" at http://lists.sqlmag.com/t?ctl=8469:7B3DB .) Some other new Reporting Services 2005 bells and whistles include a date-picker, multivalue support for parameter selection, in-report resorting of data, a new XML data provider that permits data access from a URL or Web service, and full 64-bit support. Reporting Services can run natively on an Itanium-based server and natively (or in the Windows-on-Windows or "WOW" virtual machine) on Opteron and Xeon-extended machines.


Another great new feature in Reporting Services 2005 is the Report Builder, an ad hoc reporting tool that lets end users intuitively navigate data sources to build and share reports--reports that let them drill down from summary data into granular details. Note that Report Builder will be available only in the Enterprise Edition. Welcker walked me though the process of using the Report Builder Semantic Modeler to generate a semantic data model on top of a SQL Server or Analysis Services data source. Once you have the data model, end users can perform ad hoc data exploration using a lightweight browser-deployed .NET smart client interface against a semantic query engine that generates T-SQL or MDX queries against the underlying database.


Welcker also talked about Visual Studio 2005's embedded reporting capabilities. Visual Studio 2005, which Microsoft is developing and releasing with SQL Server 2005, will offer Reporting Services Report Controls that let applications process and render reports with or without access to a Reporting Services Report Server. This opens many doors for developers to use Reporting Services with OEM applications in unique high-security environments and deploy reporting for SQL Server Express. Interestingly, Microsoft has switched the Report Manager application to use the Visual Studio Report Controls, helping the development team test and optimize the Report Controls.


Many folks have asked me about what it will take to upgrade their Reporting Services environment to 2005. According to Welcker, "Everything will be upgrade-in-place for Report Server. Reporting Services 2000 reports can be run on 2005 though there won't be support for any features that are new in 2005. Reports will be automatically upgraded if opened in the 2005 Report Designer." I think there's a lot to get excited about in the new Reporting Services. Get the April Community Technology Preview (CTP) and be on the lookout for SQL Server 2005 Beta 3 to get started with Reporting Services and Report Builder.


 
Categories: SQL Server

June 7, 2005
@ 09:37 AM
In the Tuesday keynote, Microsoft Senior Vice President Paul Flessner announced that SQL Server 2005, Visual Studio 2005 and BizTalk Server 2006 will all ship the week of Nov. 7.  All

that's left is "fit and finish," said Thomas Rizzo, director, SQL Server product management, in a follow-up interview. He noted that once Microsoft publishes benchmarks, as it did on Tuesday, "we're close to the end" -- welcome news considering the product has been five years in the making. Microsoft said that, according to three TPC-H benchmarks, SQL Server 2005 (formerly known as Yukon) showed performance up to 162 percent higher than SQL Server 2000 and 38 percent higher than Oracle's best shot on comparable hardware. Numbers like that, along with improvements in manageability and integration with products including Visual Studio and Office, will make for a compelling business case, Rizzo says.

 
Categories: SQL Server

This article provides how-to information and code for two different monitoring systems you can set up centrally to manage reporting of SQL Server 2000 maintenance and disk utilization. The first is a scheme I have used in my role as a DBA, which has helped simplify and speed up one of the more mundane tasks we as DBAs are likely to face: checking overnight backups and DBCC checks. The second is a simple system which centrally collects disk drive utilization data from target SQL Servers. This data can be checked regularly to ensure none of your servers are about to run out of disk space, and it is also retained so you can analyze it for trends and use the results for the prediction of your future disk requirements.


Central Maintenance Monitoring

The objective of this system is to provide an automated, central view of your server’s maintenance (backup and DBCC) results for you to review. The information is collected on a central server using a scheduled job and you can interrogate it using a stored procedure. I embed this in a web page which calls the SP on-demand whenever the web page is browsed, but this is a personal preference.


[More]


 
Categories: SQL Server

Microsoft on Friday posted Service Pack 4 for SQL Server 2000, the first service pack update for the company's flagship database server since early 2003.

The major new feature of the service pack is extending SQL Server support to the Windows x64 editions, which run on x86 processors with 64-bit extensions (AMD64 and Intel EM64T). An existing edition of SQL Server 2000 already supported the Intel Itanium architecture for 64-bit computing.


Microsoft released the x64 editions of Windows Server 2003 and Windows XP Professional in late April. Specifically, SP4 will allow customers to run 32-bit SQL Server applications on x64 systems in Windows on Windows emulation (WOW64).


The cumulative service pack includes new bug fixes for the relational database and the Analysis Services component, along with all fixes included in SP1, SP2 and SP3a. The service pack also enhances performance and serviceability.


Microsoft's last service pack came out around the time the SQL Slammer worm raged. Even though it's been awhile, Microsoft's SQL Server developers haven't been standing still on SQL Server 2000 in advance of SQL Server 2005, expected later this year. Since SP3a, Microsoft updated SQL Server 2000's functionality significantly with SQL Server 2000 Reporting Services at the beginning of 2004. Reporting Services received its own SP2 a few weeks ago.


The SP4 download is available at:
http://www.microsoft.com/sql/downloads/2000/sp4.asp


 
Categories: SQL Server

The SQL Server 2005 product family has now been announced, so with four editions available, what does this mean for SQL Server Integration Services? Starting from the bottom we have the free edition known as Express, and the entry level Workgroup edition, and neither include the full IS product. They have the Import/Export capabilities, but nothing more, so for simple loading and extraction of data this should suffice, but you will not be able to build packages.


Read more here


 
Categories: SQL Server

April 5, 2005
@ 07:52 PM

One of the age old problems in DTS is moving packages between your development, test and production environments. Typically a series of manual edits needs to be done to all the packages to make sure that all the connection objects are pointing to the correct physical servers. This is time consuming and gives rise to the possibility of human error, particularly if the solution incorporates many DTS packages. Many companies have provided their own custom solutions for managing this problem but these are still workarounds for a problem that is inherently DTS's.


See full article at http://www.sqlis.com/default.aspx?26


 
Categories: SQL Server

Service pack 1 for Windows Server 2003 was released on Wednesday, March 30th.  In addition release candidate 1 of  Windows Server Update Services was also made available. Windows Update Services is Microsoft's attempt to merge the various update sites that separately managed updates for Windows, Office, and the variying server products.
 
Categories: SQL Server