Issue here is that if you are creating it from physical assembly then you need to copy it manually on the db server.
Solution is to use assembly bits. but that would create issues while creating assembly in master db with external access. and you dont want to set trustworty to off for mater .not even for a while.
fix is that we give the permission set as safe to the assembly that we are creating in master. as assembly in master is oinly going to use to create assymetric key, you should be ok.
http://stackoverflow.com/questions/9059912/asymmetric-key-creation-over-network
http://www.sqlservercentral.com/articles/SQLCLR/74377/
Solution is to use assembly bits. but that would create issues while creating assembly in master db with external access. and you dont want to set trustworty to off for mater .not even for a while.
fix is that we give the permission set as safe to the assembly that we are creating in master. as assembly in master is oinly going to use to create assymetric key, you should be ok.
http://stackoverflow.com/questions/9059912/asymmetric-key-creation-over-network
http://www.sqlservercentral.com/articles/SQLCLR/74377/
No comments:
Post a Comment