I looked around microsoft.com and here, but I don't see a target date for the production version. Is that info posted anywhere?
Thanks,
Ned
If you are looking for the date for Release version of SSEv 3.1 then it would be in Nov this Year.
We will soon post message on our Blog http://blogs.msdn.com/sqlservereverywhere
sqlI've just downloaded SQL Server Express (with advanced services) from both the main SQL Server Express website and from MSDN. When I right click on the exe I downloaded and go into properties the Product Version says SQLEVALVER. To me this implies it is an evaluation.
Can I confirm this is just a mistake and if we start to redistribute the product it won't timeout in the future? I am sure it is not an evaluation but just want to make absolutely sure.
hi,
, yep... it's true ...
but as long as you downloaded the correct binaries there's no problem, and it will install the appropriate SQLExpress version..
and this are not Eval binaries... they are just "free"..
regards
I am using ProClarity 6.1 and Enterprise version of analysis server 2005. (not sure if I need an proclarity update or a fix for ProClarity because i guess there is a newer version 6.2)
Because of one of the performance optimizations that I did after following some blogs on the net, I can't specify slicerSel parameters to my proclarity graphs! Let me explain:
I have a slicer in Proclarity graph for which I used to specify a url querystring parameter as slicerSel=xxxxxx. This was working until I modified the dimension.
The modification: initially my dimension had the following attributes: Key, Name. Now I just have one attribute Name, whose key column points to KEY (db) and Name column points to NAME (db). because of this my slicerSel parameters do not work.
I checked the html of proclarity by doing an view souce and found the following difference.
before:
<option value ="[CLIENTNAME].[NAME].&[ABCDE FGHIJK]">ABCDE FGHIJK<option>
After modifing the Keycolumn and Namecolumn:
<option value ="[CLIENTNAME].[NAME].&[4.94735E6]">ABCDE FGHIJK</option>
Now I can't specify the slicer using the number 4.94735E6 which i dont think is the key (its in scientific format).
My question is, Is there any way out to specify the slicer as ABCDE FGHIJK (Name) as before ?
If it is not possible, shall I add another attribute to the dimension called Key and then seperate the Key and Name from the single attribute? will this impact the performance? especially because the dimension will have another attribute which contains just the key, which will not be displayed but used in the relationships. Is there any specific way to design this? (Key is the primary key column of the database table, which is used for storing dimension values and referenced in the Fact tables).
Regards
Your key is 494735.
The only way you will get the name there is to set-up the name only as a separate attribute. Then the name will be used as a key, slightly less efficient. ProClarity generates the MDX with the key element of the attribute value that is selected from the slicer.
You can also change the data type of the key when creating the attributes in Visual Studio. Sometimes it defaults to a double if the data is sourced from a view rather than a table.
