[TGKnIght]

Yes, make sure you have selected the correct database before executing.

[TGKnIght]

Well I do have to say that so far Beta 11 has been behaving very well.. And thank you to the devs for putting up with this grumpy old dude 😉

[TGKnIght]

A little trick I use is to add an extra SQL query into your scheduled action that gives me basically a timestamp of a successful import.

For example, I have some jobs that are set up as “Notification Services”.. After performing any DB operations I want, I add an extra line at the end

Code:

SELECT 'NAME OF IMPORT – SUCCESS', NOW();

Then set the email notification to notify every time. If it is successful, you will get the timestamp back of when the db operation was completed.

Hope this helps in the meantime!

PS To the devs, please don't forget my suggestion of adding in the timestamp into a custom message subject. (VS currently you can either do timestamp OR a custome subject)

[TGKnIght]

Am I getting all these problems because I'm running Windows XP? Or is it because my DB is on Windows Server 2003? What test environment do you have? It makes no sense that you guys can never reproduce my errors..

You guys keep asking for test data… I'm telling you this error occurs on ANY database I have (Yes I have more than one) Anyway, I spent the time to make up some dummy tables for you, since I cannot provide my data from work anyway. The error occurs with these tables just the same as any other tables in any other DB that I need to manage.

PS It would make sense if you guys allowed files with a .sql extension to be uploaded to the message board, no?

Code:

select t1.id, t1.Desc1, t1.Desc2, t2.Desc3, t2.Desc4
from table1 t1, table2 t2
where t1.id = t2.Table1ID

[TGKnIght]

peterlaursen wrote on Nov 1 2006, 11:08 PM:

@TGKnight

Was that beta10 ?

No sorry was still beta 9 n2, installing beta 10 now

[TGKnIght]

Crashed… no error message, no debugger..

[TGKnIght]

Ok … beta 9 n 2 closed silently, no debug window appeared.

EDIT :: x2

[TGKnIght]

Ok going to download beta 9 shortly..

With the way you just laid out the licensing, I could have gotten away with buying 2 licenses.. Since I only have myself and one of my other guys that would be using SQLyog simultaneously..

[TGKnIght]

I would just post your dump file here if you got one that relates to this thread..

Anyway just wanted to let you guys know, I have been using 5.2 beta 8 all day long with only one connection open and it has been behaving well..

Someone further up said that they experienced the problem with only one connect, but where normally I would have crashed 2 – 3 times by now, I have been running the same instance all day long..

Will continue testing with one connection come next week.

[TGKnIght]

It is installed on 5 computers, 2 of which are used regularly.. ( I did not realize that licensing was per user, I thought it was per computer so I had purchased 5)

I don't have the other computers using beta versions, just my own dev box.. AFAIK they are not suffering from the same problem

[TGKnIght]

Someone else mentioned this further up the thread… But it is very possible that this error is occuring because of having multiple connections open at once..

I will continue to try to use the Yog with only one connection open for a while and see if the problem occurs.. So far it has not.

[TGKnIght]

There is no longer a “debug” version as of Beta 8.

If you get the Beta 8 version installed the debugger is now integrated.

[TGKnIght]

Well I assume the priority at this point is to get the new debugging system to actually catch the error?

[TGKnIght]

peterlaursen wrote on Oct 24 2006, 12:36 AM:

Please upgrade to beta8 (Check 'News' section for the link)

This will give us a dump that we can use. The one that you give here only tells that the crash is 'triggered' from a Win32 API -functiuon. Not what SQLygo did at that particular time.

My last error message screenshot is using the Beta 8 build… The error is not being caught by the new debugger.

[TGKnIght]

As I mentioned I had forgotten to get a screenshot of it before!

Here is a screenshot from it occuring today.

This is completely random.. I can't force the error to occur… It happens under the same circumstances as the rest of the times I have reported this issue… It is very random and sometimes occurs soon after starting the Yog or sometimes the Yog runs for a while then spits up.

The only thing that is consistent about this problem is that it occurs when SQLYog is minimized or in the background and then I bring it into focus.

I have no way of providing you the structure and data from my database at this point in time.

[Author]

Posts