tag:blogger.com,1999:blog-4402664127960334547.post7091648937644052647..comments2024-03-24T10:38:58.256-05:00Comments on Nebraska SQL from @DBA_ANDY: Invalid value given for parameter PASSWORD. Specify a valid parameter value.@DBA_ANDYhttp://www.blogger.com/profile/09130139756284009675noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-4402664127960334547.post-88298385333522867682019-05-01T23:15:04.431-05:002019-05-01T23:15:04.431-05:00Question is Then how can we transfer login from sq...Question is Then how can we transfer login from sql 2012 + servers to sql server 2008 R2- servers <br /><br />Please elaborateManishArorahttps://www.blogger.com/profile/12090966667949765696noreply@blogger.comtag:blogger.com,1999:blog-4402664127960334547.post-16645040511177363902018-11-27T15:07:11.938-06:002018-11-27T15:07:11.938-06:00Hello, great article. Doesn't the same issue ...Hello, great article. Doesn't the same issue exist for use of column level encyption in the database (aka use of keys). I am aware of traceflag 4631. Not sure how this plays out here.Anonymoushttps://www.blogger.com/profile/14955140083739874904noreply@blogger.comtag:blogger.com,1999:blog-4402664127960334547.post-41365625054277571652018-10-20T01:01:20.786-05:002018-10-20T01:01:20.786-05:00Great post as always. However you mentioned only T...Great post as always. However you mentioned only Target server only, not source server. But going through it multiple times, got to know Source was 2012+ server.ManishArorahttps://www.blogger.com/profile/12090966667949765696noreply@blogger.com