Comments
Sort by recent activity
I have connected with Microsoft Entra MFA and I tried Entra Password. Right now Entra Password worked.
I have all the tools for Essential. History, Search, Test and SourceControl
/ comments
I have connected with Microsoft Entra MFA and I tried Entra Password. Right now Entra Password worked.
I have all the tools for Essential. History, Search, Test and SourceControl
Hello thank you for the reply Ben, we are using Microsoft Entra MFA which Intellisense does not work. it does work on SQL servers where authentication is 'Windows Authentication' My local laptop has all application of the most current Tool belt essentials. (SQL History, SQL Search, SQL Test and SQL Source Control) Source control is version 7.7.10.18663 for my local On my virtual machine I did not install Source Control and installed the latest Toolbelt Essentials package on the website, so this is happening on two different machines. My team is also experiencing the same issues.
My current work around is to re-install SSMS 18 as I can connect to Azure Databases and have Intellisense as that connection is Azure Active Directory - Universal with MFA Thank you,
Dan
/ comments
Hello thank you for the reply Ben, we are using Microsoft Entra MFA which Intellisense does not work. it does work on SQL servers where authentication is 'Windows Authentication' My local laptop h...
Thank you that worked. I will try this on my virtual machine that currently does not have Source Control installed. I appreciate the quick fix. / comments
Thank you that worked. I will try this on my virtual machine that currently does not have Source Control installed. I appreciate the quick fix.
Hello, I have version SSMS v18.12.1, SQL Prompt v10.14.17.8739, SQL Source Control v7.7.9.18623 I have full Admin Rights on my Server / database and I'm getting the same error. Ran DBCC CHECKDB and there were no errors, I tried multiple databases on different servers and received the same errors. DBA's also checked the DB and permissions and all is good.
The error message does show the script that can't run and I am able to copy the script and run manually however as a work around.
An unexpected error was encountered while querying the database system tables (for Field). You may have insufficient permissions, or the database may be in an inconsistent state. You are recommended to use SQL Compare with dbo permissions. You can check the database is in a consistent state by running DBCC CHECKDB. Original error message: Specified cast is not valid.
/ comments
Hello, I have version SSMS v18.12.1, SQL Prompt v10.14.17.8739, SQL Source Control v7.7.9.18623 I have full Admin Rights on my Server / database and I'm getting the same error. Ran DBCC CHECKDB and...