Any SQL Server 2008 Database Change Management (MIgrations) Tools Available? - sql-server-2008

We were running Tarantino in a Nant build script but we're getting some new hardware and using the opportunity to upgrade to SQL Server 2008. Unfortunately Tarantino won't work with SQL 2K8 so I'm looking for an alternative.
Any ideas?

Migrator.net is the tool I use with SQL 2008. It also has nant script capability. I suggest using the trunk version, rather than the 0.7 release as it's had some good, as yet unreleased changes.
This roundup has other options. And there are few other similar questions here.

There are quite a few really good tools - some require adoption of a database change management process (like DBGhost), while others are less restrictive, but require more work (and efforts) on your side, e.g. Red-Gate's SQL Packager, which allows you to package your database creation and change scripts into .NET projects and/or stand-alone EXE files.

I believe Tarantino has been fixed now to work with SQL2008 as of March 2009
http://code.google.com/p/tarantino/source/list

Try the latest version of Tarantino from SVN, it works with SQL Server 2008.
Unfortunately, they have an outdated release published in Downloads section.

You may want to have a look at RoundhousE as well.

Related

Issues installing Umbraco on SQL Server 2008

I am having lots of problems install Umbraco on SQL Server 2008 are there know compatibility issues?
Also are there any good reasons not to use SQL Server CE 4?
What version of Umbraco? V5.x will only run on SQL 2008 out of the box. Umbraco 4.7 will definitely run just fine on SQL2008.
There is no reason you can't use SQLCE for development, but I wouldn't recommend it.
For production - the performance is just not good enough (though I suppose with a low traffic site it might work). With the much more powerful SQL Express also available for free, there is very little reason not to use it from the get-go, and it would alleviate the SQLCE->SQL Express upgrade headaches you may encounter down the road.

Create Database in SQL Server 2012, Script and Use in 2008?

If I create a database using 2012 and work and add that info to it, if I were to script the database after, would I be able to run the script in 2008 and have everything work A.O.K?
If you are using SQL Management Studio, you can right-click on the database name, then select Tasks → Generate Scripts.
Here you will be able to create scripts to script out the Schema, Data, or both Schema and Data, and if you click the Advanced button, you can specify which version of SQL Server you'd like to target.
So, simply choose SQL 2008 as the destination server and you should be good to go!
A script? Yes. Well, let me rephrase: it depends. As long as your objects don't use any 2012-specific features, you will be able to script out the schema using Management Studio or a variety of 3rd party tools (I blogged about some options here). Many of the tools also offer options (or companion tools) to also script the data.
The problem is there isn't a very easy way in SQL Server 2012 to identify all of the places where you might be using 2012-specific features. For example, I don't know of a tool that will inspect your database and point out that you are using the FORMAT() function, which is not available in SQL Server 2008 or 2008 R2.
Other means of copying the database over - backup/restore, attach/detach, mirroring/log shipping etc. will not work. You can go up (from 2005, 2008 or 2008 R2) to 2012, but you can't go backwards.
So in general I agree with John. Much safer to develop on a version <= deployment version. Why would you want to develop on 2012 to deploy to 2008? Seems quite risky to me.
If you have very large amounts of data to move (gigabytes) then the TSQL scripts that the SQL Management Studio will generate for you could give you problems because of the sheer size. A better alternative would be to use BCP (Bulk Copy Program). The downside is that this is a command line utility and requires more work than just using the wizard.
As luck would have it somebody has written something which looks remarkably like the wizard only using BCP. It is the SQL Database Migration Wizard and is freely available on Codeplex - http://sqlazuremw.codeplex.com/releases/view/32334. Originally intended as a database migration tool between SQL Server and Azure you can just as easily use it between SQL Server and SQL Server. The key is to go into the advanced options (similar to the Management Studio wizard) and pick SQL Server. Later when you are prompted for the target system choose your 2008 installation.
I had no 2012 specific artefacts in my database and it worked very smoothly for me.

What to know for upgrading from Reporting Services 2000 to SSRS 2008

Not that it's a prerequisite for commenting here, but I'd like to pick the brain of someone that's taken their Reporting Services platform from 2000 to 2008 (skipping right over 2005).
The architecture between 2000 and 2005 (so thus between 2000 and 2008 also) changed significantly it seems, so I'd like to know what needs to be done (before,during,after) the process of taking my rs2000 install (installed on a web server running IIS 5, connecting to a remote sql server 2000 box that hosts the ReportServer/ReportServerTempDB databases) and converting it to SQL208 - where, from the looks of it, is hosted in some sort of it's own native hosting engine, no IIS needed (is that right?).
I've used this tool before, but only for moving stuff between 2 rs2000 databases. I'm curious if it works between 2000 and 2008. I've also been reading on TechNet and MSDN about some kind of "upgrade advisor" and "upgrade wizard" - but I remember what the VB6 to VB.NET Wizard was like, so I'm a little skeptical of a wizard that proclaims to help migrate stuff between 2 architecturally different versions of a product.
Disclaimer: I am not a Reporting Services (or SQL Server) admin. Just the guy on the team most familiar with installing/supporting the tool, so I'm stuck being responsible for this migration too - though I'm a veteran developer, not totally clueless.
Be aware, there is no anonymous mode in SRS 2008, you should use Active Directory / Kerberos / Windows authentication or use your own authentication module.
In SRS2008 you've got feature like Tablix/Matrix which are really usefull, maybe you can make some optimizations into your old reports.

is it safe to install mySQL on windows server 2003 when MS SQL 2005 express already exists?

[edit]
I should note that I need to do this on a live production server. The MS SQL Server is already attached to our website and supports a 3rd party ERP package. I want to set up a separate database that I can code against for some auxiliary pages and internal-use apps) which will be completely independent (mostly for security, but also because I prefer mySQL) from the ERP solution.
[end edit]
The MS SQL 2005 express db is already installed and in use, so I don't want to hose it.
Will this create problems, or have you done it successfully?
Aside from performance issues, assuming they're both continuously used, there shouldn't be a problem.
For a development machine this is safe to do. The two database servers listen on different ports, so there is no problem of running both at the same time.
I wouldn't recommend it though for a production system.
Like Assaf said, the only thing you should worry about are possible performance issues with both database services getting run at the same time. Other than that you should have no worries concerning the integrity of the two. They are completely separate and should not have any sort of conflicts.

Why is SQL Server 2008 Management Studio Intellisense not working?

I'm being driven to insanity trying to figure out why Intellisense just fails to work at all. The server I'm using is local and is 2008, the database is set to 2008 compatibility, Intellisense is on in every menu I can find, and yet no member list will pop up even with a CTRL-J.
Has anyone experienced something like this and found a way to fix it? I really can't bring myself to start work unless I have Intellisense working.
I understand this post is old but if anybody is still searching and has not found a solution to the intellisense issue even after re-installing, applying the cumulative updates, or other methods, then I hope I may be of assistance.
I have Applied SQL 2008 R2 Service Pack 1 which you can download here
http://www.microsoft.com/download/en/details.aspx?id=26727
32 Bit:
SQLServer2008R2SP1-KB2528583-x86-ENU.exe
64 Bit:
SQLServer2008R2SP1-KB2528583-x64-ENU.exe
I have applied this SP1 and now my intellisense works again.
Visual Studio 2010 SP1 breaks SSMS 2008 R2's IntelliSense. There is a connect about that, and fortunately there is also a fix for that.
(In short, you will need to install Cumulative Update package 7 for SQL Server 2008 R2 by requesting
SQLServer2008R2_RTM_CU7_2507770_10_50_1777_x86or
SQLServer2008R2_RTM_CU7_2507770_10_50_1777_x64
from this hotfix request page.)
EDIT: As #Paul Lemke noted, one might need to get the latest CU package. This blog contains the SQL server releases. (As of this writing, the latest is CU14)
For SQL Server 2008 R2, installing Cumulative Update 7 will fix the problem. The file you need is
SQLServer2008R2_RTM_CU7_2507770_10_50_1777_x86
or
SQLServer2008R2_RTM_CU7_2507770_10_50_1777_x64
I also had to uninstall and re-install SQL Server 2008 first (which didn't fix it, but the CU did).
No need to reinstall.
Click on the setup file. Then go to maintenance and click on Repair. This should correct the intellisense problem.
I just the had same problem. I figured out that Intellisense stopped working after I took some databases offline and doing an Intellisense refresh (Ctrl-Shift-R). I brought the offline databases back online, did a refresh (Ctl-Shft-R) again and VOILA! Intellisense is working again.
What a crappy design. Maybe the population of Intellisense's lists chokes when a database exists but is offline. Thanks Microsoft.
I don't want to suggest a product out of turn, since getting Intellisense running is probably the best option, but I've struggled with the accursed no intellisense on Management Studio for months. Reinstallation, CU7 update, refreshing caches, sacrificing chickens to pagan gods; nothing has helped.
I was about to pay for RedGate's SqlPrompt (pretty damned pricey, $195 US), when I found SqlComplete.
http://www.devart.com/dbforge/sql/sqlcomplete/?gclid=CN2xs_Lw7akCFcYZHAodpicXXw
There is a free version which does the basics, and the full version is only $50!
I'm a database architect, and while I can remember the commands, auto complete saves me heaps of time. If you're stuck and can't get Intellisense to work, try SqlComplete. It saved me hours of hassle.
I recently wrote a tip about troubleshooting IntelliSense. The title says SQL Server 2012 but most of the techniques can be applied to earlier versions of Management Studio as well.
Troubleshooting IntelliSense in SQL Server Management Studio
I ended up fixing it by reinstalling SQL Server 2008. This wasn't at all optimal, but if someone comes across a similar problem be sure to know this route will probably work.
I tried all the fixes - taking databases offline and then bringing them online, installed Cumulative update 10, repaired SQL Server Installation, refreshed local cache, made changes to the required settings on SQL Server Management Studio but everything was in vain. Finally installing the correct service pack (SP1) did the trick for me !
Follow the link below, and download SQLServer2008R2SP1-KB2528583-x86-ENU.exe (or the x64 file for a x64 bit instance of SQL Server)
http://www.microsoft.com/download/en/details.aspx?id=26727
Finally i have Intellisense enabled !
I'm posting this here as I am sure more people will be comeing across this issue. I installed Security Update for microsoft Visual Studio 2010 Service Pack 1 (KB2565057) and lost Intellisense in SQL Server Management studio 2008 (not R2).
An uninstall of the SP restored Intellisense .. Don't you just love Microsoft????
After finding this thread, I discovered that my Intellisense only broke after taking a database offline, and any offline database(s) on the instance would kill Intellisense.
In this thread, explaining that in order to restore Intellisense, you must
take the necessary databases offline, then
restart the server instance, and finally
refresh the Intellisense cache.
This procedure has worked for me and Intellisense is now working again.
I've had the same problem too. Searched everywhere online and can't find a solution. I did install Redgate's SQL Prompt which functions similarly to Intellisense, so maybe there was a conflict. I've since stopped the Prompt from running, but now no intellisense at all. Using SQL Server 2008 will SQLCMD mode off, no luck at all. This has happened before, a reinstall of SQL Server was the only thing that I could get to work.
Same problem, but just re-installing SQL Management Studio 2008 R2 Service Pack 1 worked for me. I left my DB engine alone. The DB engine is not the problem, just SQL Management Studio getting hosed by Visual Studio SP1.
Installers here...
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26727
I installed SQLManagementStudio_x86_ENU.exe (32 bit for my machine).
When trying the accepted answer, I was getting an installation error: A failure was detected for a previous installation, patch, or repair blah, blah, blah...
To fix this, in my registry, I changed all DWORD values to 1 in the following Keys: (As always be careful modifying the registry and create a backup of the key before changing anything)
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\100\ConfigurationState
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\ConfigurationState
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\ConfigurationState
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.SQLEXPRESS\ConfigurationState
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\ConfigurationState
See my full post about Fixing Intellisense issue in SSMS.
Here is the official word on this from MS.
http://support.microsoft.com/kb/2531482
Their solution is the same as above, install the SQL Server 2008 R2 updates with the version 10.50.1777.0.
http://support.microsoft.com/kb/2507770
I did all of the above and ultimately gave up. Then one last resort was a third part SQL Intellisense add-on I found SQL Complete Express by devArt.
It's Intellisense plus more. Intellisense is back and all is well.
Supports SSMS 2005 - 2012 also includes Visual Studio Add-In.
SQL Complete
For SQL Server 2008 R2, installing Cumulative Update 7 will fix the problem. The file you need is
SQLServer2008R2_RTM_CU7_2507770_10_50_1777_x86
or
SQLServer2008R2_RTM_CU7_2507770_10_50_1777_x64
I also had to uninstall and re-install SQL Server 2008 first (which didn't fix it, but the CU did).
this is Direct Link From MS that i was got it Hot Fix