Search results matching tags 'denali', 'SQL Denali', and 'download'

SQL Server 2012 : The Data Tools installer is now available

AaronBertrand — Mon, 21 Nov 2011 15:18:00 GMT

Last week when RC0 was released, the updated installer for "Juneau" (SQL Server Data Tools) was not available. Depending on how you tried to get it, you either ended up on a blank search page, or a page offering the CTP3 bits. Important note: the CTP3 Juneau bits are not compatible with SQL Server 2012 RC0.

If you already have Visual Studio 2010 installed (meaning Standard/Pro/Premium/Ultimate), you will need to install Service Pack 1 before continuing. You can get to the installer simply by opening Visual Studio, going to File > New > Project, and then choose the option "SQL Server" that appears under the "Other Languages" category (not the "SQL Server" option that appears under the "Database" category):

When you click OK, you will get another dialog that prompts you to install SQL Server Data Tools:

When you click Install, your web browser will be launched on the Data Tools "Get Started" page. There you will see a link to "Download SQL Server Data Tools" which will launch or download SSDTSetup.exe:

At this point I would close Visual Studio 2010, because you'll probably be prompted to close it anyway.

As usual you'll be prompted with a security warning:

Next you'll need to agree to the lengthy license terms and conditions:

Next it will download LoaclDB (the new dev/Express runtime) and install. For me on multiple installs the Installation Progress bar held at 99% for a noticeable amount of time:

With a little bit of luck you should end up at the "Success" screen:

Now you can open Visual Studio directly (or from the "SQL Server Data Tools" menu item under All Programs > Microsoft SQL Server 2012 RC0. Choose File > New > Project and again choose "SQL Server" under "Other Languages." The option depicted above has changed to "SQL Server Database Project":

Click OK. You will find a Toolbox and a familiar Object Explorer on the left, where you can easily create new objects:

And now you can go to town developing your project. I haven't tried upgrading a project from CTP3 or from a previous version of "Data Dude." You're on your own there, sorry.

As an aside the "other" SQL Server option under "Database" contains all the old project types that you may not want to use anymore. I hope they straighten this out and consolidate by RTM:

If you already had Juneau CTP3 installed, you should be able to install SQL Server Data Tools CTP4 as an upgrade by simply downloading the updated SSDTSetup.exe from the "Get Started" page. You may still need to install Visual Studio 2010 Service Pack 1 prior to doing so. For what it's worth, I completely removed SQL Server 2012 CTP3 and Juneau CTP3 before attempting to install the updated bits. If you try an upgrade and come across any issues, please let me know.

You may be wondering why the versioning seems out of cadence - SQL Server is at RC0 while Juneau is at CTP4. This is because SQL Server is feature complete and an upgrade to RTM will now be supported. Juneau is not quite complete (there are still some pending changes before RTM); the naming remains CTP so that folks do not get the impression that an upgrade to RTM will be supported.

SQL Server v.Next (Denali) : Putting Juneau CTP3 over Juneau CTP2

AaronBertrand — Thu, 14 Jul 2011 22:04:00 GMT

Okay, I'll be the first to admit, I tried to install CTP3 on a machine without first cleaning up the CTP2 bits. My primary motivation was to be able to query the catalog views to detect any metadata changes that I hadn't already talked about here. As you might have guessed, this experiment did not go well.

In a couple of cases I have installed CTP3 quite cleanly on new VMs. I haven't installed Juneau yet on those, because I'm a little nervous about what exactly that will do to Management Studio... and I need at least one VM where I can rely on full functionality there. I'm getting there, but I wanted to address the case where CTP2 *was* installed.

In cases where I would prefer to keep my existing VM (which has various other ongoing work other than Denali, making it infeasible to roll back to some snapshot), I've resorted to removing every single CTP1 or CTP2 piece of software using Programs and Features (nee Add/Remove Programs). Once I had removed CTP2 completely, I ran a repair of CTP3. I then realized that I didn't have Management Studio (because the complete removal of CTP2 included shared features such as client tools). So I ran setup again, adding the Management Tools and a few other odds and ends to the instance.

Now, with all traces of CTP2 gone (including Juneau), and a now functional CTP3 and Management Studio, I thought it was time to install Juneau. No problem, I go for the web installer, located here:

http://www.microsoft.com/web/gallery/install.aspx?appid=JUNEAU10

Unfortunately, all signs indicate that this is going to try to install CTP2:

Fellow MVP Juan Alvarado pointed me to the registry key that was causing this problem (thanks Juan!). It is one of the things that the CTP2 of Juneau did not clean up through the normal uninstall process. The key is:

HKEY_LOCAL_MACHINE\Software\Microsoft\WebPlatformInstaller\ProductXmlLocation\

It will have a value of some folder on your machine (I changed the value to foo because my path was really long)... just change the name of the key to something else, or delete it entirely, and run the web installer again. You should see the right platform now:

I can't fault the team for this problem at all. I shouldn't expect CTPs to remove cleanly, and should know not to put CTPs on important machines or VMs that can't just be rebuilt as needed.

Ultimately, what you *REALLY SHOULD* be doing is installing CTP3 (both engine components and add-ons like Juneau) in a clean virtual machine. But I know how it is, it isn't always practical to dedicate an OS this way. So hopefully this helps some of you work around the issue.

In addition, I am in no way guaranteeing that Juneau will *work* - just that you should be able to get it installed. Once it's installed, I'm afraid you're on your own. If it doesn't work correctly, please read the previous paragraph.

SQL Server v.Next (Denali) : Juneau CTP3 is now available!

AaronBertrand — Wed, 13 Jul 2011 13:32:00 GMT

SQL Server Developer Tools (SSDT) - code-named "Juneau" - is now available. Many (including myself) believed that Juneau was simply a part of BIDS in CTP3, but after trying to use Juneau-specific functionality that this was not the case. As indicated on the Developer Tools page, and on the SSDT blog, you can download Juneau now through a Web Platform Installer.

According to this page, if you're already using Visual Studio Professional, you need to install Visual Studio 2010 SP1 *FIRST* (though if you've installed Denali, you've probably already done this), otherwise your shell gets downgraded to only have Juneau functionality - at least that's how I've read it. In any case, suggest being up to date on Windows Updates and make sure that SP1 is installed before installing Juneau. You'll also want to be sure you install the CTP3 version of Juneau on a machine that has never had a previous version of Juneau installed - even a proper add/remove does not truly get rid of all of the pieces, and you're likely to end up with a quite crippled installation. All the more reason to use a VM for Denali stuff, since it is easy enough to throw away and re-create those.

You can start the Web Platform Installer by clicking on the following link:

http://www.microsoft.com/web/gallery/install.aspx?appid=JUNEAU10

First, you'll be asked by Internet Explorer if you're sure you want the Web Platform Installer to go about its business:

Then you'll be asked again, if you have UAC enabled:

Once you allow the program to run, you will see this introductory screen:

It says the download size is 8.51 MB, but that is a lie. To see the true download size, click on the "Items to be installed" link in the bottom left corner. You will see something like this:

My first observation here was that the local database runtime actually points to the SQL Express installer. It is not supposed to be a standalone instance, and it's interesting that they are finding a way to make Express support non-Express features that Juneau will have to support (e.g. partitioning).

When you click Install, you will be prompted (of course) to accept a license agreement. This screen also shows a summary of the items that are going to be downloaded and installed. You can click on the individual links to download each package and install them yourself, but I recommend against that because some need to be laid down in a specific order.

Once you accept, installation will begin. This took a surprising amount of time on my system (equipped with 8GB RAM and an SSD), even after all the downloading had finished.

(A funny observation here: this is my laptop, which I use for presenting, and it is yet another example where dialogs are not tested at non-default font settings - I have my fonts set to 125%, and the text no longer fits within the dialog.)

Depending on the state of your system (including Windows Updates), you can expect several reboots to be required during the installation of various Juneau prerequisites. If you have any failures installing the dependencies (which will prevent Juneau itself from being installed), you can try running their installers manually by clicking on the download links in the failure dialog - just make sure you run the Juneau installer last. I had a heck of a time installing the .NET Framework 4.0 update from KB #2468871 using the Web Platform Installer, but after running the EXE from the KB article manually, I finally had success:

I then re-applied Visual Studio 2010 Service Pack 1 (again), just to be on the safe side. Of course I had to clear out some space first, as this is on a tight SSD - the SP1 installer apparently needs close to 6 GB free just to run.

So now when I launch my BIDS shortcut, this is the splash screen I see:

Once I opened Juneau, my experience with connecting to a server and performing various operations has not been great, so I'll leave my evaluation and description of those things for another post.

SQL Server v.Next (Denali) : CTP3 Installation Walk-Through

AaronBertrand — Tue, 12 Jul 2011 13:07:00 GMT

In case you missed my previous post, you can now download CTP3. The delivery mechanism this time is a little different. Instead of downloading an ISO, you download a very small EXE, two .box files, and an HTML file that currently contains a set of links that aren't fully functional. You run the EXE by double-clicking it, and it extracts the box files into a folder in the same location called SQLFULL_x64_ENU:

Don't do what I did. In order to easily expose the CTP to all of my virtual machines (including Server Core), I took the four files and made an ISO file. When I tried the above process using the ISO file exposed to the VM as a DVD drive, it ran through the unloading process, then went away silently. I tried this a couple of times before I realized what was going on - Windows will not let you write output to a "DVD" - and that the unloading was being attempted in place (and I haven't examined the exe to determine if there are any arguments you could pass to tell it where to send the output - I tried /x, which is the argument used for cumulative updates, and that didn't work). I'm kind of surprised that there isn't a prompt for output location, and I'm absolutely amazed that the unloading process whistles along happily - with no error message or any indication whatsoever that it couldn't create the output folder or extract the files there.

Anyway, now I am off to make an ISO of the *result* of that operation. The lesson here is, copy the four files to a location where you have at least 6GB of free space, since you won't be able to run the command from one location and have it extract the contents to another.

[Also, please be sure to check out my notes on operating system support and prerequisites; also, consider installing Denali in a virtual machine, especially if you are worried about compatibility with your existing applications (Visual Studio, BIDS, etc.) or other instances of SQL Server.]

Once you have done that and you have your SQLFULL_x64_ENU folder ready, double-click SETUP.EXE. You will eventually be right back in to the SQL Server Installation Center you know and love. Click on the Installation tab (for any of the following screen shots, click on them to embiggen in a new window):

Then click on "New SQL Server stand-alone installation or add features to an existing installation" - you'll go through Setup Support Rules, which will hopefully all pass with flying colors:

(Remember to not close the Installation Center dialog until after setup is complete. This window needs to remain open as it keeps the temporary folder used by setup, though it can be minimized. See Connect #388671 for more details.)

Click OK. Next you will have the choice to enter a product key or choose a free edition. It is pre-selected to Evaluation edition:

Click Next. Check the box that says you accept the license terms. I would never suggest to not read them from start to finish, but I'll let you guess how long I spend on this screen. (I usually do uncheck the box about sending feature usage data to Microsoft.)

Click Next. The Install Setup Files dialog checks for updated setup files; is it possible this is the first clue that we are going to have automatic slipstreaming in Denali? I hope so:

Then shortly after my first "SQUEEEEE" moment, I get my first "BOOOOO" moment:

Click OK. Sheepishly. In fact, I implore you to click OK sheepishly. :-)

Now we see the Setup Support Rules dialog. Click Next unless you want to see the details (or any of the rules failed):

Next we choose the Installation Type. Since this is my first taste of CTP3, I will choose the [Perform a new installation of SQL Server "Denali" CTP3] option:

Click Next. n the Setup Role tab I'm going to keep things simple and choose the [SQL Server Feature Installation] option:

Click Next. On the Feature Selection tab, again for simplicity, I'm going to choose Database Engine Services, Books Online Components, and both Management Tools options (see more about Books Online toward the end of this post). I'm tempted to add DQS and Distributed Replay here, but my first instance is going to be pretty bare bones (note that if you have BIDS, Visual Studio, or Juneau from a previous CTP installed, you'll want to select as many of those options that seem relevant - most importantly Business Intelligence Development Studio):

Click Next. We'll let the Installation Rules succeed (unless you are unlucky):

Click Next. Now we select our instance name. I'm way beyond the ability to choose a default instance here, and I'm not all that creative:

Click Next. Simple summary screen showing disk space requirements. I clearly need to learn to build bigger VMs:

Click Next. You can change the service accounts and startup type on the Server Configuration tab. For local testing instances I rarely find it necessary to do this, especially during setup, since they can be configured later if need be. I also don't touch the Collation tab, leaving the default in place (though for pure development environments I will probably be getting more in the habit of switching to case sensitive):

Click Next. On the Database Engine Configuration screen, you can change to mixed authentication, add an sa password, and add yourself and other Windows accounts as SQL Server Administrators:

And on the Data Directories tab, you could change the location for new databases, tempdb and backups. On a normal system I would be changing these appropriately, but since I am on a VM with a single C:\ drive, I'm a little limited to what I can do to spread this I/O around. Thankfully I am not planning to do any heavy activity on my workstation:

I'm not going to use FILESTREAM for this instance, once again for simplicity, so I'm going to leave this tab alone. Click Next.

The Error Reporting dialog allows you to choose whether to send error reports to Microsoft. I'm going to leave this checked (though I unchecked it earlier in the beta cycle because I assumed there would be a lot more "that's already on the books to get fixed" type of exceptions):

Click Next. We get another rules screen, this time the Installation Configuration Rules screen. These might fail if you're still using FAT32, for example, so I can't imagine too many people will get blocked here:

Click Next. Finally we are at a summary screen which lists all of the options we've chosen and what SQL Server setup thinks it's going to try to do:

Click Install. Progress is indicated (you'll see various status message whiz by, faster than you can read them, for about 10 minutes - or less if you are on an SSD):

And finally, completion:

Click OK, click Close, and sheepishly (yes, sheepishly) reboot. Now you can launch Management Studio and start sniffing around:

Note that if you start sniffing around before you've rebooted, you may get some strange errors when trying to connect:

I know you're impatient, but just reboot. I also noticed that I had to manually start the service for the new CTP3 instance, even though it had been set to start automatically. Not sure if I just didn't wait long enough, but starting it manually worked fine.

Finally, I am finding the following error occurs when I try to launch a new query by right-clicking a database or server in Object Explorer and selecting New Query (if I try to modify an existing stored procedure, the dialog is identical, but it's a yellow exclamation point instead of a red x):

The error dialog is only slightly different (an additional top-level error message, and now it isn't an error, it's an informational dialog) if I try File > New >Database Engine Query:

And the error is once again an error, but still a slightly different dialog (I can no longer copy the text) if I use Ctrl + N or try to open an existing .sql file using File/Open:

For searchy goodness, here is the text of the error message:

TITLE: Microsoft SQL Server Management Studio
------------------------------
Failed to create new SQL Server script.
------------------------------
ADDITIONAL INFORMATION:
Method not found: 'System.Collections.Generic.List`1<System.Object> Microsoft.SqlServer.Management.UI.VSIntegration.GenericUtilityView.get_OpenedEditors()'. (mscorlib)
------------------------------

I tried to fix this by re-applying Visual Studio Service Pack 1, as I had recommended in my previous post (once again, do as I say, not as I do). The SP1 update package complained about a missing silverlight_sdk.msi:

Microsoft Silverlight 4 SDK

The feature you are trying to use is on a network resource that is unavailable.

Someone should file a bug on this; the exclusion of this MSI file is especially annoying in this case because I don't care about the Silverlight SDK. Anyway, the fix: download the Silverlight 4 Tools, run the exe from a command line with the /x argument, specify a folder when prompted, and then you can point the SP1 installer at that folder. What a mess. And it gets even worse; I next got a similar complaint about WCF RIA Services V1.0 SP1 - like I'd know where to get that even if I knew what it was. One time, okay; I wasn't going to repeat this for who-knows-how-many files. So the real fix is: download the whole VS2010 SP1 ISO, mount it or extract it using your favorite utility, and point SP1 setup at that folder whenever prompted. Ugh. Again, what an absolute mess - and yes, yet another reboot. And for whatever reason, the re-application of SP1 took longer than the whole Denali install, including the time to take screen shots of every single dialog!

And I still have the same issue when launch a new query. *sigh*

(This only happened on the machine where I left CTP1 installed - because I wanted to easily compare DMVs and other things. I guess that plan is a bust.)

For some information about installing Books Online locally, in case I led you to believe that selecting the box above really installed Books Online, see this blog post from Geoff Hiten (@SQLCraftsman):

http://weblogs.sqlteam.com/geoffh/archive/2011/07/12/the-first-thing-you-will-hate-about-sql-denalihellip.aspx

Stay tuned for more posts about other tools (e.g. Juneau), changes to Books Online, and CTP3 engine features as I discover them.