Comments
Sort by recent activity
Did you try to remove also the folders in the AppData folder as I said in the first reply? / comments
Did you try to remove also the folders in the AppData folder as I said in the first reply?
AppData is the %LOCALAPPDATA% path of Windows. The complete path is which is `C:\Users\<your_user>\AppData\Local\Red Gate` / comments
AppData is the %LOCALAPPDATA% path of Windows. The complete path is which is `C:\Users\<your_user>\AppData\Local\Red Gate`
Hi @OhNoooo,
after the uninstall processes ends (please try to remove everything), try to delete the Program Files (or x86) and AppData/Local/RedGate folder too. It's not straightforward, but without all the information in those folder, you have more chance to get it.
If this does not work, try to reinstall SSMS also.
Let us know
cheers / comments
Hi @OhNoooo,
after the uninstall processes ends (please try to remove everything), try to delete the Program Files (or x86) and AppData/Local/RedGate folder too. It's not straightforward, but witho...
Hey @kyle_vaske
could you please add further details? Please include the error stack trace (you should see the error in details clicking on the error link, if present) and also the repro step.
Are you replacing the database without re-linking it?
Thanks / comments
Hey @kyle_vaske
could you please add further details? Please include the error stack trace (you should see the error in details clicking on the error link, if present) and also the repro step.
Are ...
In addition to the @Grant's suggestion, if you have just a few linked server hard coded and if you can change the code, you could consider replacing them with synonyms (that point to the linked server objects).
I know, it's a refactor and it can be potentially massive, but I think that you'll get many advantages.
just my two cents,
cheers / comments
In addition to the @Grant's suggestion, if you have just a few linked server hard coded and if you can change the code, you could consider replacing them with synonyms (that point to the linked ser...
Yes @Grant, I'm totally with you. It's often a stressing-and-heavy work to do, but leaving the code as is leads to code smells sometimes :-).
[OOT]
I know that you agree with me (I really hope :-) ) when I say that whether we'd like to be more "DevOps", we should invest some effort in changing small chunks step by step, in order to get a real sandbox in development stage and, in this case too, give value to the customers (quicker releases, more test isolation and automation, and so on).
[/OOT] / comments
Yes @Grant, I'm totally with you. It's often a stressing-and-heavy work to do, but leaving the code as is leads to code smells sometimes :-).
[OOT]
I know that you agree with me (I really hope :-) ...
hey @...,
having the same object name is a problem if you don't specify the two part name (ex. Schema.Table). It works by default if you have the objects under the dbo schema (or the default one of the user which executes the script). It depends on how the script has been created. However, this should not work also after the restore. But if I got it, the second time you tried, the script ran successfully.
So, I guess that there was a "open transaction" problem. Something that created objects, not committed, or simply stuck in the middle on the, let's say, "first database". I know, it sounds weird, but I had similar problem. I could not see objects which were created and I had a database file corruption (or a disk failure I don't remember right now actually).
What do you think about this possibility? / comments
hey @...,
having the same object name is a problem if you don't specify the two part name (ex. Schema.Table). It works by default if you have the objects under the dbo schema (or the default one of...
hi GeoRewind,
I cannot understand why you need a comparison criteria like this one. Does this mean that you change the structure directly in production, so the target database drifts before you release? In a straight release strategy I'd expect a dev/test environment to be ahead than the production, regardless the date in which a column is changed.
If you change something in the target database, you can "merge back" the changes or resolve conflicts before release the new version of the database.
Did I get? / comments
hi GeoRewind,
I cannot understand why you need a comparison criteria like this one. Does this mean that you change the structure directly in production, so the target database drifts before you rel...
Rog wrote: »
Is there a way I can run this on specific objects instead of an entire database?
you're right, I confused that feature with "find unused items" in scripts.
You mentioned "it's breaking at the same place", which is? Right after the click?
In order to understand better, you could trace the commands using SQL Profiler. It could be some trouble in your user's permission set. / comments
Rog wrote: »
Is there a way I can run this on specific objects instead of an entire database?
you're right, I confused that feature with "find unused items" in scripts.
You mentioned "it's bre...
hi @Rog,
does this happen on all the objects you check? / comments
hi @Rog,
does this happen on all the objects you check?