SQLSrvAnalysisSrvcs Work Item Rss Feed

Commented Issue: Few Links referenced in the document are outdated [15452]

furmangg — Thu, 03 Mar 2011 04:49:07 GMT

Please fix the links referenced in the document, those are outdated.

SSAS Load Testing Best Practices:

http://sqlsrvanalysissrvcs.codeplex.com/releases/view/3505?ProjectName=sqlsrvanalysissrvcs

SSAS Load Testing Best Practices
documentation, 1527K, uploaded Jul 12 2007 - 1539 downloads
http://sqlsrvanalysissrvcs.codeplex.com/releases/view/3505#DownloadId=15642

Thanks,
Comments: ** Comment from web user: furmangg **

How did you get to that link? That's a very old release. You'll want to use the latest release which can always be found at:
http://sqlsrvanalysissrvcs.codeplex.com/releases

Created Issue: Few Links referenced in the document are outdated [15452]

vansree — Wed, 02 Mar 2011 23:20:23 GMT

Please fix the links referenced in the document, those are outdated.

Commented Issue: Report CountersDataPoints - grafic tables doesn't fit the frame [14891]

Germo — Wed, 15 Dec 2010 17:45:29 GMT

see the attachement: all frames around all graphic tables are to small - or all graphic tables are to big for the frames.
Windows 7 Home Premium 64 bit, SQL Server 2008 R2: it's a new installation on a new windows.
I have the same effect in MSIE and on firefox (firefox mode and IE mode)
Comments: ** Comment from web user: Germo **

it is a bug in SQL Server 2008 R2 when you use 96 DPI: https://connect.microsoft.com/SQLServer/feedback/details/577159/ssrs-2008-r2-chart-data-visualization-shows-cropped-on-browser?wa=wsignin1.0

Created Issue: Report CountersDataPoints - grafic tables doesn't fit the frame [14891]

Germo — Wed, 15 Dec 2010 13:13:10 GMT

Created Issue: wrong target database in [ssas].[populate_olap_query_log_table] [14886]

Germo — Tue, 14 Dec 2010 20:48:09 GMT

in the documentation you write:
1. Create_Table_SSAS_OLAPQueryLog.sql – This Transact-SQL script creates the OLAPQueryLog table in the MDW_Control database on the MDWDataCollectionServer.
2. Populate_OLAP_Query_Log.sql – This Transact-SQL script creates the Populate_OLAP_Query_Log_Table stored procedure in the MDW_Control database on the MDWDataCollectionServer.

You write about MDW_Control database, but in the [ssas].[populate_olap_query_log_table] is only a parameter for the mdw database:
@mdw_database_name nvarchar(128) = null

This is OK - but the code for inserting has:

INSERT INTO ' + @mdw_database_name + '.[ssas].[OlapQueryLog]

and this is wrong, because the [ssas].[OlapQueryLog] is not in @mdw_database_name but in the current database (for example mdw_control)
the above line shoud be changed to
INSERT INTO [ssas].[OlapQueryLog]

Created Issue: wrong variable SSASServerSSASInstanceName in Execute_MDW_Load_Perfmon_Counter_Config_Table_SP.sql [14885]

Germo — Tue, 14 Dec 2010 20:24:06 GMT

There is an error in Execute_MDW_Load_Perfmon_Counter_Config_Table_SP.sql

USE MDW_Control
GO
EXEC [mdw].[load_perfmon_counter_config_table]
@mdw_database_name = 'MDW'
, @Include_Counter = 'Y'
, @instance_name_filter = '$(SSASServerSSASInstanceName)'
go

--SSASServerSSASInstance should be used but not SSASServerSSASInstanceName

Created Issue: Bug in ASQueryGen [14041]

carlrabeler — Wed, 18 Aug 2010 17:48:07 GMT

there is a small bug in TupleDictionary.cs, line 235 where it says

string mdx = "with member [measures].[__TESTTEST__] as 'null' select " + queryTokenDefinition + " on 0 from [" + cube + "] where [measures].[__TESTTEST__]";

The problem with it is that it prevents ASQueryGen to generate random members on the measures "axis".

If the line is changed to

string mdx = String.Format("select {0} on 0, null on 1 from [{1}]", queryTokenDefinition, cube);

it can also create random measure sets (and still does not query data; what I guess you wanted to do by using the WITH MEMBER ... term).

Created Issue: ASCMD.exe for SSAS 2008 [12272]

viraj — Thu, 25 Mar 2010 16:06:26 GMT

I think there is a bug in the Command Line sample utility provided with SQL Server 2008 for running xmla commands against the SSAS instance. We have used the similar utility for SQL Server 2005 to run a XMLA command without any issues. But when I tried to do the same with the utility provided as a sample with SQL Server 2008, I ran into issues. Having debugged it, I narrowed the problem. There is a provision in the utility to run multiple xmla commands separated by “GO”. The 2005 utility regex looked for exact characters ‘GO” to create batches, however 2008 utility regex looks for any characters that end with “GO” characters. Therefore our XMLA was being incorrectly parsed into batches by occurrences of captions containing “go”. E.g <Caption>Código de pago</Caption>.
Once I changed the regex from
const string BatchRegex = @"^[\w\W]*?[\r\n]*go\s";
TO
const string BatchRegex = @"^[\w\W]*?[\r\n]go\s";

The utility now can execute the xmla correctly.

Created Issue: ssas.SSASCleanBatch looks to have bug. [10929]

opoudel — Thu, 12 Nov 2009 16:45:12 GMT

ssas.SSASCleanBatch procedure has where criteria as P_BatchID <= @BatchID in order to get rid of all the old batches. Should not that be P_BatchID < @BatchID?

Closed Issue: Unable to use ASTrace in 64 Bit machine

furmangg — Fri, 21 Aug 2009 16:13:28 GMT

I tried to build ASTrace targetting x86 cpu and deployed into 64bit server. I cant get to start the service. It always fails with following message.
8/19/2009 10:28:54 PM: Error: Microsoft.SqlServer.Management.Trace.SqlTraceException: Failed to initialize object as reader. ---> System.Runtime.InteropServices.COMException (0x8004021A)
at ?A0x8159d01c.ProcessError(Int32 hr, UInt16* lpszMessage)
at Microsoft.SqlServer.Management.Trace.CTraceControllerBase.InitSource(Boolean bReOpen)
at Microsoft.SqlServer.Management.Trace.CTraceObjectsRowsetController.InitSource(Boolean bReOpen)
at Microsoft.SqlServer.Management.Trace.TraceServer.InitializeAsReader(ConnectionInfoBase serverConnInfo, String profileFileName)
--- End of inner exception stack trace ---
at Microsoft.SqlServer.Management.Trace.TraceServer.InitializeAsReader(ConnectionInfoBase serverConnInfo, String profileFileName)
at ASTrace.Trace.OnStart(String[] args)

I have already applied the sugesstions given in the other thread related to this issue.

Please let me know what else needs to be done.
Comments:

resolved

Commented Issue: Unable to use ASTrace in 64 Bit machine

sambathraj — Fri, 21 Aug 2009 04:31:04 GMT

Thanks For your reply. I now reinstalled the service and added the registry key. It now worked.

Commented Issue: Unable to use ASTrace in 64 Bit machine

furmangg — Thu, 20 Aug 2009 19:58:04 GMT

you followed the instructions at http://timlaqua.com/2008/11/installing-astraceexe-in-a-64-bit-environment/ and it still didn't work? Works great for me.

Created Issue: Unable to use ASTrace in 64 Bit machine

sambathraj — Thu, 20 Aug 2009 05:36:47 GMT

Created Issue: ActivityViewer - LoadServerNode uses RegisteredServerName instead of ServerName

ScaleOvenStove — Fri, 02 Jan 2009 22:28:26 GMT

In SSMS, if you register a server and name it, then it doesn't work with activity viewer. You can type in a "Registered Server Name" different from your server name, so example:

Server Name = ABC123
Registered Server name = MyServer

ActivityViewer will try to use the Registered Server Name from the RegSrvr.xml in App Data folder. It needs to use the <ServerName> under <ConnectionInformation> instead. A kludegy workaround is this code change in the LoadServerNode

else if (node.Name.Equals("SERVER", StringComparison.InvariantCultureIgnoreCase))
{
string server = node.InnerXml;
server = server.Substring(server.IndexOf("<ServerName>"), server.IndexOf("</ServerName>") - server.IndexOf("<ServerName>"));
server = server.Replace("<ServerName>", "");
tn = new TreeNode(
server,
(int)ImageListItems.ServerConnected,
(int)ImageListItems.ServerConnected);
tn.Tag = AppNodeType.Server;
}

Commented Issue: ASTrace IA64, X64

tlaqua — Mon, 17 Nov 2008 11:39:25 GMT

Problem reported with AS trace on IA64 and x64 platforms
Environment:
======================
1.　Windows2003 ENT ENU
2.　DEV ENU 09.00.3033.00

Repro Steps:
======================
1. Build ASTrace.sln.
2. Create a folder named ASTrace under folder "C:\Program Files\Microsoft SQL Server\MSSQL.1"
3. Copy the files "ASTrace.exe.config" and "Standard.tdf" from the default sample installed folder "C:\Program Files\Microsoft SQL Server\90\Samples\Analysis Services\Administrator\ASTrace" to the folder ASTrace created in step1. The copy ASTrace.exe (The size of this file is 24KB.) from the debug folder to the folder ASTrace created in step1.
4.Open a Visual Studio 2005 Command Prompt, CD to "C:\Program Files\Microsoft SQL Server\MSSQL.1\ASTrace".
5.Execute the following command:
InstallUtil.exe ASTrace
6.Keey the properties of ASTrace.exe.config file as default.
7.Open Windows Service Control Manager and navigate to ASTrace, then start it.

Expectations:
======================
1.The ASTrace service should be started without error and after that the status ASTrace service displayed in Windows Service Control Manager shoulde be "Started".
2.Table "ASTraceTable" should be created in database "AdventureWorksDW".

Actual Results:
======================
1.Failed to start ASTrace service. Warning message provided by Windows Service Control Manager
Comments: ** Comment from web user: tlaqua **

Workaround: http://timlaqua.com/2008/11/installing-astraceexe-in-a-64-bit-environment/

Commented Issue: ASTrace IA64, X64

stoicform — Tue, 12 Aug 2008 03:40:36 GMT

Service started! Now to test if it is working. That last step was to shore up the domain authentication by setting the service account to a domain account with rights on the target SSAS and MSSQL servers.

Commented Issue: ASTrace IA64, X64

stoicform — Tue, 12 Aug 2008 03:39:25 GMT

Just noting that I had to manually create a reg key (after reading the code to see what it wanted).
regedit export:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASTrace]
"path"="C:\\Users\\timshea\\work\\ASTrace\\ASTrace\\CS\\ASTrace\\bin\\Debug"

Commented Issue: ASTrace IA64, X64

stoicform — Tue, 12 Aug 2008 03:19:55 GMT

Forcing the build target to x86 moved past this error (was set to CPU agnostic in the downloaded sample code). pfclt.dll can be found under Program Files (x86) if tools are installed with SQL. Now onto the next issue..

Commented Issue: ASTrace IA64, X64

stoicform — Tue, 12 Aug 2008 03:07:05 GMT

Found this in MSDN: The log provider for SQL Server Profiler was unable to load pfclnt.dll because it is only supported on 32-bit systems.

Commented Issue: ASTrace IA64, X64

stoicform — Tue, 12 Aug 2008 02:55:49 GMT

I have a perfect repro. pfclnt.dll does not exist.
Note that I only got this far by manually creating the "path" registry key, which is failing to be created at service install.

8/11/2008 7:46:55 PM: Service Started in 'C:\Users\timshea\work\ASTrace\ASTrace\CS\ASTrace\bin\Debug'
8/11/2008 7:46:55 PM: Cannot start Analysis Server trace:
8/11/2008 7:46:55 PM: Analysis Server name: 'bi-server-24-lh\ssas2k8'
8/11/2008 7:46:55 PM: Trace defintion : 'C:\Users\timshea\work\ASTrace\ASTrace\CS\ASTrace\bin\Debug\Standard.tdf'
8/11/2008 7:46:55 PM: Error: Microsoft.SqlServer.Management.Trace.SqlTraceException: Failed to initialize object as reader. ---> System.IO.FileNotFoundException: Could not load file or assembly 'file:///C:\Program Files\Microsoft SQL Server\100\Tools\Binn\pfclnt.dll' or one of its dependencies. The system cannot find the file specified.
File name: 'file:///C:\Program Files\Microsoft SQL Server\100\Tools\Binn\pfclnt.dll'
at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.LoadFrom(String assemblyFile)
at Microsoft.SqlServer.Management.Trace.TraceUtils.CreateInstance(String assemblyRelativePath, String objectClass)
at Microsoft.SqlServer.Management.Trace.TraceServer.InitializeAsReader(ConnectionInfoBase serverConnInfo, String profileFileName)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

--- End of inner exception stack trace ---
at Microsoft.SqlServer.Management.Trace.TraceServer.InitializeAsReader(ConnectionInfoBase serverConnInfo, String profileFileName)
at ASTrace.Trace.OnStart(String[] args) in C:\Users\timshea\work\ASTrace\ASTrace\CS\ASTrace\Service1.cs:line 73