Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
R
Constraint Violating Yak Guru
328 Posts |
Posted - 2012-02-07 : 11:18:11
|
HiCan anyone please enlighten me to the outcome of the following actions....Does the CLR UDF automatically get restored as part of the restore process, even thought the DLL might not exist on the new machine? e.g. Will the restored database on the new machine automatically be able to utilize the UDF CLR without dropping and re-creating from the .DLL file?Thanks. |
|
Bustaz Kool
Master Smack Fu Yak Hacker
1834 Posts |
Posted - 2012-02-10 : 11:53:30
|
What results did you get when you tried to do this?=================================================Men shout to avoid listening to one another. -Miguel de Unamuno |
 |
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2012-02-10 : 12:28:30
|
Once the assembly is registered/created it's embedded in the database and backed up like everything else. You do not need the actual DLL file at that point, unless you need to drop and re-create the assembly. |
 |
|
R
Constraint Violating Yak Guru
328 Posts |
Posted - 2012-02-13 : 05:16:35
|
Okay great. I haven't actually had the chance to test out yet because the DLL hasn't been deployed on the live database. If I find any different results to what robvolk states then I'll post an update.In the meantime, thanks Rob for your valued help. |
 |
|
R
Constraint Violating Yak Guru
328 Posts |
Posted - 2012-03-08 : 06:37:59
|
quote: Originally posted by Bustaz Kool What results did you get when you tried to do this?=================================================Men shout to avoid listening to one another. -Miguel de Unamuno
Just to provide some closure to this thread...robvolk's answer was exactly right. Once the DLL is 'embedded' into the database on the live server, it is no longer needed, and the functions backup and restore as part of the normal process, so the DLL is not needed again, unless I guess the logic needs to change in which case it will be re-deployed as before. |
 |
|
|
|
|