Thanks. Yes I am doing the migration using SSIS and BCP and notice load is faster than SSMA. However, I am trying to adjust settings in SSMA which seems to...

Any advise?

Thanks! Would this work for whole db rather than individual table? How about Primary keys and clustered index?

I am using SSMA to migrate data from sybase to SQL Server. I have table that has approx 40 columns on source. I am getting an error on sybase side...

I am not trying to move the store proc from Sybase to sql server. I am trying to run the sybase store proc from SQL Server using linked server. So...

Thanks HandyD. It is a way to do it. However, the server is not standalone it will be configured for Always on. Would that make any difference?

I was looking at native option. So you saying using sql server native method data masking can be done from SQL server 2016 onwards?

Thanks! Another question on same scenario, since Node1(Primary), Node2( secondary HA) and Node4(Secondary Reporting) are in the same location and Node3(Secondary Asynch DR) is in the DR location. Let's say...

I tried with Option(Recompile), added indexes and then rewrote the query but the excessive memory grant warning is still exists.

Found below link, this is the same problem i am facing....

Found that enabling resource governor might help?

1) Do I even need to worry about this excessive memory grant? 2) If so, how can I avoid this?

Any advise. Happy to provide more details if needed?

Thanks. I just tested if enforce password policy is checked then the account get's locked.

I am not looking for the domain accounts actually for the application accounts which is sql account only.

You mean Enforce Password Policy and Pwd expiration? I enabled it and tested with failed attempts to see it cause any account locks? But the account lock did not happen?