January 18, 2009 at 12:38 am
Hi all,
My manager came to me and said that i need to migrate SQLCLR to SQLServer2005
i googled it and learned abt SQLCLR but want to know abt migraton stratergies involved
pls tell me
1) what r the steps involved in doin the migration.
2) do i need to convert all .NET code to YSQL? (any other method)
3) factors i need to consider
4) any simple links will be suffice
Cheers
Danny
January 18, 2009 at 2:37 am
What kind of CLR stuff do you have? Just asking in general about migrating it's a pretty vague question.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 18, 2009 at 4:39 am
u mean C# or vb.net?
i know SQLCLR means all written in .NET code and compiled as dll etc
January 18, 2009 at 6:18 am
You need to give more information here. A lot more.
What's your manager talking about migrating?
SQL CLR is the CLR (the common language runtime) within SQL Server (2005+). It allows procedures, functions, triggers to be written in one of the CLR languages (and there are a lot of them, VB and C# are just the best known)
Since you don't know what SQLCLR is, can I assume you have no existing CLR objects? If that's the case, what are you migrating from what, to what and why?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 18, 2009 at 7:36 am
presumably you have access to the source for the CLR functions you are to migrate?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs"
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy