SQL Server MS Blogs

Loading data to SQL Azure the fast way

MS SQL CAT Team - Fri, 07/30/2010 - 17:11

Introduction Now that you have your database set up in SQL Azure , the next step is to load your data to this database. Your data could exist in various sources ; valid sources include SQL Server, Oracle, Excel, Access, flat files and others. Your data...(read more)

Categories: SQL Server MS Blogs

Quote of the day - Doing the right thing

Bucky Woody - Fri, 07/30/2010 - 07:39

Today's quote is from Ovid, a Roman poet: "Video meliora proboque deteriora sequor"

 (I see and approve the better course, yet choose the worse.)

Unfortunately all too true for me far too often.

Categories: SQL Server MS Blogs

SQL 2008 FileStream Fails to Enable After Setup on Cluster that uses Veritas Mountpoints

SQL Server SQL CSS - Thu, 07/29/2010 - 10:52

Recently a customer ran into an issue where they had successfully installed SQL Server 2008 SP1 on a 2 node Windows 2008 cluster. When they went to restore a database that was given to them, they found out the database was created with the new SQL 2008 FileStream feature and couldn’t restore the database on their newly installed SQL 2008 SP1 clustered instance. So they went to enable FileStream through the SQL Configuration Manager. After clicking the check box “Enable FILESTREAM for Transact-SQL access” and “Enable FILESTREAM for file I/O streaming access”, then attempting to apply their selections they encountered a message in the dialog.

The message appears below the last checkbox (my system doesn’t have the error, but I wanted to show the dialog). The actual message:

"A previous filestream configuration attempt was incomplete. Filestream may be in an inconsistent state until re-configured"

In addition, if you look in the Application Event log you will see an Access Violation was raised:

Faulting application wmiprvse.exe, version 6.0.6002.18005, time stamp 0x49e0274f, faulting module CLUSAPI.dll, version 6.0.6001.18000, time stamp 0x4791acce, exception code 0xc0000005, fault offset 0x000000000001df73, process id 0xca4, application start time 0x01cb28f4bcfeed65.

Cause

This is a bug in the SQL Server 2008 post-setup FileStream Enablement code. We assume the cluster resources are physical disks and not mount points. This causes a NULL value to be returned to the hResult, which we then pass to the Cluster API which causes an AV. We have only seen this problem when using Veritas Storage Foundation (in this case 5.1 SP1 of VSF) mountpoints.

Workaround

1. Uninstall and Reinstall SQL Server 2008 SP1 and enable FileStream as part of the setup. It will succeed. Make sure you backup all system and user databases before uninstalling and reinstalling SQL Server.

2. Change storage so that it doesn’t use Veritas mountpoints

3. This problem will be fixed in CU10 for SQL 2008 SP1 due out in September 2010. This will allow FileStream enablement post-setup when using mountpoints.

Thanks

Eric Burgess

SQL Server Escalation Services.

Categories: SQL Server MS Blogs

Installing SQL Integration Services after SQL Cluster Setup has Completed

SQL Server SQL CSS - Thu, 07/29/2010 - 10:15

Today I ran into an issue where, SQL Server 2008 SP1 was installed on a Windows 2008 cluster and was working just fine, but we wanted to install SQL Server Integration Services (SSIS) to the two nodes of the cluster. Since SSIS is not cluster aware, we thought it was be just a simple process of adding features to an existing instance of SQL Server. Unfortunately, it was not that intuitive.

In setup’s SQL Server Installation Center you naturally select “New SQL Server stand-alone installation or add features to an existing installation”, because you already have a installed instance of SQL Server on the cluster.

In the “Installation Type” step of the setup, if you select the second ratio button to “Add features to an existing instance of SQL Server” is when you run into problems in this situation.

 

If you select the “Integration Services” option only during the “Feature Selection” step, then proceed with the SSIS installation you will encounter the following error if you already have a clustered SQL instance:

---------------------------
Rule "Existing clustered or cluster-prepared instance" failed.

The instance selected for installation is already installed and clustered on computer SQLClustInstName. To continue, select a different instance to cluster.
---------------------------
OK  
---------------------------

Of course, you don’t want to install another cluster to your instance, but here is the key: you do want to “Perform a new installation of SQL Server 2008”, which is the first radio button in the Installation Type step of the setup (screen shot above). This will allow you to select any feature you desire to put on the system in the Feature Selection step:

Here you would only select “Integration Services” (unfortunately my screen shot shows I have SSIS already installed). By just choosing “Integration Services” you can successfully install SSIS on each node of the cluster. You must run this setup on all nodes of the cluster where you want the SSIS service installed.

Note: Don’t forget to alter you <ServerName>.\SQL2008</ServerName> property in the MsDtsSrvr.xml file to correctly point to your SQL virtual server name rather than the default “.\InstanceName” that is currently there.

Have a great day!

Eric Burgess

SQL Server Escalation Services

Categories: SQL Server MS Blogs

Just how permanent does that data need to be?

Bucky Woody - Thu, 07/29/2010 - 06:23

As data professionals, we plan for things. We plan for growth, we have a disaster-recovery plan, we have a plan for consolidation. Those are all good things. But I've seen very few shops that have a good data retention plan. This is a plan that basically answers the question, how permanent does that data need to be? Just like the disaster recovery plan, we have to ask the organization what they want, and just like that DR plan they'll tell you they want it all. In the case of the DR plan, they'll say "we don't want any downtime", and when you ask them how long to keep a set of data they will say "forever". But both of those things come at a cost. Not only is there a storage cost, but as the data grows your window for maintenance, backups and optimization grows.

So take some time today and put that retention question on your roadmap. I know, you have a lot to do, but if you don't at least open the discussion now, you'll have a lot more to do in the future.

Categories: SQL Server MS Blogs

The Microsoft IT Showcase

Bucky Woody - Wed, 07/28/2010 - 07:27

I had dinner in Seattle (three words: bacon-wrapped-steak) with the folks that put on "How Microsoft Does IT" (get it? Does "it", "IT"? OK, I'm easily amused) and I wanted to point out this fantastic resource to you - again. I rave about it all the time, because before I started at Microsoft I worked at shops large and small, and many times I was called on to come up with strategies and architectures for my organizations. And what better place to start than the people who wrote the software, and use it in their business every day. There are so many references there you'll never get through them all.

If you're not familiar with the site, it's a great compilation on how we at Microsoft run our IT infrastructure - Windows, Office, SharePoint, Exchange, SQL Server, Biztalk, the whole thing. If you don't have it bookmarked, definitely go check it out. There's a DVD you can order as well, and we keep the site very up-to-date and current.

The link is here: http://technet.microsoft.com/en-us/library/bb687780.aspx 

Categories: SQL Server MS Blogs

The TechNet Wiki and Updated Security Checklists

Bucky Woody - Tue, 07/27/2010 - 07:18

You're probably familiar with a Wiki - a document set that anyone can edit. Did you know TechNet (Microsoft's source for technical professionals) has one? And did you know there are lots of folks keeping it up to date? Well, Rick Byham, one of my friends over in the SQL Server group has posted a bunch of security checklists - and you know how much I love checklists! You can go to the Wiki here: http://social.technet.microsoft.com/wiki/ and search for "Checklists", but here's what he's posted to get you started:

Database Engine Security Checklist: Encrypting Sensitive Data

Database Engine Security Checklist: Enhancing the Security of Database Engine Connections

Database Engine Security Checklist: Limiting Access to Data

Database Engine Security Checklist: Database Engine Security Configuration

Thanks, Rick!

Categories: SQL Server MS Blogs

Security Checklists on TechNet Wiki

SQL Server Security Team - Mon, 07/26/2010 - 13:34

Rick Byham, our wonderful technical writer, just posted some checklists you may find useful on the TechNet Wiki. You can search the wiki for word checklist or use these links:

Database Engine Security Checklist: Encrypting Sensitive Data
Database Engine Security Checklist: Enhancing the Security of Database Engine Connections
Database Engine Security Checklist: Limiting Access to Data
Database Engine Security Checklist: Database Engine Security Configuration

It's a wiki, so feel free to correct, comment, etc. Hope this becomes a good resource for the collective knowledge out there on these topics. Thanks Rick!

Categories: SQL Server MS Blogs

Exploration and Understanding

Bucky Woody - Mon, 07/26/2010 - 07:49

As most of you know, I tend to spend a little time on social networks like Twitter, FaceBook and LinkedIn. On one of those networks, Ken Simmons sent the following thought: “One hour sessions give you great ideas you can explore; full day sessions give you in depth knowledge you can use.” He was talking about the difference in a one-hour session and an all-day event at the Professional Association of SQL Server (PASS) summit.

 

He brings up a great point. Many sessions at a technical conference have a “level” associated with them – 100 for beginners through 400 for advanced topics. This can be challenging – if you give a 400-level presentation, you have to assume a great deal of knowledge on the part of the audience, and in one hour you can only cover something very specific at that level. For instance, you could cover in one hour the details of how the locking mechanism works, but only in specific circumstances.

 

An all-day (or at least more than a few hours) workshop, on the other hand, allows you to start with the basics and move all the way to some fairly advanced information. When you think about it, it’s where you spend the time, in-class or on your own. The issue is when you forget this, and believe that a speaker can get you from 100 to 400 level in one hour – it just doesn’t work like that.

 

I’ve got an article here on how to attend a technical conference. Might be worth a look.

Categories: SQL Server MS Blogs

Quote of the Day: On Earning it Yourself

Bucky Woody - Fri, 07/23/2010 - 07:25

 Never stand begging for that which you have the power to earn.        Miguel de Cervantes

Categories: SQL Server MS Blogs

When you’re asking for help, make sure you explain what you’re trying to accomplish

Bucky Woody - Thu, 07/22/2010 - 06:24

At some time, all of us need technical help with something. Whenever you do, make sure you try and frame the question not necessarily in terms of what you want to know, but what you're trying to do. Spending time on thinking through your questions will help you get better answers, and people will appreciate that you're putting some effort into the process, and they are more willing to get help.

For instance - let's say yo're stuck on a particular SQL Server Replication issue. You're not sure whether moving the Distributor function away from the Publisher server is the right thing to do, given your budget. You could ask:

"Where should the Distrbutor go in a Replication scheme?"

That's too vague, and doesn't help others help you. Instead, this might be a better way to put the question:

"I'm setting up the design for my Replication scheme, and I have a limited budget. What are the best ways to save money in my design?"

This question goes more towards what you really want to know, and in fact, you may find out that the Distributor question isn't what you need to care about at all. Sure, sometimes you just want the phone number to a store, and you really don't need to tell everyone you're hungry, but if the question goes beyond simple facts, it's a good idea to include as much information as possible so folks can help you best.

Categories: SQL Server MS Blogs

Why does PREEMPTIVE_OS_GETPROCADDRESS Show a Large Accumulation?

SQL Server SQL CSS - Wed, 07/21/2010 - 06:56

There is a bug in SQL Server 2008 that causes PREEMPTIVE_OS_GETPROCADDRESS to include and accumulate the execution time of the extended stored procedure (XPROC). The following is an example showing the increase in the GetProcAddress wait time.

select * from sys.dm_os_wait_stats where wait_type = 'PREEMPTIVE_OS_GETPROCADDRESS' or wait_type = 'MSQL_XP'
exec master..xp_dirtree 'f:\'
select * from sys.dm_os_wait_stats where wait_type = 'PREEMPTIVE_OS_GETPROCADDRESS' or wait_type = 'MSQL_XP'

GetProcAddress is used to load the entrypoint in the DLL (XPROC) and should complete quickly but due to the accumulation bug the wait time is inflated.   To get a better idea (ballpark) of how long GetProcAddress really takes you can using the following query.

declare @WaitTime bigint
select @WaitTime = wait_time_ms from sys.dm_os_wait_stats where wait_type = 'MSQL_XP'
select @WaitTime - wait_time_ms from sys.dm_os_wait_stats where wait_type = 'PREEMPTIVE_OS_GETPROCADDRESS'

Bob Dorr - Principal SQL Server Escalation Engineer

Categories: SQL Server MS Blogs

Presentation Links: SQL Server Performance Tuning (Quest)

Bucky Woody - Wed, 07/21/2010 - 03:54

I worked with a team of folks brought together by Quest software, and we presented multiple sessions on SQL Server Performance Tuning. Here are the links I mentioned during those presentations:

 

Blitz! SQL Server Takeovers (Brent)

 

You're minding your own business in your corner office - well, no, you're a DBA, so it's just your cubicle - when somebody says, "Did you know about this SQL Server over here?" Suddenly, you have to find out what the server's doing, how it was set up, and whether things are working correctly. In this real-time session, Brent will show you how he tackles unknown servers in 60 minutes to find problems, take an inventory, and set the server up for easier management down the road.

·        SQL Server Best Practices Article: http://technet.microsoft.com/en-us/library/cc966412.aspx

·        How to determine proper SQL Server configuration settings: http://support.microsoft.com/kb/319942

·        Setting Server Configuration Options (SQL Server 2008 R2, other versions available) : http://technet.microsoft.com/en-us/library/ms189631.aspx

·        Running SQL Server 2008 in a Hyper-V Environment - Best Practices and Performance Recommendations: http://download.microsoft.com/download/d/9/4/d948f981-926e-40fa-a026-5bfcf076d9b9/SQL2008inHyperV2008.docx

·        Checklist: SQL Server Performance: http://msdn.microsoft.com/en-us/library/ms979169.aspx

·        Script Repository for SQL Server Information: http://gallery.technet.microsoft.com/ScriptCenter/en-us/site/search?f%5B0%5D.Type=RootCategory&f%5B0%5D.Value=databases&f%5B0%5D.Text=Databases&f%5B1%5D.Type=SubCategory&f%5B1%5D.Value=sqlserver&f%5B1%5D.Text=SQL%20Server

 

 “Turn your head and cough” – Quick Health Check Using Wait Stats for the SQL Server Takeover (Kevin)

So you’ve survived the SQL Server Blitz and have made sure that your server is properly setup, configured, and under proper preventative maintenance.  Now it’s time to play doctor and determining the health of your SQL Server.  Kevin will slip on the latex gloves and show you how to determine the health of an unknown server and the applications running on that SQL Server with a quick physical.

·        SQL Server Best Practices Analyzer (SQL Server 2008 R2, other versions available) : http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=0fd439d7-4bff-4df7-a52f-9a1be8725591

·        Microsoft Assessment and Planning (MAP) Toolkit for SQL Server 2008 (will detect all the way down to SQL Server 2000): http://technet.microsoft.com/en-us/solutionaccelerators/dd537572.aspx

·        DMV Stats:  http://www.codeplex.com/sqldmvstats

·        SQL Server 2005 Performance Dashboard Reports: http://www.microsoft.com/downloads/details.aspx?familyid=1d3a4a0d-7e0c-4730-8204-e419218c1efc&displaylang=en

 

Lose Wait Fast with Wait Stats (Brent)

It's time for you to get serious about wait loss - no, not weight loss, but wait loss.  SQL Server wait stats will tell you what your queries and your server have been waiting on, and you don't even have to use Profiler or tracing!  Brent will show you how to troubleshoot issues in real time and check historical data.  He'll also show tools to make this process easier.

·        Troubleshooting Performance Problems in SQL Server 2008 Whitepaper (2005 version also available) : http://msdn.microsoft.com/en-us/library/dd672789.aspx

·        SQL Server 2005 Performance Tuning using Waits and Queues:  http://technet.microsoft.com/library/cc966413.aspx

·        SQL Server 2005 Waits and Queues: http://sqlcat.com/whitepapers/archive/2007/11/19/sql-server-2005-waits-and-queues.aspx

·        OLTP Top 6 Performance Issues for OLTP Applications:  http://www.microsoft.com/technet/prodtechnol/sql/bestpractice/oltp-performance-issues.mspx

·        Top SQL Server 2005 Performance Issues for OLTP Applications: http://sqlcat.com/top10lists/archive/2007/11/21/top-sql-server-2005-performance-issues-for-oltp-applications.aspx

 

PerfMon is “Irie Mon” (Kevin)

They say “irie mon” in Jamaica when everything is going well.  Performance Monitor is irie! It’s an extremely important tool in the pocket of any IT professional because it’s available on every version of Windows and provides valuable performance information across all of the components of SQL Server, from the relational and storage engine to SSIS, SSAS, and SSRS.  Kevin will show you how to make sense of PerfMon’s multitude of counters, how to store PerfMon data for long-term analysis, and how to correlate PerfMon

·        Windows Reliability and Performance Monitor : http://technet.microsoft.com/en-us/library/cc755081(WS.10).aspx

·        Overview of Windows Performance Monitor: http://technet.microsoft.com/en-us/library/cc749154.aspx

·        Scripts and Tools for Performance Tuning and Troubleshooting SQL Server 2005: http://www.microsoft.com/technet/scriptcenter/scripts/sql/sql2005/default.mspx

·        Troubleshooting Performance Problems in SQL Server 2008: http://sqlcat.com/whitepapers/archive/2009/04/14/troubleshooting-performance-problems-in-sql-server-2008.aspx

 

Categories: SQL Server MS Blogs

PowerShell and Extended Properties

Bucky Woody - Tue, 07/20/2010 - 06:43

I use Extended Properties on databases and their objects all the time. They are a great way to include information about the object – I use them for versioning the database, detailing what a column is used for and so on. They can be a little tricky to set, but it’s really not bad once you learn how.  Ken Simmons, a SQL Server MVP has a fantastic article here that explains more: http://cybersql.blogspot.com/2010/07/extended-property-awesomeness.html

 

Although it’s not as simple as I would like to set the properties using PowerShell, it’s really trivial to read them. I do this to make system documentation in an HTML page. Open a SQL Server 2008 Powershell provider (sqlps.exe) and CD to any “directory” of a database or tables, views, whatever. Then you can just type this:

DIR | select-object –property name, Extendedproperties

 

As always, do this on a test system.

 

Script Disclaimer, for people who need to be told this sort of thing:

Never trust any script, including those that you find here, until you understand exactly what it does and how it will act on your systems. Always check the script on a test system or Virtual Machine, not a production system. Yes, there are always multiple ways to do things, and this script may not work in every situation, for everything. It’s just a script, people. All scripts on this site are performed by a professional stunt driver on a closed course. Your mileage may vary. Void where prohibited. Offer good for a limited time only. Keep out of reach of small children. Do not operate heavy machinery while using this script. If you experience blurry vision, indigestion or diarrhea during the operation of this script, see a physician immediately.

Categories: SQL Server MS Blogs

Cumulative Update #9 for SQL Server 2008 Service Pack 1

SQL Server Release Blog - Mon, 07/19/2010 - 19:01

Keep your system up to date with the most recent cumulative update package for SQL Server 2008 SP1. This package contains all of the SQL Server 2008 hotfixes that have been released since the initial release of SQL Server 2008 SP1. Understanding Incremental...(read more)

Categories: SQL Server MS Blogs

Performance Monitor and Wait Events Presentation with Quest

Bucky Woody - Mon, 07/19/2010 - 07:41

Quest Software is a great partner with Microsoft, and I’m honored to be able to present with Brent Ozar, Kevin Kline and Ari Weil at a day-long event that you can attend for free. We’re going to cover many aspects of performance tuning, from waits and queues to the Windows System Monitor, which you might also know as PerfMon or Performance Monitor.

It’s expensive to go to conferences, so when your boss complains that you’ll be gone all day, remind him/her that it’s *free*. (Plus, you can tell them I said it’s OK. )

Register here: www.quest.com/julyvtbwblog 

Categories: SQL Server MS Blogs

External Activator Security

SQL Server Service Broker Team - Mon, 07/19/2010 - 00:54

This short post deals with security and permission-related aspects of External Activator.

Selecting External Activator service account

When you install External Activator, you are asked to choose the service account (the Windows account that External Activator service will run as). The choice is from well-known Windows service accounts and a custom user with a password. For more information on the well-known accounts, please refer Sql Server Books Online or MSDN pages. The recommended service account for External Activator is a local or domain user.

Local security groups created by External Activator

The External Activator setup application will also create one or two (depending on the Operating System) local security groups for administrative purposes.

The first group, SSB EA Admin, is created regardless of the OS used. Members of this group have permission to start/stop the service, view the trace (log) file and modify the configuration file. The purpose of this group is to provide sufficient privilege separation so that the user(s) configuring and running External Activator doesn’t have to be a box admin.

The second group, SSB EA Service, is only created on down-level OSes and its purpose is to make changing External Activator’s service account easier (more on that below).

Changing External Activator’s service account

On newer OSes (starting from Vista/Server 2008) changing External Activator’s service account is as simple as setting the new account in Services MMC snap-in (Win-R –> services.msc). The reason it works is that ACLs on External Activator’s files are created based on Service SID, which is independent of service’s “real” service account (more about Per Service SID can be found here). On down-level OSes using the Services MMC snap-in is not enough, because changing the External Activator’s service account there won’t automatically change the file ACLs to the new account. This is something you need to do yourself, but in order to make it easier, the SSB EA Service local group has been introduced. The files are ACLed to be accessible by members of SSB EA Service group rather than by the External Activator’s service account directly. Therefore, when changing service account, it’s enough to add the new account to that group (and possibly remove the old one), without the need to actually touch any file ACLs. You can do that from a command line window:

net localgroup “SSB EA Service” /add “<new account name>”
net localgroup “SSB EA Service” /delete “<old account name>”

Local security groups created by External Activator

One of the previous posts provided a detailed description of all the Sql Server permissions that External Activator needs in order to work properly. It all starts with creating a Sql Server login for External Activator to use. There are several options how this login may be created, depending on the topology of the services:

1. External Activator runs on a machine in different domain from the machine hosting Sql Server. Even though External Activator doesn’t support Sql authentication when connecting to the notification service, you can still make connections across domain boundaries. The trick is to use “mirrored accounts”, which boils down to creating a local/domain windows user on the database server with the same username and password as the External Activator’s service account. The service account must be a local or domain user (you can’t use e.g. NT AUTHORITY\NETWORK SERVICE). Once you create a Sql Server login from that user and grant necessary Sql Server permissions to that login, External Activator will be able to connect, even from outside of the database server’s domain.
2. External Activator runs on different machine from Sql Server, but both machines are in the same domain or in trusted domains.
   1.  
      1. If External Activator runs as NT AUTHORITY\NETWORK SERVICE or NT AUTHORITY\SYSTEM, the login may be created from machine account (e.g. MyDomain\EaMachine$ - note the dollar sign necessary for machine accounts).
      2. If External Activator runs as domain user, the login may be created from that user directly (e.g. MyDomain\EaUser).
      3. If External Activator runs as local user, you have to resort to using mirrored accounts as described above.
      4. NT AUTHORITY\LOCAL SERVICE is not supported as External Activator service account in a multi-machine deployment.
3. External Activator runs on the same machine as the Sql Server it’s connecting to. In this case, in addition to the above possibilities, you can also use the following:
   1.  
      1. If External Activator runs as local user, the login may be created from the local user (e.g. MachineName\EaUser).
      2. If the OS is Vista or higher, the login may be created using the service SID (i.e. NT SERVICE\SSBExternalActivator).
      3. If the OS is older than Vista, the login may be created using the SSB EA Service local group (i.e. MyMachine\SSB EA Service). Note however that it won’t work if External Activator runs as NT AUTHORITY\SYSTEM. Local system is a special account and even if it belongs to SSB EA Service security group, that group’s token won’t be passed to Sql Server when External Activator tries to log in, hence the login will fail.
         
         The advantage of using Service SID/SSB EA Service group as a base for Sql login is that nothing needs to be done on Sql Server side when External Activator’s service account is changed.

Categories: SQL Server MS Blogs

Quote of the Day – Motivation and Talent

Bucky Woody - Fri, 07/16/2010 - 07:48

“Motivation will almost always beat mere talent.” - Norman Augustine

Categories: SQL Server MS Blogs

Side-By-Side Installations – What gets changed?

Bucky Woody - Thu, 07/15/2010 - 07:06

I was asked yesterday if it was “OK” to install SQL Server 2008 R2 on a system that already had SQL Server 2008, but without upgrading. In other words, they wanted to keep both versions of SQL Server running at the different levels. That’s supported; and it’s called a “side-by-side” installation. that means you’ll end up with at least one “Named Instance”, one at the first version and the other at the newer version. Everything is kept separate.

Well, not *everything*. While the engine, databases and all those kinds of things will still have separate versions, there are things that will be upgraded no matter what – it’s just a consequence of the upgrade. The list of things that will get a single, new version for SQL Server 2008 R2 when upgrading from 2008, for instance, from Books Online reads like this:

• Integration Services

• SQL Server Browser

• SQL Server Active Directory Helper Services

• SQL Server Profiler

• SQL Server Native Client

• SQL Server Policies

• SQL Server System CLR Types

• SQL Server VSS Writer

• SQLdiag Utility

• Management Tools

  • Basic

  • Complete

• Business Intelligence Development Studio

• Client tools connectivity

• Client tools SDK

• SQL Server Books Online

• SQL Client Connectivity SDK

So it’s important to keep that in mind. There’s a topic similar to that link for 2005 in the Books Online for 2008, so you can see what will change if you make that upgrade as well. By and large it’s that same list.

You will see a difference from 2000, however, since some of these tools don’t exist on that older platform. In that case, you may end up with a bit of a mix – you’ll still have Enterprise Manager running around, for instance.

Installations and upgrades can be a difficult topic, but as long as you take your time and read through the installation planning documentation, you can write out the notes for what applies to you.

Categories: SQL Server MS Blogs

Designing Dashboards

Bucky Woody - Wed, 07/14/2010 - 08:44

Not all data professionals get into the "front end" of the applications that hit their data. But most of us end up having to do a "dashboard" of information, even if it's a dashboard of our system information and performance tracking. I do this quite often for myself and for other folks, and I wanted to share a resource I use for that. It's from a site called "Quince", and I really like the way they break down all kinds of User-Interface (UI) information. Well worth your time to take a look, and share with your dev friends: http://quince.infragistics.com/#/Main/ViewPattern$pattern=Dashboard/PatternExamples$guid=0cdc0314-2ab3-4981-bbef-0b7a038adab2 

Categories: SQL Server MS Blogs