Resolved issue #67 and fixed error in Invoke-SQLUploadFileOle #68
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…hen file is too big so that it crashes Powershell interpreter.
|
Thanks for the updates! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
I've resolved issue #67 that I'd reported earlier since that was a straightforward fix and also noticed that my
Invoke-SQLUploadFileOlefunction can sometimes derail PowerShell interpreter when formatting big input file into hex interpretation.To overcome that I've changed implementation to use different method for converting byte array into hexstring that works far more stable now.
Also, could we mention those two functions in PowerUpSQL's wiki, like for instance here? It would help anyone who's not aware they could use MSSQL to download/upload files :)
Hope you'll like it!
Cheers,
Mariusz.