Monday, 30 May 2016

Enterprise Application Integration (EAI)

Enterprise Application Integration (EAI)

This is a business computing term for the plans, methods and tools aimed at modernizing, consolidating and coordinating the computer applications in Enterprise.
Typically, an enterprise has existing Legacy applications and databases and want to continue to use them while adding and migrating to a new set of applications that exploit the internet, e-commerce, extranet and other new technologies. EAI may involve developing a new total view of an enterprise's business and its applications fit into the new view, and then devising way to efficiency reuse what already exist while adding new applications and data.
EAI encompasses methodologies such as
  • Object-oriented programming,.
  • Distributed, cross-platform program communication using message brokers with Common Object Request Broker Architecture (CORBA) and COM+.
  • The modification of Enterprise Resource Planning (ERP) to fit new objective.
  • Enterprise-wide content and data distribution using common database and data standard implemented with the Extensible Markup Language (XML).
  • Middleware, message queuing and, other approaches.
[Source : techtarget.com]
Read the below link to know more about EAI and ESB.

https://www.mulesoft.com/resources/esb/enterprise-application-integration-eai-and-esb

Thursday, 26 May 2016

Prevent double clicking or multiple Form submission after the ASP.Net Button is clicked?

Some time it happens that we write a complex code or a lengthy DB operation with in a button submit event which take more than a second or two to complete it operation and control comes back to the button. In these scenario the user has chance to click the button again and there are high chance that the code with in the button get executed again. Though this can be handled in server side, it is better to handle this on client side. Out of many way to handle, I found the following was as more robust.

Attach an client click event to the button

<asp:Button ID="btnSubmit" runat="server" Text="Submit" OnClientClick="return preventReSubmissions();" OnClick="btnSubmit_Click" />

Create a javascript method preventReSubmissions() with the below content.

<script type="text/javascript" src="jquery/1.11.2/jquery.min.js"></script> <script type="text/javascript"> var isSubmitted = false; function preventReSubmissions() { if (!isSubmitted) { $('#<%=btnSubmit.ClientID %>').val('Plz Wait..'); isSubmitted = true; return true; } else { return false; } } </script>

Friday, 27 November 2015

Parsing XML Data from SQL Database Column


There are scenarios when we will have data dumped in to Database Column in XML format.
Now when we are reading those data it does not make sense to present the data in the XML format.
Here are the example where we have XML data in a below format.


declare @Employee as nvarchar(max)
declare @EmployeeXML as XML
declare @cnt int
   SET @EmployeeXML='<Employees>
   <Employee><EmployeeID>Anoj Singh</EmployeeID><EmployeeName>150025</EmployeeName><Department>Delivery</Department></Employee>
   <Employee><EmployeeID>Ashutosh Mund</EmployeeID><EmployeeName>150016</EmployeeName><Department>Sales</Department></Employee>
   <Employee><EmployeeID>Nihil Jain</EmployeeID><EmployeeName>150017</EmployeeName><Department>Finance</Department></Employee>
   <Employee><EmployeeID>Sravan Kumar</EmployeeID><EmployeeName>150018</EmployeeName><Department>Admin</Department></Employee>
   </Employees>'

SELECT b.value('(EmployeeID)[1]', 'NVARCHAR(200)')+','+
       b.value('(EmployeeName)[1]', 'NVARCHAR(200)')+','+
       b.value('(Department)[1]', 'NVARCHAR(200)') as EmployeeData
       FROM  @EmployeeXML.nodes('Employees/Employee') a(b)
       print @Employee

This will display the data as shown below.


There are other way and format also which I will share in subsequent posts.


Monday, 23 November 2015

Installing Complete TFS 2010 in Windows Server 2008 R2 with SharePoint

Installing TFS 2010 in Windows Server 2008 R2 with SharePoint 
(including SSRS, SSIS, and Build Server Configuration)






































Error: 15138 – The database principal owns a schema in the database, and cannot be dropped

Error: 15138 – The database principal owns a schema in the database, and cannot be dropped

This is a typical issue faced by every Database guy if they are beginner to SQL DB world. This appears when we try to delete a database user who's owner of the database schema and SQL DB does not allow to delete the user if the user owns a schema.

Resolution to this is, a) Find out the schema or schema's owned by that user.
                                      b) Assign those schema to some other user
                                      c) Delete the user.

This can be done in 2 ways 1. Using SQL Script
                                                   2. Using Management Studio.

Using SQL Script

SELECT name FROM  sys.schemas WHERE principal_id = USER_ID('DBUser')

Run another command to assign the schema to another user
   
ALTER AUTHORIZATION ON SCHEMA::NameofSchema TO DBUser2 
GO
DROP USER DBUser

Using Management Studio

Step 1 : Select the User name and Open Property Window



Step 2 : Select the Schema Property viewed in above screen


Step 3 : Assign the Schema to another user by clicking Search and Browsing appropriate new user.












The most recommended is to assign to "dbo".

Step 4: Now if you see the new user property you can see the Schema is owned by the new user.




















Now you can delete the user which you are intend to.

Monday, 29 June 2015

ERROR : Package 'RadLangSvc.Package, RadLangSvc.VS......' failed to load

Package 'RadLangSvc.Package, RadLangSvc.VS, Version=10.0.0.0, culture=neutral, PublicKeyToken=89845dcd8080cc91' Failed to Load



Error
 
Package 'RadLangSvc.Package, RadLangSvc.VS, Version=10.0.0.0, culture=neutral, PublicKeyToken=89845dcd8080cc91' failed to load
 
Solution
  1. Open Visual Studio Offline Installer Folder
  2. Open WCU folder
  3. Open DAC folder
  4. Install below .msi:
      i) DACFramework_enu.msi
      ii) DACProjectSystemSetup_enu.msi
      iii) TSqlLanguageService_enu.ms

Tuesday, 23 June 2015

Starting with FastSearch 2010 for SharePoint Configuration Part 1

The first step towards configuration of Fast Search in SharePoint 2010 environment is to have the SharePoint Enterprise edition activated. This will have a Feature called Fast Search Server 2010 for SharePoint Master Job Provisioning

To check this get into Central Admin -> System Setting -> Manage Farm Feature.




If you do not see this available here following are the steps to follow.
Go to Central Admin -> Upgrade and Migration click on Enable Enterprise Feature


There you can verify whether the Enterprise feature is activated or not.
If not go ahead and activate the Enterprise feature with a valid License key.
Once activated you can see the Fast Search Server 2010 for SharePoint Master Job Provisioning activated.