SurendraThotaMSBIProfessional

SSAS Error :Error ErrorCode="3238133825" Description="File system error: A FileStore error from WriteFile occurred. Physical file: \\?\E:\MSSQL\Log\DbHWE.2.db\Network Equipment.0.dim\5729.H4 OBJ DB ID.ksstore When you process a dimension by using the Process Update processing option or the Process Default processing option, the string file store (.asstore) is appended instead of being overwritten. This behavior reduces the process time even if no change is made on the string attribute. If the dimension is frequently processed that way, the string file store will become very large. When the string file store reaches 4 GB, you can no longer process the dimension by using the Process Update processing option or the Process Default processing option. You will receive an error message: “File system error: A FileStore error from WriteFile occurred. Physical file: ....” If you are doing ProcessUpdate on a regular basis, I would suggest doing processFull now and then. When yo

In AMO Script    when we have partition with some template ie  complete query with dummy dates  and for example it is named as myTemplatePartitionName_partialday  //generate new partition creation script // First identify the template partition and assign to a Partition object                     AMO. Partition amoTemplatePartition = amoMeasureGroup.Partitions.FindByName(myTemplatePartitionName_partialday);   // clone that template to another patition Object                     AMO. Partition amoNextPartition = amoTemplatePartition.Clone();   //  assign the prefdefined name and ID to the partition                     amoNextPartition.ID = myNextPartitionName;                     amoNextPartition.Name = myNextPartitionName;

In AMO scripting to find a particular Partition in a Measure group  then see the below script //Declare AMO server object and get the server detail from connection manager          amoServer = new AMO. Server ();                 amoServer.Connect(myConnectionManager.ConnectionString);   // Then get Measure group name using FindByName function                 amoMeasureGroup = amoServer.Databases.FindByName(amoServer.ConnectionInfo.Catalog.ToString()).Cubes.FindByName(myCubeName).MeasureGroups.FindByName(myMeasureGroupName);                 amoServer.CaptureXml = true ;   // Prepare partition name  which you are going to search                 String myNextPartitionName = myPartitionNamePrefix + myLastPeriodName_source.Replace( ":" , "_" ).Replace( "-" , "_" );                 //check wether next partition already exists                 if (!amoMeasureGroup.Partitions.Contains(myNextPartitionName))

After searching for many Best practices and finally we found some which we fallow regularly Development Best Practices 1.        Rename all Name and Description properties from the default. This will help when debugging particularly if the person doing the debugging is not the person that built the package Only select columns that you need in the pipeline to reduce buffer size and reduce On Warning events at execution time Use Sequence containers to organise package structure into logical units of work. This makes it easier to identify what the package does and also helps to control transactions if they are being implemented. Use caching in your LOOKUP components where possible. It makes them quicker. Watch that you are not grabbing too many resources when you do this though. 5.        Use naming conventions for your tasks and components The acronyms below should be used at the beginning of the names of tasks to identify what type of task it is. Task Prefix For L