Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.

SQL DRY RUN

john9's profile image john9 posted 3 weeks ago in HeidiSQL portable Permalink

Hello,

HeidiSQL looks amazing but when running SQL queries I do not find any option to get a dry-run, isn't it?

Is there a way to code a dry-run for whatever query?

Thank you.

ansgar's profile image ansgar posted 3 weeks ago Permalink

No, there is no such a "dry-run mode".

Probably comparable to the EXPLAIN logic, which analyzes the query and tells you about performance issues.

Description

john9's profile image john9 posted 2 weeks ago Permalink

Thank you. But in this case I should run it once before to get the description. Am I wrong? Thank you

ansgar's profile image ansgar posted 2 weeks ago Permalink

EXPLAIN provides an analysis, not a description. However, it's up to you whether you want to run it before running the query itself.

john9's profile image john9 posted 2 weeks ago Permalink

Thank you!

john9's profile image john9 posted 2 weeks ago Permalink

I did search several and strings on the server and replace them. A few of them were correctly replaced.

Others are still there despite Heidisql does not find those strings anymore. (searching on the server) (it was in 2 tables mainly)

Is there anything I should do in order to update the tables on the server after Heidisql updated the tables in the app?

john9's profile image john9 posted 2 weeks ago Permalink

see attached what I mean. It has been 2 days where apparently no tables have those values according to HeidiSQL but online everything is the same. Despite cleaning the cache several times (browser - wp - cf)

please help

2 attachment(s):
  • not-found-0
  • online-yes-cleaned-cache-both-cf-wp-browser
ansgar's profile image ansgar posted 2 weeks ago Permalink

You are either

  • searching on the wrong server
  • or searching in the wrong database
  • or searching for the wrong HTML snippet (that "href=..." may have some additional attribute?)
john9's profile image john9 posted 2 weeks ago Permalink

there is 1 server (but I'm checking it with the owner), 1 database, the snippet has not attributes (we copied pasted it from the source code)

it is on CloudFlare but I do not think it impacts on it (till we delete the cache)

Thank you

ansgar's profile image ansgar posted 2 weeks ago Permalink

Ok if you are sure you edited all relevant places in your database, it can only be a cache issue in the application. But that's beyond what I know from here.

john9's profile image john9 posted 1 week ago Permalink

you mean, we should clean the database cache? or restart phpmyadmin? is there a way to manage it with HeidiSQL?

Thank you

john9's profile image john9 posted 1 week ago Permalink

with

DBCC FREEPROCCACHE DBCC DROPCLEANBUFFERS

I have syntax errors for MariaDB

john9's profile image john9 posted 1 week ago Permalink

same for DBCC DROPCLEANBUFFERS

ansgar's profile image ansgar posted 1 week ago Permalink

I'm talking about your application's cache, but that was just an attempt to point you in the right direction. I cannot tell you how your application is using some cache. I just can say for sure these "DBCC.." commands are not SQL queries, which you can run in HeidiSQL or pma.

john9's profile image john9 posted 1 week ago Permalink

Ok. Thank you so much for your support. (I did use different commands but I've got permission problem) We are on it with the server support. Thank you

john9's profile image john9 posted 5 days ago Permalink

we have been able to edit the information_schema and maximize the values but now when trying to replace fields, it starts doing it but after a couple of them it shows "not responding" - see attachment (it was 1 hour ago and it is still that way)

1 attachment(s):
  • not-responding-HeidiSQL-search-replace
john9's profile image john9 posted 5 days ago Permalink

Before it wasn't able to replace them due to an SQL timeout. Now HeidiSQL is not responding when doing it.

john9's profile image john9 posted 5 days ago Permalink

I've also found out, from the "relevance" field that it changed some of them. (more than what we saw it did at the very beginning) But not all of them and especially we cannot explain why it crashes.

john9's profile image john9 posted 3 days ago Permalink

any feedback? it's happening to me only? (or is it a well known issue) Thank you

ansgar's profile image ansgar posted 3 days ago Permalink

I thought you already replaced all occurrences of that HTML snippet?

I already told you you should consult your application and check its caches or whatever. Probably the issue is not in the database but somewhere else.

john9's profile image john9 posted 3 days ago Permalink

Once edited the information_schema I've been able to replace some snippets. I use HeidiSQL with Windows. (using a laptop with good 32gb ram and 16 log processors) Which cache should I clear? I frequently clear the browser cache. sometimes I flush the dns but I have not found anything about cache and HeidiSQL.

Maybe running the query for a lot of fields it reaches some pick of RAM/CPU usage and it crashes. (now it is my first guess)

ansgar's profile image ansgar posted 3 days ago Permalink

I was talking about your application's cache. And that was a guess, which may not be helpful. Please read and understand.

You probably need some more technical knowledge before fixing that. Your posts read as if you're not familiar with databases in general.

However, your issue is not in HeidiSQL, but likely in your specific application, where you see the old data (if that's still the problem).

This is a forum for HeidiSQL, not for any custom database in your own applications.

john9's profile image john9 posted 3 days ago Permalink

That's fine. Thank you

BubikolRamios's profile image BubikolRamios posted 1 day ago Permalink

Not responding might appear in following case: you run replace an then there are million records and you figure you should do something in between, any you click and all sort of things (within heidi). Do not do that. Try that on like 50 records table and it should wok fine, do not disturb. If it crashes on 50 records, and you do not interrupt, then the prob is elsewhere.

john9's profile image john9 posted 1 day ago Permalink

Ok. Thank you for your feedback.

Please login to leave a reply, or register at first.




Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.