Showing posts with label SQL. Show all posts
Showing posts with label SQL. Show all posts

Friday, June 27, 2014

Microsoft SQL Server Version List

 Microsoft SQL Server Version List


Below is the detailed list of SQL versions



RTM (no SP)SP1SP2SP3SP4
 SQL Server 2014

12.00.2000.8
 SQL Server 2012
    
11.00.2100.60 11.00.3000.0 11.00.5058.0
 SQL Server 2008 R2
  
10.50.1600.110.50.2500.0
or 10.51.2500.0
10.50.4000.0
or 10.52.4000.0
 SQL Server 2008
   
10.00.1600.2210.00.2531.0 10.00.4000.010.00.5500.0
 SQL Server 2005
  
9.00.1399.069.00.20479.00.30429.00.40359.00.5000
 SQL Server 2000
  
8.00.1948.00.3848.00.5328.00.7608.00.2039
 SQL Server 7.0
  
7.00.6237.00.6997.00.8427.00.9617.00.1063

 

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

SQL Server 2012 Service Pack 2



SQL Server 2012 Service Pack 2

In the below article I am providing the details of Service packs for SQL. Download the Latest packs by below URLS.

Microsoft® SQL Server® 2012 Service Pack 2 (SP2)
Microsoft® SQL Server® 2012 SP2 Report Builder
Microsoft® SQL Server® 2012 SP2 Reporting Services Add-in for Microsoft® SharePoint®
Microsoft® SQL Server® 2012 SP2 Power Pivot® for Microsoft SharePoint 2013®
Microsoft® SQL Server® 2012 Service Pack 2 (SP2) Master Data Services Add-in For Microsoft® Excel®
Microsoft® SQL Server® 2012 SP2 Power Pivot for Microsoft Excel® 2010
Microsoft® SQL Server® 2012 SP2 Semantic Language Statistics
  

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Wednesday, June 18, 2014

How to Migrate SharePoint content databases



How to Migrate SharePoint content databases

This is the task that every SharePoint administrator that should perform on regular. In this article I am providing the detailed steps how to do that.

Steps:
1.    Take backup of the DB which the site is using from SQL server management studio.
2.    Now go to Central Admin Website -> Application Management ->SharePoint Web Application Management -> Content Databases.
3.    Select the appropriate web application. It will display the content DB(s) used by that application.
4.    Now click on the content DB which opens Manage Content Database Settings page.
5.    Note down all the details in this page, since we require this later.
6.    Select Remove content Database & click OK & again OK.
7.    Now we have to detach our database. To do so go to SQL Management studio & right click on the database and select Take Offline. Once the process is done again right click & select Detach.
8.    Now go to “drive name:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data” and files where the DB is already located.
9.    Copy the mdf & ldf file and place it in a new drive in same location “drive name:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data”
10. Now go to SQL Management studio right click on the “Databases” in object explorer and click Attach.
11. Click on Add, browse to the mdf file you copied & click OK.
12. Now do follow step 2 & 3. In this case we will not see any content DB’s associated with the application.
13. Click on Attach Content Database & fill in the details which we got in step 5.
14. Note the DB name should be same as the previous one we detached.
15. That’s all & your DB is migrated.
  

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Monday, June 16, 2014

Transaction log is full error



Transaction log is full error – Steps to truncate the transaction log.
This is very generic Error that every SharePoint administrator face in there experience. Some times while trying to contribute to your site we will get ‘Unexpected error’ or Result error with some error code. If we see more into the event viewer log, we will find that a SQL Server error has occurred which states that the transaction log is full. In this article I am providing the steps that How to truncate the Transaction log.

Solution: Follow the below steps to truncate the Logs.

1.    Open SQL Server Management Studio and locate your site’s content db(You can find it from the central admin site).
2.    Select your  db and right click to open the backup task.
3.    Select the Transaction Log to backup, go to options and select the radio button Truncate Log.
4.    Start the backup.
5.    That’s it. Transaction Log is truncated
 

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Monday, June 2, 2014

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections



A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections

Issue: The web application can’t find while we open the CA. In the ULS logs and Event viewer sees the error” A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections”

Solution: Ensure to check the below settings to get rid of the error.

·        Ensure SQL database and services are running.
·        Ensure to reboot  the DB server after applied a Hot fix or Service Pack.
·        Ensure the Firewall is not blocking the communication
·        Ensure The SharePoint Installation Account does have the required permissions to the SQL Server database.
·        Ensure Network connectivity is OK between the SharePoint Server and SQL Server

If issue Still persists, Restart the SQL services and restart the DB server If necessary.
 

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

ShareThis

X