Comments
Sort by recent activity
... this is a hack, but if your not in a production environment, rolling back the minimum tls version will work
I create a new image with this DockerFile
FROM redgate/sqlcompare
RUN /bin/sh -c 'touch /etc/ssl/openssl_custom.cnf'
RUN /bin/sh -c 'echo "openssl_conf = openssl_init " >> /etc/ssl/openssl_custom.cnf'
RUN /bin/sh -c 'cat /etc/ssl/openssl.cnf >> /etc/ssl/openssl_custom.cnf'
RUN /bin/sh -c 'echo "[ openssl_init ] " >> /etc/ssl/openssl_custom.cnf'
RUN /bin/sh -c 'echo "ssl_conf = ssl_sect " >> /etc/ssl/openssl_custom.cnf'
RUN /bin/sh -c 'echo "[ ssl_sect ] " >> /etc/ssl/openssl_custom.cnf'
RUN /bin/sh -c 'echo "system_default = system_default_sect " >> /etc/ssl/openssl_custom.cnf'
RUN /bin/sh -c 'echo "[ system_default_sect ] " >> /etc/ssl/openssl_custom.cnf'
RUN /bin/sh -c 'echo "CipherString = DEFAULT@SECLEVEL=1 " >> /etc/ssl/openssl_custom.cnf'
ENV OPENSSL_CONF=/etc/ssl/openssl_custom.cnf
/ comments
... this is a hack, but if your not in a production environment, rolling back the minimum tls version will work
I create a new image with this DockerFile
FROM redgate/sqlcompare
RUN /bin/sh -c 'tou...
Is it possible to roll back to the previous version? from now on I'll check the forum before blindly updating [image]
/ comments
Is it possible to roll back to the previous version?from now on I'll check the forum before blindly updating
FIXED! update the latest version of Sql Prompt (9.5.0.9311) see this thread for the explanation
https://forum.red-gate.com/discussion/84956/sql-search-not-returning-any-results#latest
/ comments
FIXED! update the latest version of Sql Prompt (9.5.0.9311)see this thread for the explanation
https://forum.red-gate.com/discussion/84956/sql-search-not-returning-any-results#latest
I'm experiencing the exact same issue sql search v 3.2.6.2313 ssms v 17.9.1 the last error in my log (there's one for each database) 23 Apr 2019 17:23:19.115 [92] ERROR DatabaseObjectIndexer - Exception while indexing database tempdb: System.EntryPointNotFoundException: Unable to find an entry point named 'sqlite3_open_interop' in DLL 'SQLite.Interop.dll'. at System.Data.SQLite.UnsafeNativeMethods.sqlite3_open_interop(Byte[] utf8Filename, Byte[] vfsName, SQLiteOpenFlagsEnum flags, Int32 extFuncs, IntPtr& db) at System.Data.SQLite.SQLite3.Open(String strFilename, String vfsName, SQLiteConnectionFlags connectionFlags, SQLiteOpenFlagsEnum openFlags, Int32 maxPoolSize, Boolean usePool) at System.Data.SQLite.SQLiteConnection.Open() at RedGate.SQLSearch.Indexing.SQLite.SqliteDatabaseConnection.EnsureConnectionOpen() at RedGate.SQLSearch.Indexing.SQLite.SqliteDatabaseConnection.CreateCommand() at RedGate.SQLSearch.Indexing.SQLite.DatabaseObjectStorage.Initialise() at RedGate.SQLSearch.Indexing.DatabaseObjectIndexer.Index(CancellationToken ) / comments
I'm experiencing the exact same issue sql search v 3.2.6.2313ssms v 17.9.1the last error in my log (there's one for each database)23 Apr 2019 17:23:19.115 [92] ERROR DatabaseObjectIndexer - Excepti...
That did it. Thanks! That is also un-intuitive as all-get-out as it seems that the place for the Filter is in the projects Options tab. Anyway thanks for the help.
/ comments
That did it. Thanks! That is also un-intuitive as all-get-out as it seems that the place for the Filter is in the projects Options tab.Anyway thanks for the help.
Robert;
I installed that version, as soon as it was available, and returned the Comparison Options back to their defaults (re-enabled Throw Exceptions On SQL parser errors) .
So far it does appear to have solved these issues.
Thanks / comments
Robert;
I installed that version, as soon as it was available, and returned the Comparison Options back to their defaults (re-enabled Throw Exceptions On SQL parser errors) .
So far it does appear ...
I'm using version 5.4.0.3902 with TFS and am experiencing the same issue
"After successfully checking in the view I recieve the error "There was an error parsing the file {0} at line {1}, column {2}, near the text."
I receive this error
with a view that uses CROSS APPLY OPENJSON(r.ApplicationData) WITH([KEY] VARCHAR(MAX) '$.KEY' ,CROSS APPLY OPENJSON(r.[ApplicationData])
[list=2]with a SP that uses the exact same syntax inside a CTE[/list]
The view and the stored proc work and have been deployed to SQL server. this is strictly an issue whereby SLQ SOURCE CONTROL blocks me from managing any other changes to the database. / comments
I'm using version 5.4.0.3902 with TFS and am experiencing the same issue
"After successfully checking in the view I recieve the error "There was an error parsing the file {0} at line {1}, column {2...
Robert,
changing the "Throw exceptions on SQL parser errors" to false does seem to have gotten me past the original error, but now I get "unexpected token: ["r",<1184>,line=8,col=23] [char=246]"
the text of the view
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO
CREATE VIEW [dbo].[vw_DataByRequest]
as
SELECT [r].[EffectiveScreeningRequestID] ,
LTRIM(RTRIM([j].[KEY])) [KEY] ,
LTRIM(RTRIM([j].[VALUE])) [VALUE]
FROM [dbo].[MyTable] [r]
CROSS APPLY OPENJSON(r.[Data])
WITH (
[KEY] VARCHAR(MAX) '$.Key'
, [VALUE] VARCHAR(MAX) '$.Value'
) j
WHERE ISJSON(r.[Data])=1
GO / comments
Robert,
changing the "Throw exceptions on SQL parser errors" to false does seem to have gotten me past the original error, but now I get "unexpected token: ["r",<1184>,line=8,col=23] [char=246]"
th...