Comments
Sort by recent activity
Brill thanks for clarifying - at least we're not going mad [image] / comments
Brill thanks for clarifying - at least we're not going mad
Hi all, I'm getting the same after the latest upgrade... 2023-12-05 17:51:14.335 +00:00 [Information] Launching package entry point Ssms18 (version 15.0.18424.0) for SQL Prompt 10.14.3.4664.
... 2023-12-05 17:51:16.133 +00:00 [Information] SqlPromptApplication initialised (startup took 0:0:0.0)
2023-12-05 17:51:36.168 +00:00 [Information] Sql History initialized successfully 2023-12-05 17:51:37.970 +00:00 [Information] Created new ServerCandidate for server: XYZ 2023-12-05 17:51:38.234 +00:00 [Warning] Failed to load server XYZ
Microsoft.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.) I've set both encrypted and trust server certificate to no avail! Thanks, Dr. Michael Dye. / comments
Hi all,I'm getting the same after the latest upgrade...2023-12-05 17:51:14.335 +00:00 [Information] Launching package entry point Ssms18 (version 15.0.18424.0) for SQL Prompt 10.14.3.4664.
...2023-...
Good morning again,
Here's a failure I've just got by doing "everything" - i.e. just deploying all changes to the database schema; and including the dependencies [image]
Basically the failure was because I guess it was creating SQL SP's referencing the full text index before said index existed.
So; I took a two-pass approach: select all tables (new and altered); deploy those changes *without* dependencies; then 2nd pass was everything else; again without dependencies. That worked great.
N.B. It also reported differences in an assembly and a certificate; well; there will be (?) I think; especially the certificate... I chose not to deploy them... [OK I could exclude them by a filter; but I want to know they're there; just the differences aren't as such...]
Hope that makes sense and explains a bit why I tend to avoid the "dependencies" checkbox and have to do some manual input into the compare/deploy strategy [which has all worked; which is great; just a bit manual].
Ta, Michael. / comments
Good morning again,
Here's a failure I've just got by doing "everything" - i.e. just deploying all changes to the database schema; and including the dependencies
Basically the failure was because I...
Morning Mark, I think you've hit the nail on the head there - it's the "I just want a couple of those" [the schema bound views]; and yes - an explanation as to why might well help as I'm sure there are items I think that are "not required". What I'm going to do is use that checkbox and work out if/when it fails and why; I'll let you know. Ta, Michael. / comments
Morning Mark, I think you've hit the nail on the head there - it's the "I just want a couple of those" [the schema bound views]; and yes - an explanation as to why might well help as I'm sure there...
Thanks Mark, I need to review the "deploy all dependencies" bit as I tend to have that off as it drags in what seemed to be irrelevant items and I did have problems with it before (long time ago, many versions ago but I'm stuck in my ways!). I'll let you know. / comments
Thanks Mark, I need to review the "deploy all dependencies" bit as I tend to have that off as it drags in what seemed to be irrelevant items and I did have problems with it before (long time ago, m...
Duh! Answered my own question... I think it was the typing up of the question that finally made my brain work.
My version of SQLSnapper was out of date. A quick Google to: https://www.simple-talk.com/blogs/2014/ ... ql-snapper
And it tells you how to copy SqlSnapper from your SQLCompare directory. That seriously up-versioned my SQLSnapper and now the schemas match.
Well, except that the Assembly items are now appearing in the mis-match list; even though they don't???
Thanks, Dr. Michael Dye. / comments
Duh! Answered my own question... I think it was the typing up of the question that finally made my brain work.
My version of SQLSnapper was out of date. A quick Google to:https://www.simple-talk.c...