I am writing this blog post to point to an important published article from Microsoft Patterns and Practices Team on understanding, designing and implementing Big Data Solution on Windows Azure using HDInsight.
Want to know what is big data ? what is being used for ? Do you have a need for it ? what is the best scenarios to think about adopting to big data tools?
The answer for these questions are covered under the first section of Understanding Big Data on below link:
Second section of this article is covering how to design a scalable big data solutions in Azure platform using HDInsight. Would you use big data to explore your data and extract patterns, Apply BI techniques, Build ETL integration tools, Automation data processes all are covered on below link:
Third section of this article is covering how to using Azure as PaaS to implement your Big Data Solution using HDInsight including how to provision your first Hadoop cluster node and all required configurations for storing your big data files, build end-to-end solutions and visualizing your data:
Hope this helps!
I am writing this blog post to show how to migrate or move the standard MVC authentication tables into your existing database in your asp.net web application.
When you create a MVC web application in VS 2013, VS embed a sql server database in your project, and this project is being used as a source of asp.net membership. Since you will not use this database as an embedded file and you want to have it as part of your existing database in SQL Server instance. The file is created under App_Data folder. To see the .mdf file click on Show all files in the solution explorer.
You can see the contents of this database and all tables in the server explorer window.
How to create those tables in SQL server ?
First, you can delete the .mdf file in App_Data folder. Since we don’t need any of these tables.Then, we need to update the default connection string in the web.config to point to our database.
<add name=”DefaultConnection” connectionString=”Data Source=SERVER\INSTANCENAME;Initial Catalog=DBNAME;Integrated Security=True” providerName=”System.Data.SqlClient” />
Third, Open Nuget Package Manager and write the following commands:
Check out your database, all ASP.NET membership tables with Prefix Asp have been create and then you can test it out by running your application and execute membership actions such as Signing up or Signing in to your application.
Created tables after running above commands:
Hope this helps.
I am writing this blog post to provide some tips and insights on using open source search technologies such as Solr in your solutions and applications.
Here are my notes:
1) Solr is an open source search server product. It is free and one of the most trusted, mature search products in the market.
2) Solr uses lucene, lucene is the heart of Solr search server product. Lucene is the full text service or component that is used in Solr which provides all search, index and queries capabilities.
3) Lucene is a java based library to create, manage, and retrieve inverted index files.
4) Inverted index is a specialized data structure by Lucene to handle queries to text based documents.
5) Using full text feature that is available in some DBMS is not a replacement for Solr, Solr provides advanced search, query and ranking capabilities.
6) Solr provides on top of lucene full text capability the following features: pagination, sorting, faceting, auto-suggest, spell checker, hit highlighting, data modeling, grouping, and standard http API to integrate with your solutions.
7) Each Solt server has only one home, the path of the home is $SolrInstallation/example/solr, where $SolrInstallation is the path where you installed solr binaries.
8) Each Solr server can contain more than 1 core, each core contains its index data and configuration.
9) Solr web application is stored under solr.web folder which contains all servelts, html and js files.
10) Solr is running on Jetty as an application server. Google is using Jetty in its App Engine platform.
Hope this helps.
References: Solr in Action
I was developing a web application that reference SharePoint 2013 dlls, and since SharePoint server dlls in general runs on a 64 bit environment, i want to use IIS express in Visual Studio 2013 without the need to use full local IIS that runs on 64 bit.
I was getting this error message when i am running my web application:
Could not load file or assembly or one of its dependencies.
and i was seeing in the yellow error page that the VS 2013 is using IIS express under c:\ program files (86)\ IIS Express folder which is the 32 bit.
I want to switch IIS express to 64 bit so i will be able to run my web application that references 64 bit SharePoint dlls. here is the solution for this:
From Visual Studio 2013 IDE:
Click on : Tools –> Options –> Projects and Solutions –> Web Projects –> Use the 64 bit version of IIS Express –> check this checkbox and save.
Once you save, make sure you exit any instance of the IIS express and try to re-run your project! It will run with no issues!
I was working on a public SharePoint site and i wanted to enabled the developer dashboard utility. I Ran the following powershell command to enable the developer dashboard:
Turn On Developer Dashboard Powershell Command:
$content = ([Microsoft.SharePoint.Administration.SPWebService]::ContentService)
$appsetting.DisplayLevel = [Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::On
**If you want to turn it off, just change the On flag to Off and you are good.
After that, I was able to see the developer dashboard icon in the Central Administration site but not on my public SharePoint site.
So basically, I found that you have to grant permissions for anonymous users to access this utility since it is not accessible for anonymous users even if the utility is enabled.
How to enable Developer Dashboard for anonymous users:
$contentService = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
$dashboardSettings = $contentService.DeveloperDashboardSettings
$dashboardSettings.RequiredPermissions = [Microsoft.SharePoint.SPBasePermissions]::EmptyMask
By default, the required permissions property for the developer dashboard utility is “AddAndCustomizePages” which is available for authenticated users who have this permission, so you need to changed it to no permissions by setting the value to EmptyMask which means in SharePoint permissions world no permissions are needed.
Note: This is a good technique while you are developing, testing and in the user acceptance test phase of any SharePoint implementation project. when you don’t need this utility it is strongly recommended to turn it off on production environment.
Hope this helps!
1) SharePoint base permissions:
I ran into an issue when i was working on a SharePoint hosted app, when the application loads it keeps throwing errors in the IE development tool that “RegisterSod is undefined”.
I was deploying the application to the following site url:
The cause of this problem is that i didn’t have a site in the root site collection, so i opened the Central Administration and created a site collection for the same web application that i am using to deploy my SharePoint apps to “appCatalog” site.
Re-deployed my application! it works!
Hope this helps!