Saturday, 4 October 2014

Share Point - Part 2 Hardware Requirement

SharePoint 2013 provides for several installation scenarios. Currently, these installations include single server with built-in database installations, single-server farm installations, and multiple-server farm installations. This article describes the hardware requirements for SharePoint 2013.

Web server or Application server


  • 12 GB RAM
  • 64-bit, 4 cores Processor
  • Hard Disk Space of 80 GB for system drive


Database server


  • 8 GB RAM for Small Deployments (Applicable if users are less than 1000)
  • 16 GB RAM for Mid Size Deployments (Applicable if users are less than 10000)
  • 64 Bit with 4 Core for Small Deployments (Applicable if users are less than 1000)
  • 64 Bit with 8 Core for Mid Size Deployments (Applicable if users are less than 10000)
  • Hard Disk is depends on how much content that we have for deployment 

Happy Reading
Sanjay Bakshi
mesanjaybakshi@gmail.com

Friday, 3 October 2014

Share Point - Part 1

What is Share Point?

Share Point is web application framework/platform developed my Microsoft. It was first launched in 2001.

It help to connect people and the information. It provide the central site for sharing information with other users. It is accessible from anywhere in the world via Internet Connection.

This provides places to store and share ideas, information, communication and documents. The sites facilitates team participation. The document libraries allow for easy checking in and checking out of documents and version control.

As share point can have multiple sub sites. Similar to storing files in folder we can them in different share point sub sites.

A typical share point web site may include below information such as

1) Discussions
2) Calendars
3) Contacts
4) Task List
5) Documents

This sites can be easily searched and user can get the intimation whenever any document has been changed.

It has started with Content Management and document management but later version came up with new and broader capabilities.



Happy Reading
Sanjay Bakshi
mesanjaybakshi@gmail.com

Wednesday, 24 September 2014

RDP Copy Paste is not Working

Below Solution Comes when User is not able to Copy Paste data from Desktop to RDP
 
If any time we come in this kind of scenario below is the solution
 
1) Load Up Task Manager
2) Go to Process TAB
3) Select rdpclip.exe
4) Click End Process
5) Click on Application Tab
6) Click on New process and Type rdpclip
 
Developer Problem is solved...................


Happy Reading
Sanjay
mesanjaybakshi@gmail.com


 

Saturday, 23 August 2014

ACID


In computer science ACID is a set of properties which make sure that database transactions are processed reliably. In the context of database a single logical operation called Transaction.

 Atomicity


Atomicity means “All or Nothing”. If one part of transaction fails whole transaction will get into failed state and database status left unchanged. This concepts works in real time environment when database will suffer auto shut down, electricity failure, error and crashes.

Consistency


Consistency property ensures that whatever value database will store will pass all the validation and that is a correct value.

This will make sure that data will be valid according to defined rules, not limited to constraints, cascades and triggers

Isolation


Isolation property ensures that the concurrent execution of transactions results in a system state that would be obtained if transactions were executed serially. i.e one after another.

No transaction sees the intermediate effects another transaction. If we have two transaction doing same things isolation will ensure that both will run seprately

Durability


Durability means that once a transaction has been committed, it will remain so even in the power loss also. In relational database once a group of SQL statement runs the results will be stored permanently even if the database crashes immediately there after. 


Happy Reading
Sanjay
mesanjaybakshi@gmail.com

Saturday, 12 July 2014

Accent-Sensitivity in SQL Server

Accent-Sensitivity in SQL Server

Accent comes in picture where an application runs most the queries with first name and last name.

Some application which frequently include the functionality to support database queries based on first name and last name, which is a problematic when names contain accent character and the database is accent – sensitivity

For Example we have a table Emp_Master where we want to check all the names start with TEST, the result should be include

   TEST
   TEST1
   TEST123
   TEST1234
   ´TEST12345
   TEST´4567

But when database collation is accent sensitive the result include only

  TEST
  TEST1
  TEST123
  TEST1234

If you noticed above queries has left out all the name which are related with accent which is not a desire result.

To get a desire result we can provide two solutions to above

1)       Configure the database so that it is not accent sensitive, change the collation to SQL_LATIN1_GENERAL_CP1_CI_AI
2)       Select * from Emp_Master where fname like ‘TEST%’ collation SQL_LATIN1_GENERAL_CP1_CI_AI

Option 1 is a permanent solution and the so that when you install any new instance change the collation second option is based on requirement so that you do not have to change any database settings

Change the SQL Server Collation

Please remember it is a complex operation and can perform with below three steps

1)       Create the scripts that need to re create the database

2)       Export all your data

3)       Drop all the user database

4)       Rebuild master database new SQL Collation Property by using below command

 

Setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=InstanceName 
/SQLSYSADMINACCOUNTS=accounts /[ SAPWD= StrongPassword ] 
/SQLCOLLATION=CollationName

 

 Keep Reading!!!!!!!!! (Sanjay) (mesanjaybakshi@gmail.com)







Friday, 11 July 2014

(SQL Server )Output Clause $action Function

In SQL Server 2005 and above there is a feature of displaying an output result by output clause.The clause returns a copy of the data which user has inserted or deleted.

User can return the data into a table variable, temporary or parmanent table or to the processing application that's call the DML statements. We can use this as a archieving,confirmation message or other application requirements.

SQL 2005 allows user to add on output clause to insert,update and delete statement.Sql 2008 make us eligible to use output clause with Merge statement also.

In this blog we will learn how to use output clause with these statements.

Using with Insert Statement
*****************************************************
--Created Main Table which is actual table
Create Table TEST_INSERTED
(
EMP_NAME VARCHAR(100)
)
--Created Recorded Table where data needs to be inserted 
Create Table TEST_INSERTED_RECORDED_Example1
(
EMP_NAME VARCHAR(100)
)
--Inserted record into Actual Table
Insert into TEST_INSERTED
Output
INSERTED.*
INTO TEST_INSERTED_RECORDED_Example1
values('ABC')

--Get Record into Actual Table
 Select * from TEST_INSERTED

--Get Record into Recorded Table
Select * from TEST_INSERTED_RECORDED_Example1

User can see same record in both the table
******************************************************
Using with Update Statement
********************************************************We will use same actual table for update statement but we will create new recorded table, as we will store old value and new value both.

--Created Recorded Table where data needs to be inserted
Create Table TEST_INSERTED_RECORDED_Example2
(
NEW_EMP_NAME VARCHAR(100),
OLD_EMP_NAME VARCHAR(100)
)

--Write Update Statement
Update TEST_INSERTED
SET EMP_NAME='ABC_NEW_NAME'
output
Deleted.Emp_Name,
Inserted.Emp_Name
into
TEST_INSERTED_RECORDED_Example2
WHERE EMP_NAME='ABC'

--Get Record into Actual Table
Select * from TEST_INSERTED

--Get Record into Recorded Table
Select * from TEST_INSERTED_RECORDED_Example2

******************************************************

Using with Delete Statement
********************************************************We will use same actual table for delete statement but we will create new deleted table

--Created Recorded Table where data needs to be inserted 
Create Table TEST_INSERTED_RECORDED_Example3
(
Deleted_EMP_NAME VARCHAR(100)
)

--Write Update Statement
Delete from 
TEST_INSERTED
Output Deleted.* Into TEST_INSERTED_RECORDED_Example3


--Get Record into Actual Table
Select * from TEST_INSERTED

--Get Record into Recorded Table
Select * from 
TEST_INSERTED_RECORDED_Example3

******************************************************

Happy Reading.......
Sanjay
mesanjaybakshi@gmail.com

Saturday, 5 July 2014

SQL Server (CTE)

 
 
 
 
What is CTE
 
CTE stands with Common Table Expression. CTE can be thought as a temporary result set that defined within the execution scope of Single Select/Update/Delete/Create View.
 
This worked like derived table which does not store data as an object and last only till the duration of query.
 
Where Developer can use CTE
 
1) When Developer wants to use Recursive Query
2) Substitute of View when you want to run the View and do not want to store the definition
3) Refrence as a table which developer uses very often
 
 
Disadvantage of CTE
 
CTE can not be nested like Sub Query
 
How to use
 
USE <DB NAME>
GO
 
With TEST_CTE (Emp_Id,Emp_Name,DOJ)
as
--Define the Query
(
 
Select Emp_Id,Emp_Name,DOJ  from <Table Name>
 
)
 
--Define the Query Result
 
 
Select Emp_Id,Emp_Name,DOJ from Test_CTE
 
 
 
Happy Reading!!!!!!!!!!!!!!