You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I have a somewhat unique situation and hoping the team here can offer some constructive guidance. A customer is asking me to do some work on one of our products and part of the solution will require creating PS support scripts that will need to work with SQL 2019 Dbs (CRUD w/some xxGB imports). While the initial script usage will be on Win, they are asking for PS 7 so they can leverage Linux a little further down the road.
There will be a few scenarios in how the scripts will be called with the Db connection string being passed as part of the call. Security will be important and with the script receiving the connection string there will be the need to add some level of connection string validation. Have been looking at the SqlConnectionStringBuilder class.
Everything I read is that Microsoft.Data.SqlClient is the direction to go with System.Data.SqlClient not being updated anymore AND I can't do certain validations, such as column encryption, in the System.DataSqlClient version of SqlConnectionStringBuilder with PS 7. That pushes me toward Microsoft.Data.SqlClient. On the surface that sounds simple enough but when I attempt to load the Microsoft.Data.SqlClient NuGet package in PS7 things go sideways as I can't get it to load (dependency fun).
I'm trying to decide what is the best way to approach this. Once developed, other customers likely take advantage of this as well so the set up can't be too complex. Don't see documenting a SIMPLE PS Microsoft.Data.SqlClient NuGet process given everything I'm seeing online. Would love to hear recommendations on what would be the best way to approach this.
Thank you much for your time, suggestions and recommendations.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello, I have a somewhat unique situation and hoping the team here can offer some constructive guidance. A customer is asking me to do some work on one of our products and part of the solution will require creating PS support scripts that will need to work with SQL 2019 Dbs (CRUD w/some xxGB imports). While the initial script usage will be on Win, they are asking for PS 7 so they can leverage Linux a little further down the road.
There will be a few scenarios in how the scripts will be called with the Db connection string being passed as part of the call. Security will be important and with the script receiving the connection string there will be the need to add some level of connection string validation. Have been looking at the SqlConnectionStringBuilder class.
Everything I read is that Microsoft.Data.SqlClient is the direction to go with System.Data.SqlClient not being updated anymore AND I can't do certain validations, such as column encryption, in the System.DataSqlClient version of SqlConnectionStringBuilder with PS 7. That pushes me toward Microsoft.Data.SqlClient. On the surface that sounds simple enough but when I attempt to load the Microsoft.Data.SqlClient NuGet package in PS7 things go sideways as I can't get it to load (dependency fun).
I'm trying to decide what is the best way to approach this. Once developed, other customers likely take advantage of this as well so the set up can't be too complex. Don't see documenting a SIMPLE PS Microsoft.Data.SqlClient NuGet process given everything I'm seeing online. Would love to hear recommendations on what would be the best way to approach this.
Thank you much for your time, suggestions and recommendations.
Beta Was this translation helpful? Give feedback.
All reactions