January 21, 2016 at 2:59 pm
Hi,
We have Server A which has SQL Running on it. Server B where the application is running.
The SQL server is currently 2005 standard edition. We are planning to upgrade to SQL Server 2008r2.
We don't have either SSRS or SSAS. We have only Integration services running. But other than Maintenance plans, I didn't see any other SSIS packages under the file system or msdb.
What are the best approach to start the process.
We have some SQL Logins. No one knows the password for them. How to get the passwords?
There is no QA env available to test migration first.
They do have system clone so I have to the in place migration.
January 21, 2016 at 10:16 pm
I ran the upgrade advisor
I see the red cross mark under the importance for SQL Server. It is showing that Full-Text search has changed in sql server 2008 under the description. When to fix (Before)
Upgrade Advisor determined that full-text search is currently installed
Any advice how to fix this!
How to identify is there any deprecated features are used either in sp or views..
January 22, 2016 at 3:40 am
ramana3327 (1/21/2016)
What are the best approach to start the process.
In my opinion you shouldn't be doing an in-place upgrade. It almost always turn out to be ugly. Do a side-by-side upgrade if possible.
Script out everything that has to be scripted and apply it to the destination machine.
TEST the applications thoroughly!
We have some SQL Logins. No one knows the password for them. How to get the passwords?
You don't need to know the passwords: you have the password hashes. Use the stored procedure sp_help_revlogin that you can find here: https://support.microsoft.com/en-us/kb/918992
There is no QA env available to test migration first.
They do have system clone so I have to the in place migration.
This is really bad. No tests means no guarantee it will work. Make this clear with your boss and let him/her decide if this is an acceptable risk.
I see the red cross mark under the importance for SQL Server. It is showing that Full-Text search has changed in sql server 2008 under the description. When to fix (Before)
Upgrade Advisor determined that full-text search is currently installed
Installed does not mean used. Try to determine if the application is using it. The developers or the vendor should know that.
How to identify is there any deprecated features are used either in sp or views..
The upgrade advisor should have reported that.
-- Gianluca Sartori
January 24, 2016 at 10:54 pm
Thank you.
We have only option in place upgrade. We have only 1db. I don't need to worry about the SQL Logins (Due to in place).
In case if there is an issue, is it possible to revert back using the system (Includes resource DB) & user db backups?
Steps in order to do:
1) Stop the application
2) Backup all databases (Include resource DB)
3) Stop the SQL Server Service
4) Run the setup file
5) Choose the upgrade from 2005
6) Restart the engine
This is in place so we don't need to change compatability level and check for orphan users
Is there anything else am I missing?
The server is Windows 2008r2 64-bit operating system
Do I need to install any .net framework before? (Looks 4 is installed already)
For me it looks they enabled the full text engine but didn't find any full text indexes so far
If we have full text indexes enabled in the db what is the best option to do migration (Rebuilt or reset)?
Where this option will populate (In which step)?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply