marrowyung
asked on
SQL server 2005 RTM standard edition x86 to SQL server 2012 standard edition X64
Dear all,
from migration point of view, is it possible to migration SQL server 2005 RTM standard edition x86 to SQL server 2012 standard edition X64?
We have SSIS 2005 package in the existing SQL server 2005 X86 RTM standard edition, it save as the SQL job! How to migrate them all ?
The migration thing can get ride of the x86 to X64 problem, right? this only take place in upgrade/in-place upgrade case, right?
from migration point of view, is it possible to migration SQL server 2005 RTM standard edition x86 to SQL server 2012 standard edition X64?
We have SSIS 2005 package in the existing SQL server 2005 X86 RTM standard edition, it save as the SQL job! How to migrate them all ?
The migration thing can get ride of the x86 to X64 problem, right? this only take place in upgrade/in-place upgrade case, right?
ASKER
first of all, tks for your reply.
"I have moved SQL 2005 Std 64Bit databases to SQL 2012 Std 64Bit."
I mean from SQL server 2005 std x86 to SQL server 2012 std 64 bits, architecture is diff.
"The process of restoring them converts them to 2012, they cannot be again connected to 2005."
you mean they cna't connect back to SQL server 2005, right?
"There could however been some incompatibilities any upgrade that may or may not be evident."
cna't see what it means but you have tried that alreayd, what is the issue ?
"The SSIS packages we moved to 2012 by first converting the Visual Studio Solution from 2005 to 2012. The Visual Studio has a wee wizard that does this conversion for you. It gives you a summary of the warnings errors and whatever. "
any step by step guide on this ? I need some resource !
"the SQL Agent and the proxies to run DTSExec, which is a bit of work also!!! A"
we need a SQL proxies? I never set it up before and even from some kind of web trainning of the web, the SSIS deployemnt don't need proxies, am I right ?
the most importnat thing here is the change from x86 to x64, it will have no problem on SSIS side?
how about SSAS and reporting service from SQL server 2005 X86 to SQL server 2012 X64 ?
"I have moved SQL 2005 Std 64Bit databases to SQL 2012 Std 64Bit."
I mean from SQL server 2005 std x86 to SQL server 2012 std 64 bits, architecture is diff.
"The process of restoring them converts them to 2012, they cannot be again connected to 2005."
you mean they cna't connect back to SQL server 2005, right?
"There could however been some incompatibilities any upgrade that may or may not be evident."
cna't see what it means but you have tried that alreayd, what is the issue ?
"The SSIS packages we moved to 2012 by first converting the Visual Studio Solution from 2005 to 2012. The Visual Studio has a wee wizard that does this conversion for you. It gives you a summary of the warnings errors and whatever. "
any step by step guide on this ? I need some resource !
"the SQL Agent and the proxies to run DTSExec, which is a bit of work also!!! A"
we need a SQL proxies? I never set it up before and even from some kind of web trainning of the web, the SSIS deployemnt don't need proxies, am I right ?
the most importnat thing here is the change from x86 to x64, it will have no problem on SSIS side?
how about SSAS and reporting service from SQL server 2005 X86 to SQL server 2012 X64 ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
"Some of the stored procedures and Quires will not work in SQL 2012 X64."
very hard to understand ! any example ? why it doesn't work.
"To migrate to can do a backup and restore in SQL 2012 X64.. "
so still backup and restore can the DB migrate from 2005 X86 to 2012 X64 ? it seem the SQL server 2005 RTM needs to upgrade to SP4 before migration as the database header needs to be upgrade....?
so how to migration SSIS package?
very hard to understand ! any example ? why it doesn't work.
"To migrate to can do a backup and restore in SQL 2012 X64.. "
so still backup and restore can the DB migrate from 2005 X86 to 2012 X64 ? it seem the SQL server 2005 RTM needs to upgrade to SP4 before migration as the database header needs to be upgrade....?
so how to migration SSIS package?
Hi marrowyung,
I have misspell as Queries instead of query sorry..
Here is the link about Stored Procedures..
http://en.wikipedia.org/wiki/Stored_procedure
And SQL query will not run which u have used in application..
I have misspell as Queries instead of query sorry..
Here is the link about Stored Procedures..
http://en.wikipedia.org/wiki/Stored_procedure
And SQL query will not run which u have used in application..
ASKER
"And SQL query will not run which u have used in application.. "
sorry, I don't understand this ! please clarify. All SQL query will haved used anyway, right?
I knwo what SP is but I don't think it is related, right?
why it doesn't work then ?
sorry, I don't understand this ! please clarify. All SQL query will haved used anyway, right?
I knwo what SP is but I don't think it is related, right?
why it doesn't work then ?
You will write query in application to retrieve the data from the database to generate a report etc.
Some of the query may not work in SQL 2012...
Some of the query may not work in SQL 2012...
ASKER
"You will write query in application to retrieve the data from the database to generate a report etc.
"
but this is not from the reporting service, right?
the query we built you mean ?
"
but this is not from the reporting service, right?
the query we built you mean ?
Yes..
ASKER
ok, one thing, in order to kick that SP thing out ! migration to SQL server 2008 R2 standard edition is better on this ?
SQL server 2008 R2 would be a better option,
Go through the below link for the differences between compatibility Level 90(SQL 2005) and Level 100(SQL 2008)..
http://msdn.microsoft.com/en-in/library/bb510680.aspx
Go through the below link for the differences between compatibility Level 90(SQL 2005) and Level 100(SQL 2008)..
http://msdn.microsoft.com/en-in/library/bb510680.aspx
ASKER
wait for a sec.
it is a better option or sure there are no problems at all?
I don't want to go to a point where both edition finally after migrate, give me the same kind of problem.
the compatibility leve should do nothing on the SP coding, right? I really don't understand !
it is a better option or sure there are no problems at all?
I don't want to go to a point where both edition finally after migrate, give me the same kind of problem.
the compatibility leve should do nothing on the SP coding, right? I really don't understand !
99% sure there are no problems at all...
ASKER
and you sure SQL 2012 will have problems... you have bad experience before ?
yes i had a experience when i migrated to SQL 2012 X64..
But error depends of the coding..
But error depends of the coding..
ASKER
ok.
I have recently done something similar to you.
I have moved SQL 2005 Std 64Bit databases to SQL 2012 Std 64Bit.
No problems at all, I backed them up in 2005 and then moved the bak files to 2012 and then restored them. The process of restoring them converts them to 2012, they cannot be again connected to 2005.
There could however been some incompatibilities any upgrade that may or may not be evident.
Check the Microsoft site for this.
The SSIS packages we moved to 2012 by first converting the Visual Studio Solution from 2005 to 2012. The Visual Studio has a wee wizard that does this conversion for you. It gives you a summary of the warnings errors and whatever. We just worked through those in turn.
We then deployed the packages to 2012 SSIS. Configured the SQL Agent and the proxies to run DTSExec, which is a bit of work also!!! A secret here is to have the account in the proxy having local admin rights to the relevant folders, (if you are moving files about).
Beware also, once the solution is converted to 2012 it cannot be used in 2005.
I hope this helps a bit.