Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue when running Invoke-DbaDataMasking #4970

Closed
3 of 4 tasks
MateoV97 opened this issue Jan 17, 2019 · 3 comments
Closed
3 of 4 tasks

Issue when running Invoke-DbaDataMasking #4970

MateoV97 opened this issue Jan 17, 2019 · 3 comments
Assignees
Labels
bugs life stale Stale Bot label used to identify issues that are no longer active and bot has closed them

Comments

@MateoV97
Copy link

MateoV97 commented Jan 17, 2019

Before submitting a bug report:

  • Ensure you are able to reproduce it on the latest released version (we release often)
  • Verified this bug is not already reported in an issue
  • Verified errors are not related to permissions
  • Can reproduce in a clean PowerShell session (clean = powershell -NoProfile)

Steps to Reproduce

 Invoke-DbaDbDataMasking -SqlInstance myinstance\SQL2017 -Database mydb -FilePath C:\Users\Desktop\DboJSON.json -Confirm:$false

Expected Behavior

Be able to quickly mask data in database

Actual Behavior

Load up error at each table is trying to mask, taking a long time to load and then masking data at each table.

The following exception occurred while trying to enumerate the collection: "An exception occurred while executing a Transact-SQL statement or batch.".
At line:57683 char:25
+                     if ($tableobject.Name -notin $db.Tables.Name) {
+                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   + CategoryInfo          : NotSpecified: (:) [], ExtendedTypeSystemException
   + FullyQualifiedErrorId : ExceptionInGetEnumerator

Environmental data

 - PowerShell: 
  PSVersion                      5.1.14393.2636                                                                                            
PSEdition                      Desktop                                                                                                   
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}                                                                                   
BuildVersion                   10.0.14393.2636                                                                                           
CLRVersion                     4.0.30319.42000                                                                                           
WSManStackVersion              3.0                                                                                                       
PSRemotingProtocolVersion      2.3                                                                                                       
SerializationVersion           1.1.0. 
 - - SQL Server:  Microsoft SQL Server 2017 (RTM-GDR) (KB4293803) - 14.0.2002.14 (X64)   Jul 21 2018 07:47:45   Copyright (C) 2017 Microsoft Corporation  Developer Edition (64-bit) on Windows 10 Enterprise 2016 LTSB 10.0 <X64> (Build 14393: ) (Hypervisor) 
@potatoqualitee
Copy link
Member

@sanderstad - this may be due to the size of the table. perhaps pagination would be a solution?

@wsmelton
Copy link
Member

@MateoV97 can you pull the full error from the session so we can see the reason why it is throwing the error?

$error[0] | select *

@sanderstad sanderstad mentioned this issue Feb 11, 2019
10 tasks
@stale
Copy link

stale bot commented Mar 19, 2019

This issue has been automatically marked as stale because it has not had recent activity. If you would like this issue to remain open:

  • Verify that you can still reproduce the issue in the latest version of dbatools
  • Comment that the issue is still reproducible and include:
    • What version of dbatools you reproduced the issue on
    • What OS and version you reproduced the issue on
    • What steps you followed to reproduce the issue

@stale stale bot added the stale Stale Bot label used to identify issues that are no longer active and bot has closed them label Mar 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugs life stale Stale Bot label used to identify issues that are no longer active and bot has closed them
Projects
None yet
Development

No branches or pull requests

4 participants