asked
SQL Server Upgrade to 2008
Hi, We are upgrading our SQL 2005 to SQL 2008. Currently, Some stored procedures are using \*= and =\* for left and right outer
joins.So for this migration we have modified these Sp's since =\* and =\* are not supported in 2008 . My Question is Do we also need to modify the report datasets and SSIS packages which are using these symbols for left and right outer join. also if possible can u provide me a good link for sql 2005 to 2008 migration. Thanks in advance ,
Assuming the data is being returned in same fashion as before, no, I can't see why special testing would be needed for the apps that call the procedures that had the old syntax. A data set is a data set. As for links, go to the Microsoft site. They've got most of what you need, right there. The only thing I would add is to make sure you do a manual update on stats after the upgrade. Otherwise your system will seem slow while all the stats are rebuilt.
@sam21 Yes, you would need to change them. The old \*= and =\* syntax is long gone. The good news is that it is pretty easy to restate the queries in question as joins. By the way, you probably noticed that when you type \*= in the comment, it does not come out right. This is because the \* has a special meaning, it makes the next text in italics. To prevent it from happening, escape the \* character with the backslash (so it is interpreted literally by the parser).
Sorry, I was away, Oleg nailed it. Yes, those have to change too.
You may want to test your SSIS packages, because the way NULLs are treated between the two versions of SQL Server. SQL Server 2008 SSIS packages does require special care for fields that are NULL. For example If Row.Field1 = 42 then will fail if Field1 is null. I've had to change a lot of Script components to If Not Row.Field1_IsNull and Row.Field1 = 42 Then Best regards,
Henrik Staun Poulsen
Stovi Software
Henrik Staun Poulsen
Stovi Software
