I have a SQL Server CE database I am developing with and would like to downgrade the version so that 2005 Management Studio will open it. Currently, I have to use VS 2010 to open it, but it is a real pain to use that way.
I know I could install the 2008 version of SSMS, but the machine I use has serious problems with all installs. There is something messed up and I don't want to reimage the machine. So 2008 is not an option.
The only way I have found is to get a tool to convert the tables into raw sql. Then use this sql against a empty DB created in a earlier CE version.
Related
I get this error in Management Studio. I don't know what the reason is. I tried repairing SQL Server, but still the issue is not resolved. I read a lot of articles about this, but I don't know how to do this with registry keys.
How to solve permissions issue?
As James suggested, it's time to use a later version of SQL Server Management Studio.
If you can run the latest (version 18.4), that would be good. It still has support for SQL Server 2008.
However, it has more recent dependencies. If you look at the list of dependencies, you might decide that an earlier version would be better on the older system. SSMS 18.4 was based on a more recent Visual Studio shell. SSMS v17.9.1 is also available for download still, works fine with SQL Server 2008, and uses the older shell, so you might have less friction when trying to install it.
I have database created on SQL SERVER 2008. I want to upgrade it to SQL SERVER 2016. what is the best way to upgrade the whole database?
Thanks in advance.
Migration can be done many ways from 2008 to 2016. In-house upgrade, backup restore, etc. Different approaches are explained here:
https://learn.microsoft.com/en-us/sql/database-engine/install-windows/upgrade-database-engine
But simple backup/restore approach is the always better in my practical understanding. Also It has links for SSIS/SSAS/SSRS if required plan for those. Each has different approaches...
Major things to consider are how to remove deprecated features and how to make use of new features:
Deprecated features:
2012:
https://technet.microsoft.com/en-us/library/ms143729(v=sql.110).aspx
2014:
https://msdn.microsoft.com/en-us/library/ms144262(v=sql.120)
2016:
https://learn.microsoft.com/en-us/sql/database-engine/discontinued-database-engine-functionality-in-sql-server-2016
You can use new AMR tool to identify what tables you can use for in-memory also you can do analysis of columnstore indexes etc using below:
https://blogs.technet.microsoft.com/dataplatforminsider/2013/09/17/new-amr-tool-simplifying-the-migration-to-in-memory-oltp/
I had big problems upgrading from 2008 to 20014 as it complained about 2008 SP2 missing, but there where additional messages about missing instance ID's or nothing needed to be installed.
The upgrade from 2008 to 2012 was a better move as the 2012 is probaly better designed to deal with a previous release.
Once 2012 was installed I moved to 2014 with no problem and did not have to care about attached databases. It just upgraded.
I had to use the "SQL Server Configuration Manager" to enable Named Pipes or TCP/IP connection in the "SQL Server Network Configuration" section, and enable the new SQL service .exe in the windows firewall.
To add it to the firewall the service exe "sqlsrvr.exe" was identified using the Windows task manager and using "properties" optaning the path to the .exe.
The installation makes you nervous but once installed you know SQL Server is one of the few Microsft products that does not bother you. It just works.
Instead of downloading missing servicepacks manually it was easier to run Windows update and have it suggest SQL server sevicepacks. Winows update actually helped before migrating to the next version.
Here is a nice chart of sql server editions with links to downloads:
Microsoft SQL Server Version List
I am running SQL Server Management Studio 2008 on Windows 7. I am unable to open a SQL Server 2000 DTS package from SQL Server Management Studio 2008. I have tried going through all the steps that I have found online as far as installing the SQL Server 2005 Backwards Compatibility and the DTS Design Components, but none of it works. I have even gone through the steps to replace .dlls in the installation directory from some of the posts that I have found.
Is this actually even possible to open a SQL Server 2000 DTS package from within SQL Server 2008 Management Studio on Windows 7?
No, to the best of my knowledge, what you explicitly describe is not possible (my SSMS crashes when I try).
However, if you are looking to migrate the package from DTS to SSIS, you need to run the DTS Migration Wizard. I recommend doing this from BIDS:
Start BIDS 2008
Create an Integration Services Project
Right-click SSIS Packages and choose "Migrate DTS 2000 Package"
Follow Wizard instructions
You can access the wizard through SSMS2008, but ultimately I found it much easier to start in BIDS, and then import the finished product into SQL using SSMS2008.
Was looking for the same thing and found this:
http://blogs.msdn.com/b/ramoji/archive/2008/10/16/how-to-open-dts-packages-in-sql-server-2008.aspx
Never got chance to try it unfortunately as I've been told just to use one of the older machines we have... Hopefully it will help someone though.
I have vs2010 ultimate installed and sql server 2008 developer. I created a package using the openAuth Extension from the online gallery and can not find an option to add a sql server CE db to my project. I tried changing the target framework to 4.0 and still nothing.
I see a type that says SQL Server Database, but I believed that was for a full blown db to attach to sql server.
Where is compact?
You first need to add it in the Server explorer even if it's new.
Here is the link on how to do it.
link text
If you mean to this:
http://i.imgur.com/NcmH1.png
I fix my problem running SSCEVSTools-esn.msi from the vs2010 dvd.
D:\Visual Studio 2010\WCU\SSCE
I always seem to battle with this so on my new Windows 7 dev PC build, I thought I'd try and get it right!
Do you install VS 2008 first and then SQL Server 2005 developer or the other way around? And for either way, are there any special options/settings that have to be enabled/disabled?
I've just take an Acronis image of my PC, configured IIS for use with SQL Server 2005 (see below) and proceed to install SQL Server 2005 developer. It's warned about SQL Server 2005 needing SP3 (no problem) but it's also warned about VS 2005 not been compatible. Can I ignore this and go ahead and install VS 2008?
Cheers, Rob.
PS. The page to configure IIS features for use with SQL Server 2005 is http://support.microsoft.com/default.aspx/kb/920201
I always install in the following order
IIS
Windows Installer
Sql Server
VS any version
whenever i tried to go the other way, i always faced a problem approx thrice i faced this problem. Usually some components becomes missing in other way