SQL Assistant 5.0 BETA program is starting this week March 4

Will this new ver 5.x supports Visual Studio 2010 (WPF-IDE)?

Yes, we will surely support it when it is available. As far as I know VS 2010 is not yet released. The RC is still going through some changes. Once it is publicly released, we can start working on updating the interface. From what I've heard, this version of VS is based on .NET 4, while SQL Assistant Add-on code for VS is dependent on .NET 2 and in the RC version they don't play nice together, VS refuses to load .NET 2 dependent code (the backward compatibility is broken).

	SysOp wrote:
	Hi. The first post in this thread provides specific instructions for getting the beta version.

Then, have we to send a mail for each build you do?
In the email of first build there is just a direct link and the automatic update doesn't work...

	maxpesola wrote:
	Then, have we to send a mail for each build you do? In the email of first build there is just a direct link and the automatic update doesn't work...

I emailed the support to ask if that works that way and they told me that "Check updates" will not work in the beta version, this function is for the
retail build. They also sent me a link to build 5.0.74 and it did not contain build/version number. I think/hope it will always be the latest beta so I can download it without having to wait for a reply whenever I see there is a new build. Still, it would be nice to know whether I'm right or wrong.

I'm sorry for the inconvenience, this message board is currently the only place where notifications of new beta updates are posted. The updates (a.k.a. builds) are expected approximately every 5 days.

Here is a link to the recently setup page for downloading the most recent beta build http://www.softtreetech.com/sqlassist/beta.htm This pages displays build number and time.

This page is going to be decommissioned once after the beta period ending (no specific date known yet).

New beta build 5.0.82 is available.

This build corrects several issues with SQL intellisense, corrects issues with importing settings from previous versions overwriting new features in version 5; and also contains significant improvements in the Test Data Generator.

IMPORTANT NOTE for users installing new beta builds on a system with an older version of SQL Assistant on which you already installed previous beta version builds. After the installation of the latest build it is highly recommended that you reload the default SQL Assistant settings using the following method:

Double-click SQL Assistant's icon in the system tray to open the Options dialog.
Click the Import/Export button on the Options dialog.
Tick the Load Default Options checkbox. Click the Import button and then click OK.

It seems that 5.0.82 has error, which is as follows;

setting changes do not take effect immediately. for example, after I added new code snippet, I could not use it.
however, right after restarting sql assistant it worked.
everytime I change settings, i should restart program.

Which editor are you using? Are using system tray icon to change settings or the add-on settings?

I am using SSMS 2005 and tested both tray icon and add-on settings.

	maesta1 wrote:
	setting changes do not take effect immediately. for example, after I added new code snippet, I could not use it. however, right after restarting sql assistant it worked. everytime I change settings, i should restart program.

I had the same problems with 4.8.x trial but it vanished after I installed the 5.0 Beta.

This issue should be fixed in the next beta version build. I've seen status update for this issue in the internal tracking system, but don't have that build yet and cannot confirm it yet.

After formatting a stored procedure code I ended up with the cursor declaration somehow corrupted. The first row of the "select" is normal but all the subsequent rows between "select" and "from" are broken.

Code:

DECLARE cur_torlendo_hozzaferesek CURSOR FAST_FORWARD READ_ONLY
FOR
   SELECT a.AccessId,
   h .id_kulcs_pozicio,
   h .id_kartya,
   h .id_kulcs,
   h .muvelet,
   h .bekerult
   FROM dbo.hozzaferesek h
   INNER JOIN IQKeyLiteDB1.dbo.Positions p
   ON h.id_kulcs_pozicio = p.PositionId
   INNER JOIN IQKeyLiteDB1.dbo.[Keys] k
   ON k.PositionId = p.PositionId
   INNER JOIN IQKeyLiteDB1.dbo.KeyAccesses ka
   ON ka.KeyId = k.KeyId
   INNER JOIN IQKeyLiteDB1.dbo.Accesses a
   ON a.AccessId = ka.AccessId
   INNER JOIN dbo.kartyak k2
   ON k2.id_kartya = h.id_kartya
   AND k2.bekerult = h.bekerult
   INNER JOIN IQKeyLiteDB1.dbo.WiegandIdentification wi
   ON k2.id_kartya = wi.WiegandIdentificationCode
   WHERE h.muvelet = 4
   AND h.feldolgozva IS NULL

I took a look at the code formatting and saw that the "declare" template for cursors is a bit "oversimplified". Is there a way to fix this?

I played with your query and found out that there is a deficiency in the way the default set of formatting rules is setup. DECLARE and DECLARE CURSOR are defined in the same rule. They should be split. Here is what you can do:

In the list of formatting rules right click "declare" rule name and select Copy. Rename the duplicated entry. For example name it "cursor"

For the new "cursor" rule in the formatting pattern text leave only the cursor part on a single line

	Code:
	CURSOR ... FOR ...

Modify the "declare" and leave only the declare part

	Code:
	DECLARE ..., ...

Save changes.

This change will improve formatting of cursor statements

I tried something similar but to no avail. I guess I should not have left "DECLARE" in it. Doesn't matter, your suggestion works. Thank you.