Upgrade our CRM 2011 SQL server from 2008 R2 to SQL 2012

Can anyone please let me know what the steps involved are?
Thanks,
Red.

please see if this helps.
https://social.technet.microsoft.com/Forums/sqlserver/zh-CN/e614c52c-fbd7-4877-8e26-03d4d58f61ed/how-to-restore-sql-server-2008-r2-databases-on-sql-server-2012?forum=sqlsetupandupgrade
regards
Jithesh

Similar Messages

Blank filtered view after upgrade of CRM and SQL server

We have upgrade our CRM system to CRM 2015. We also upgraded our sql server to the latest version. We used a backup of the database on the old sql server to update the new database. All works fine except for custom reports in SSRS. It
seems that although the tables return the correct value, the filtered tables return null.
Christo Vermeulen

Have you tested this by querying the filtered views directly from SSMS? If so, be sure you are connecting to SQL using windows authentication. SQL authentication will always return null when querying filtered views.

My Bank demands me to upgrade my iMac 10.5.8 from 2008 to at least 10.6 or.7   Can I get it free? or where buy it, Apple store? 10.5.8 from 2008 to at least 10.6 or 10.7

My Bank demands me to upgrade my iMac 10.5.8 from 2008 to at least 10.6 or.7   Can I get it free? or where buy it, Apple store?

The bank knows the web browser the op is using is incompatible not the os. He could just switch web browsers to one the bank finds ok.
Safari is not the only browser that run on a mac.
Not sure why you responded to my post.
seventy one wrote:
The bank only knows the operating system is incompatible.   Safari will be supported if the OP upgrades per his original question.

Upgrading SQL Server from 2008 to 2012 doesn't respect existing install / instance paths

Basic Information : Running Microsoft Windows Server 2008 with MS SQL Server 2008 (version 10.0.5869), trying to upgrade to SQL Server 2012. Currently working in a cloned
VM of our production server (so I can try things and not worry about affecting our production system).
Current server setup:
C Drive: Operating System (About 7 GB of 50 GB free)
J Drive: Program Files (About 65 GB of 78 GB free)
F Drive: SQL Databases (About 120 GB of 195 GB free)
Issue: I am trying to do an upgrade of our existing MS SQL Server 2008 install. I am using the GUI method, and choosing "Upgrade from SQL Server, 2005, SQL Server
2008, or SQL Server 2008 R2" in the Setup GUI:
All the checks & rules run with no issues. When I get to the "Instance Configuration" screen in the setup GUI, it is not respecting where my SQL Server instance is already installed (which is on the J drive). Instead it wants to install EVERYTHING
(including Instance Directory, which should be on the F drive, and the install folder, which should be on the J drive) on the C drive under C:\Program Files\ and there is no option in the GUI to change that, as it's grayed out.
I tried using a Configuration File to do the upgrade, but when I tried to specify the specific paths, it says those variables are not allowed to be used in an upgrade. If I allow the install to go through, it seems to install fine, but only leaves me with about
1.5 GB free on the OS drive (Drive C) and all of SQL Server is now installed on Drive C, which is not what I want or need.
Looking in the Registry Editor, I can see that under HKLM\SOFTWARE\Microsoft\Microsoft
SQL Server\MSQL11.MSSQLSERVER\ that the SqlProgramDir key
has changed from "F:\" to "C:\Program Files\Microsoft SQL Server\" and that the SQLPath and SQLDataRoot have
changed from "F:\MSSQL10.MSSQLSERVER\MSSQL" to "C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL". SQLBinRoot has
also been changed "F:\MSSQL10.MSSQLSERVER\MSSQL\Binn" to "C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn".
It doesn't seem to want to follow where the existing Install and Instance Directories are. Am I missing something here? I've done a decent amount of research, but can't find anything that talks about this. So I'm at a loss as to what to do from here.

I haven't touched the registry. Here is the ConfigurationFile.ini from the original install (I've scrubbed sensitive info out of it) showing the paths:
;SQLSERVER2008 Configuration File
[SQLSERVER2008]
; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will reflect the instance ID of the SQL Server instance.
INSTANCEID="MSSQLSERVER"
; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.
ACTION="Install"
; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, and Tools. The SQL feature will install the database engine, replication, and full-text. The Tools feature will install Management Tools, Books online, Business Intelligence Development Studio, and other shared components.
FEATURES=SQLENGINE,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
; Displays the command line parameters usage
HELP="False"
; Specifies that the detailed Setup log should be piped to the console.
INDICATEPROGRESS="False"
; Setup will not display any user interface.
QUIET="False"
; Setup will display progress only without any user interaction.
QUIETSIMPLE="False"
; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system.
X86="False"
; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature.
ERRORREPORTING="False"
; Specify the root installation directory for native shared components.
INSTALLSHAREDDIR="J:\Program Files\Microsoft SQL Server"
; Specify the root installation directory for the WOW64 shared components.
INSTALLSHAREDWOWDIR="J:\Program Files (x86)\Microsoft SQL Server"
; Specify the installation directory.
INSTANCEDIR="F:"
; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature.
SQMREPORTING="False"
; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services (RS).
INSTANCENAME="MSSQLSERVER"
; Agent account name
AGTSVCACCOUNT="NT AUTHORITY\SYSTEM"
; Auto-start service after installation.
AGTSVCSTARTUPTYPE="Automatic"
; Startup type for Integration Services.
ISSVCSTARTUPTYPE="Automatic"
; Account for Integration Services: Domain\User or system account.
ISSVCACCOUNT="NT AUTHORITY\SYSTEM"
; The name of the account that the Analysis Services service runs under.
ASSVCACCOUNT="NT AUTHORITY\SYSTEM"
; Controls the service startup type setting after the service has been created.
ASSVCSTARTUPTYPE="Automatic"
; The collation to be used by Analysis Services.
ASCOLLATION="Latin1_General_CI_AS"
; The location for the Analysis Services data files.
ASDATADIR="F:\MSAS10.MSSQLSERVER\OLAP\Data"
; The location for the Analysis Services log files.
ASLOGDIR="F:\MSAS10.MSSQLSERVER\OLAP\Log"
; The location for the Analysis Services backup files.
ASBACKUPDIR="F:\MSAS10.MSSQLSERVER\OLAP\Backup"
; The location for the Analysis Services temporary files.
ASTEMPDIR="F:\MSAS10.MSSQLSERVER\OLAP\Temp"
; The location for the Analysis Services configuration files.
ASCONFIGDIR="F:\MSAS10.MSSQLSERVER\OLAP\Config"
; Specifies whether or not the MSOLAP provider is allowed to run in process.
ASPROVIDERMSOLAP="1"
; Specifies the list of administrator accounts that need to be provisioned.
ASSYSADMINACCOUNTS=""
; Startup type for the SQL Server service.
SQLSVCSTARTUPTYPE="Automatic"
; Level to enable FILESTREAM feature at (0, 1, 2 or 3).
FILESTREAMLEVEL="0"
; Set to "1" to enable RANU for SQL Server Express.
ENABLERANU="False"
; Specifies a Windows collation or an SQL collation to use for the Database Engine.
SQLCOLLATION="SQL_Latin1_General_CP1_CI_AS"
; Account for SQL Server service: Domain\User or system account.
SQLSVCACCOUNT="NT AUTHORITY\SYSTEM"
; Windows account(s) to provision as SQL Server system administrators.
SQLSYSADMINACCOUNTS=""
; The default is Windows Authentication. Use "SQL" for Mixed Mode Authentication.
SECURITYMODE="SQL"
; Provision current user as a Database Engine system administrator for SQL Server 2008 Express.
ADDCURRENTUSERASSQLADMIN="False"
; Specify 0 to disable or 1 to enable the TCP/IP protocol.
TCPENABLED="1"
; Specify 0 to disable or 1 to enable the Named Pipes protocol.
NPENABLED="0"
; Startup type for Browser Service.
BROWSERSVCSTARTUPTYPE="Disabled"
; Specifies which account the report server NT service should execute under. When omitted or when the value is empty string, the default built-in account for the current operating system.
; The username part of RSSVCACCOUNT is a maximum of 20 characters long and
; The domain part of RSSVCACCOUNT is a maximum of 254 characters long.
RSSVCACCOUNT="NT AUTHORITY\SYSTEM"
; Specifies how the startup mode of the report server NT service. When
; Manual - Service startup is manual mode (default).
; Automatic - Service startup is automatic mode.
; Disabled - Service is disabled
RSSVCSTARTUPTYPE="Automatic"
; Specifies which mode report server is installed in.
; Default value: “FilesOnly”
RSINSTALLMODE="DefaultNativeMode"

Photoshop CS6 can't save to server after upgrading to Mac OS Yosemite Server from Mac Lion Server

We recently upgraded our server from a Mac Pro 2008 with OS X Lion Server to a Mac Mini 2014 with LaCie 20TB 5Big Thunderbolt 2 RAID drive. Everything is working fine with the exception of Photoshop. It does it intermittently but once it happens it will continue to do so. We get message like "Can't save to disk because of disk error" and "Can't save file because of program error" . Sometime we are able to do a "save as" and save over it. Most of the time we have to "save as" with a different file name and then rename and recopy the file. We have check permission on all the file as well as the server HD has ignore ownership checked. Again only three things changed. 1) Sever hardware change from Mac Pro to Mac Mini. 2) Server software upgraded from 10.7 Lion to 10.10 Yosemite(both have the latest update). 3) Drive when from internal on Mac Pro to External Thunderbolt 2 LaCie drive. We have no problem with Illustrator or Indesign. Only Photoshop. Anyone with any suggestion is greatly appreciated.

Unfortunately you seem to be using Photoshop in a way that Adobe discourages, so you may not be getting a lot of helpful advice.
Networks, removable media | Photoshop | CS4 and later

Upgrade single instance from 2008 R2 SP2 to 2012 SP1

We have a central SQL 2008 R2 server that has multiple named instances, one each for System Center Configuration Manager 2012 R2, System Center Operations Manager 2012 R2, Virtual Machine Manager 2012 R2, App Controller and one for CRM 2013 SP1.
Can we easily upgrade just the CRM instance to 2012 SP1? Any suggestions how to approach this.

I feel it's a risk taking process because there is lot of dependency and complexity in your current setup. Some of the shared components will also get upgraded and rollback process is going to be harder enough to bring back the old setup. I would not
recommend you to go with In-place upgrade.
You can try side by side Upgrade strategy:- Move the CRM instance to a different instance.
Upgrading CRM is not straight forward. It has dependency and you require to modify few registry keys and requires lot of changes to be done to the configuration at the app Server.
I'll recommend you to go through the support and upgrade document of CRM.
--Prashanth

How do I migrate a FAX server from 2008 R2 to 2012 R2

Hi- I have two DCs (one 2008 R2, one 2012 R2) I'm going to build a new DC with 2012 R2 and remove the 2008 R2. This server is hosting FAX services. How do I move it to the new server? Can only find articles talking about SBS and using a migration wizard...
You should never, never doubt what nobody is sure about. -Willy Wonka

There are no tools included in Windows for migrating the fax service from one machine to another.
Alan Morris formerly with Windows Printing Team

My wife and I both upgraded our cell phones will att from iPhone 5 to iPhone 6. since then everything has worked great except for making phone calls to other cell phones. the phone acts like it connects and the call timer starts but there is no sou

unable make phone call with brand new iPhone 6

Try a reset, hold down the home/sleep button together until you see the apple logo and then release then wait for the phone to boot back up.
then try again.
Get help with hardware features on your iPhone, iPad, and iPod touch - Apple Support
If the above doesn't work, then contact AT&T.

Full-text search not available after upgrade from SQL 2008 R2 Std to SQL 2012 Std

We upgraded our production SQL Server from 2008 R2 Std to 2012 Std last week, and the installation logs show everything was successful, but now we are unable to do any searches against our full-text indexes. The resulting error is as follows:
"Full-Text Search is not installed, or a full-text component cannot be loaded."
When executing the query "SELECT FULLTEXTSERVICEPROPERTY('ISFULLTEXTINSTALLED')", the result is "0". The "Full-Text Daemon Launcher service is also running. When running installation again to add the feature, it shows
"Full-Text and Semantic Extractions for Search" as being installed and unavailable for selection in the list of features to add. As a side note, we did the same upgrade in our identical QA environment before production and everything was successful
and full-text searches are working correctly. We have run the "Repair" routine in the SQL Installation Center and it did not correct the problem.
The full-text catalogs still appear when browsing through the GUI in SSMS or querying sys.fulltext_indexes and sys.fulltext_index_columns. It is not possible to view the properties of the catalog in SSMS, though, as the GUI throws an error and an empty
dialog box is shown. Any other thoughts?
Thanks,
AJ

I have no idea what is going, but assuming that it is a little pressing to get this fix, I think the best path in this case is to open a case with Microsoft.
Erland Sommarskog, SQL Server MVP, [email protected]

Issue with SSIS Custom Components - 64 bit SQL 2012

Hello All,
Our SSIS packages built on SQL 2008 R2 make use of some custom components. These custom components are installed as part of an MSI. The dll's are copied over to the Windows/assemble [GAC Folder] and also to the Program Files(x86)/SQL Server/110/DTS/* folder.
The installation does not copy the dll's to the 64 bit program files folder.
X:\Program Files\Microsoft SQL Server\110\DTS
These packages are executed via SQL Agent jobs on a 64 bit SQL server and there does not seem be any issue.
Now we are upgrading our servers to SQL 2012 and we have a new installer for the custom components as well. The new custom components use .NET Framework 4.0 and when installed the dll files get copied over to the Ms.NET 32 bit runtime GAC folder and also
to the SQL Server DTS Folder in x86. The upgraded packages work only when we set the runtime mode to 32 bit. The packages successfully executes within the 32 bit dtexec utility, but when we try to run the same package using a 64 bit dtexec utility the
process errors out with a component failed to load message. The package moves data between two SQL Server instances.
The custom components have always been built for 32 bit runtime. I can run a older package through the dtexec utility (from the 64 bit folder in program files) and it does work without any issues. After the upgrade the package will only execute on
a 32 bit utility. can someone help me understand this issue?
Regards, Dinesh

Thank you Arthur.
i think we got the answer as well, as the .NET framework 3.0 installer copied the files over to the C:\windows assembly the dtexec utility [32 bit/64 bit] was able to load the components.
Now with the new installer the files are copied to specific runtime gac folders as Arthur has mentioned. The 64 bit utility does not find the dlls in the GAC whereas the 32 bit version will find them.
Regards, Dinesh

SharePoint 2013 Server OS upgrade from Windows 2008 R2 to Windows 2012 R2

Is it possible to have SharePoint 2013 farm to have mixed version of OS (Windows 2008 R2 and Windows 2012 R2).
We have a request to upgrade our farm servers from WIN 2008 R2 to Win 2012 R2. We have 5 servers in farm -
2 App servers - running with Central Admin, Service Applications, User Profile
3 Web Front End Servers- running web application, search and workflow manager
the database layer is separate on sql 2012 R2
We want to upgrade OS from windows 2008 R2 to windows 2012 R2 and SQL to SQL 2014.
What will be right approach to do OS upgrade in above scenario to minimize the impact of downtime.
May be add windows 2012 based servers in farm one by one and replace the windows 2008 R2 based servers from server.
Regards,
Kunal Abrol

Its possible, but I wouldn't recommend it. The problem is that you can only install SharePoint 20103 on Windows Server 2012 r2 using the slipstreamed SP1 version. I assume that you used the regular version to install on you Server 2008 r2 versions.
Even if you upgrade those servers to SP1 there are some minor differences in the builds between slipstreamed SP1 and upgraded SP1. So although it will work it isn't recommended.
Also, you should be aware the upgrade of inplace SharePoint servers running Windows 2008 r2 to Windows 2012 r2 is not supported.
To upgrade to server 2012 you'll need to add 2012 servers to your environment using the slipstreamed version os SharePoint and then remove the old server 2008 r2 servers as soon as possible. For the period of the upgrade you should be able to get away
with running the farm in a mixed state.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Upgrade Sharepoint 2010 SQL Reporting Services from 2008 R2 to 2014

I'm about to do the upgrade of SharePoint 2010 Reporting Services from 2008 R2 to 2014. The instructions say it can be done "in-place" with no downtime. I've seen this article:
http://whitepages.unlimitedviz.com/2012/03/upgrading-sql-server-reporting-services-to-2012-in-sharepoint-integrated-mode/
It covers 2012 so I assume the same holds true for 2014.
I'd like to get the low down from anyone who has actually performed the upgrade of SSRS from 2008 R2 to 2014. Anyone done this upgrade? Any issues?
David Jenkins

So far I would have to say that the upgrade can be done "in-place" but there is a "DOWNTIME".
This article has helped a lot:
http://blogs.catapultsystems.com/tlingenfelder/archive/2012/07/10/upgrading-sql-server-reporting-services-2008-r2-to-sql-server-reporting-services-2012-in-sharepoint.aspx
In the article it tells you about a bug in the SQL Upgrade process where
the Domain account you use will not work. When you type in the password it fails. On top of that it will lock the Domain account because of a bad password! There is probably something wrong with the authentication process and it garbles the password.
Anyway, you end up having to change the account to the "Network Service" account before you can do the upgrade. This means the services get restarted which means???
DOWN TIME! He goes over other errors. I haven't reviewed these issues yet.
The other thing I learned is that everything needs to be SQL Server 2008 R2 SP2 in order to upgrade. You don't find this out until almost the last step in the installation process.
Now I have to wait until next week to actually do the upgrade because I have to schedule an SP2 install. :(
David Jenkins

I did an Unsupported InPlace OS Upgrade from 2008-R2 to 2012-R2

Well, I misunderstood what was supported and upgraded the OS on a SCCM 2012-R2 server from 2008-R2 to 2012-R2. (The one and only SCCM-server in the site)
All seems to work well, my concern now is what can I expect of future problems? Should I do the backup-install-restore procedure now to be sure or let it run until... "maybe something" happens?
Thanks.

"not supported" just means that MS did not test that scenario (and it does not automatically mean that it does not work).
I've done such an OS upgrade in my lab and were running into some smaller issues (MP/DP/SUP = the roles that require IIS) and were able to fix them by removing and re-adding those roles but YMMV.
The supported way would be: recover from backup. But you can also have a close look at all roles and see if they are still working.
Torsten Meringer | http://www.mssccmfaq.de

Migrating from CRM 2011 on-premises to CRM Online (Attachments)

I need to move our CRM 2011 on-premises to CRM Online. I got my customizations into CRM Online. My next task is to get the data there. Some are easy but I am not sure how to handle
1) Interconnected records. For instance a case is connected to an account, emails, products, etc. I figured I just will
    a) export and then import leads first as accounts are connected to leads
    b) export and then import emails and products
    c) export and then import cases
However, how to I assure that all these records are still having the same connections (case 100 connected to email 501 and 502, etc)
2) Some records have files associated with them. The biggest one is emails that have attachments. How can I get these emails into CRM Online including attachments?

Thanks. Scribe is way too expensive. SSIS might be an option I need to explore more. Any opinion about Microsoft Dynamics CRM Instance Adapter? I am reading some articles about it and consider giving it a try. However, I can't even find the download despite
a lot of searches.
https://community.dynamics.com/crm/b/magnetismsolutionscrmblog/archive/2013/03/12/microsoft-dynamics-crm-2011-instance-adapter-part-1-downloads.aspx

Upgrade from windows 2008 R2 to windows 2012 and Quorum

Dear Sir.
I am going to upgrade hyper-v cluster of 4 nodes 2008 r2 to windows 2012 hyper-v cluster.
i am going to evict tow node and build new cluster.
should I configure new quorum for new cluster or can i use the the quorum from old system ?
thanks

Hi,
Base on my experience, you need create a new cluster when you choose migrate the cluster, so you need the new witness disk.
The
related article:
Best practices for migration of cluster windows 2008 R2 / 2012 - As melhores Praticas para migrar um Cluster de Windows 2008 para Windows 2012
http://blogs.technet.com/b/hugofe/archive/2012/12/06/best-practices-for-migration-of-cluster-windows-2008-r2-2012-as-melhores-praticas-para-migrar-um-cluster-de-windows-2008-para-windows-2012.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Upgrade our CRM 2011 SQL server from 2008 R2 to SQL 2012

Similar Messages

Maybe you are looking for