Comments
Sort by recent activity
Dear CPerez, The product is licensed to me. I log into the network DB via MFA utilizing my company login. I cannot get 'Find Invalid Objects' to work on the network DB, but I can get it to work on my local DB. What privilege do I need for this to function correctly? Thanks, Doug / comments
Dear CPerez,The product is licensed to me. I log into the network DB via MFA utilizing my company login. I cannot get 'Find Invalid Objects' to work on the network DB, but I can get it to work on m...
Files and screen shot attached - thank you! Doug / comments
Files and screen shot attached - thank you!Doug
So now it works - are we sure it is not going to not work again? Thanks - I'm still not sure what happened. Doug / comments
So now it works - are we sure it is not going to not work again?Thanks - I'm still not sure what happened.Doug
Should I uninstall first? Not sure where this change came from. / comments
Should I uninstall first? Not sure where this change came from.
Another UPVOTE in support to have this tool extension in VS Code / comments
Another UPVOTE in support to have this tool extension in VS Code
That is exactly what I see - but I use this all of the time - seems like an easy fix. / comments
That is exactly what I see - but I use this all of the time - seems like an easy fix.
Excellent - RG Rocks! / comments
Excellent - RG Rocks!
Jessica, Oddly enough - debugging the SP which wrote the data - we were using VARCHAR for the description? Not sure why your product would prefix the N for SQL 2008 and not prefix the N for the SQL 2017 version - but the second I made the change on my end it compared correctly. Maybe SQL is storing it as SQLVARIANT? Anyway - resolved although odd from your products point of view, Doug / comments
Jessica,Oddly enough - debugging the SP which wrote the data - we were using VARCHAR for the description? Not sure why your product would prefix the N for SQL 2008 and not prefix the N for the SQL ...
Yes. Your product consistently flags the columns as different, even though the same script has been applied to both databases. We are comparing a SQL 2008R2 instance vs a SQL 2017 instance. The 2008 version is always prefixed with N, the 2017 version is not. Kinda doesn't make sense - since the meta data itself is NVARCHAR for both. The odder issue is that it is only for the table meta data, not the column meta data. I can give you examples and screen shots - it happens 100% of the time. Doug / comments
Yes. Your product consistently flags the columns as different, even though the same script has been applied to both databases.We are comparing a SQL 2008R2 instance vs a SQL 2017 instance. The 2008...
Yes - thanks so much!
Ozzie / comments
Yes - thanks so much!
Ozzie