How to execute a stored procedure within C# program – with Parameter, using Loop

Here is a sample :

using (SqlConnection conn = new SqlConnection(ConnectionString) {
    conn.Open();

    // 1.  create a command object identifying the stored procedure
    SqlCommand cmd  = new SqlCommand("CustOrder", conn);

    // 2. set the command object so it knows to execute a stored procedure
    cmd.CommandType = CommandType.StoredProcedure;

    // 3. add parameter to command, which will be passed to the stored procedure
    cmd.Parameters.Add(new SqlParameter("@CusID", custId));

    // execute the command
    using (SqlDataReader rdr = cmd.ExecuteReader()) {
        // iterate through results, printing each to console
        while (rdr.Read())
        {
            Console.WriteLine("Product: {0,-35} Total: {1,2}",rdr["ProductName"],rdr["Total"]);
        }
    }
}

Workaround: SharePoint 2013 Preview prerequisite installer doesn’t install the Microsoft SQL Server 2008 R2 SP1 Native Client

If you install SharePoint 2013 Preview by running the prerequisite installer (Microsoft SharePoint Products Preparation Tool) and you see this line in the log file:

Error: The tool was unable to install Microsoft SQL Server 2008 R2 SP1 Native Client.

Use these steps to work around the problem:

• Go to http://go.microsoft.com/fwlink/p/?LinkId=262370 and manually download and install the Microsoft SQL Server 2008 R2 SP1 Native Client (1033\x64\sqlncli.msi).

  Important! Do not download and use 1033\IA64\sqlncli.msi or 1033\x86\sqlncli.msi. These versions are not supported for this preview release.

• Run the Microsoft SharePoint Products Preparation Tool again.

Starting/Running SQL SERVER 2012 (SQL Permissions) for SharePoint 2013

You need to give the SharePoint Account that you plan to install and configure SharePoint with some elevated rights in SQL. Typically we recommend you use a dedicated account [Domain]\[SharePoint Admin] and this account will need the following roles on the SQL Server.

• DB_Creator
• Security_Admin
• Public

From your newly installed SQL Server click Start > All Programs > Microsoft SQL Server 2012 > SQL Server Management 2012.

After waiting this loading user settings screen will appear:

Wait for some time then the following screen appears:

Login as [Domain]\[SharePoint Admin] by selecting “Windows Authentication”:

From Object Explorer expand-out Security.

Under Security expand out Logins.

In case you don’t have the User

• Right click on Logins.
• From the menu choose New Login.
• For Login name: enter [Domain]\[SharePoint Admin]  or whatever account you will be logged into SharePoint as when you do the install.

After right click, select Properties. The following screen will come:

On the left, under select a page click Server Roles.

Check the box for dbcreator and securityadmin. Also, leave public selected.

Click OK. Now your [Domain]\[SharePoint Admin] is ready to install sharepoint on the server.

Max Degree of Parallelism for SQL SERVER 2012 (before installing Sharepoint 2013)

Now that you have SQL Server all installed there is one more configuration change you need to do in order to make SharePoint happy. You need to change the max degree of parallelism. Don’t ask me what that is. Something about number of processors and how SQL uses them. Unfortunately SQL Server defaults to 0 and SharePoint 2013 necessitates, demands, forces, requires, and otherwise really wants you to set it to 1. So make the change. If you are running SharePoint 2010 this change is not required but is recommended.

Now if you look at the link I gave you saw a bunch of fancy SQL to change it. Barf! Let’s change it the easy way, with a mouse.

From your newly installed SQL Server click Start > All Programs > Microsoft SQL Server 2012 > SQL Server Management 2012.

On the Connect to Server screen click Connect. If for some reason the Server name: field is blank you would just type in the name of the server.

At the top of the Object Explorer window you see your server. Right click on it.

From the menu that appears click Properties.

In the Select a page section click Advanced.

Scroll to the bottom and change Max Degree of Parallelism from 0 to 1.

Click OK.

That does it. No need to reboot or anything else to make the change take effect.

Installing SQL SERVER 2012 (for SharePoint 2013)

To install SQL SERVER 2012 we are using the following Setup file:

#####_SQLServer2012EnterpriseEditionwithSP1_ServerCAL(With_#########)_x64

Right Click and Mount, Run “setup” Application file as Administrator:

Note: We are logged in as [SharePoint Admin] for all installations.

This Screen will Show up:

Click “Installation” on the left side, the following screen will come:

Click “New SQL Server stand-alone installation or add features to an existing installation”, the following screen will come:

Click “Show Details” to view details, Click “OK” after verifying the setup support rules. In case there is a problem resolve it and Re-run the Setup. Now the following screen appears:

Wait for some time, the following screen will come:

In the product key section, Select “Enter the Product Key” which should be 25 character key. Click next, the following screen will come:

In the license Terms section, Select “I accept the license terms” and Select Send feature usage data to Microsoft….. Click next, the following screen will come:

Click Next to “Include SQL Server product updates”:

After the above screen, a prompt as shown below will appear for restarting the system:

After restart run the setup again and reach to the below screen:

When the Setup Support Rules screen pops up review any errors or warnings you get. If nothing bad has happened the Next button will be available to click. Click Next to view the following screen:

For Setup Role select SQL Server Feature Installation and click next.

On the Feature Selection screen this is where you need to be smart. In order to make SharePoint run you only need to select one check box, Database Engine Services. I would highly recommend you also check Management Tools – Basic and Management Tools – Complete. Click Next to view the following screen:

Wait for some time, the following screen will come:

Now when you read all of these awesome features you might be thinking “I want to kick the tires of Reporting Services – SharePoint” or some other random feature. That is great, tire kicking is fun and important but if you are reading the blog post to get SQL Server installed correctly for SharePoint then you probably aren’t ready to start randomly installing features. Even if you were ready to install them you would still most likely come back and do them after SharePoint was up and running, not before. So let’s ignore them for now and click next.

On the Installation Rules screen SQL will make some checks. In this case my Server did not have the Microsoft .NET Features installed. You will need to manually add the feature now. While you do go ahead and leave this SQL window open.

To add the .NET Windows Server feature click on Start > All Programs > Administrative Tools > Server Manager.

From the right side of the screen click on Features.

Over on the left side of the screen click on Add Features.

Check the box for .NET Framework 3.5.1 Features.

When you check the box a window for Add Features Wizard will appear telling you the additional required roles. Click Add Required Role Services.

Click Next.

At the Web Server (IIS) screen click Next.

Accept all of the defaults and click Next.

At the Confirm Installation Selections click Install.

At the Installation Results screen make sure everything was successful and then click Close.

Jump back over to your SQL Installation Rules screen and click the Re-run button.

If the tests are Passed click Next to continue.

After Installation Rules the Following screen appears:

Assuming this is the only install of SQL Server on this server then you are going to want to take all of the default settings for the Instance Configuration screen, but in my Case I have updated the name to be my server, Click Next.

Wait for some time, the following screen will come:

At the Disk Space Requirements screen click next.

For the Server Configuration screen it is asking you what accounts you want to run SQL Server as. The only service you are worried about right now is the SQL Server Database Engine. This service should always be run as a domain account not a local account. Next to SQL Server Database engine click on MANAMA1\spadmin and a drop down arrow will appear.

Click <<Browse…>>.

Select your SQL account you want to use and click OK.

Enter the account password and keep the startup type as Automatic click next.

Wait for some time, the following screen will come:

On the Database Engine Configuration screen there are lots of changes you could make and over time you will learn about these options but for the purpose this guide you will except all of the defaults. You only need to click Add Current User and it is shown as.

If you were building a production capable SQL Server best practice 101 would be to store your data and log files on different volumes. By default SQL Server will store everything on the C: drive. If you want change that behavior take a gander at the Data Directories tab.

Once you are ready click next the following screen appears:

For the Error Reporting screen select Send Windows and SQL Server Error Reports…Click next the following screen appears:

At the Installation Configuration Rules screen click next.

You are ready to Install, so click Install.

Wait for some time, the following screen will come:

When the installation finishes you may be prompted to restart. This is not directly because of SQL Server but instead because of other recent installs you have done that you haven’t rebooted since. In my case because I added the .NET feature. When SQL is all done click close. If you have any other open windows at this point you can close them as well. You are all done.

If you got the pop up screen to do a reboot it will not automatically happen, you will need to reboot on your own.

Note: The Above error is due to Installation of .Net Framework 3.5, after resolving this when you run the setup again you receive the following screen:

Now the SQL SERVER 2012 is successfully installed.

Now do what is mention in this post: Max Degree of Parallelism for SQL SERVER 2012 (before installing Sharepoint 2013)

Now do what is mention in this post: Starting/Running SQL SERVER 2012 (SQL Permissions) for SharePoint 2013

Now you have your whole SQL Server ready, so you can install SharePoint 2013.

Determine your SQL Server Version, Service Pack, and Edition

To determine the version of SQL Server, you can use any of the following methods:

Method 1

Connect to the server by using Object Explorer in SQL Server Management Studio. After Object Explorer is connected, it will show the version information in parentheses, together with the user name that is used to connect to the specific instance of SQL Server.

Method 2

Connect to the instance of SQL Server, and then run the following query:

Select @@version

An example of the output of this query is as follows:

Microsoft SQL Server 2008 (SP1) – 10.0.2531.0 (X64)   Mar 29 2009 10:11:52
Copyright (c) 1988-2008 Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )

Method 3

Connect to the instance of SQL Server, and then run the following query:

SELECT SERVERPROPERTY(‘productversion’), SERVERPROPERTY (‘productlevel’), SERVERPROPERTY (‘edition’)

Note This query works with any instance of SQL Server 2000 or later

The following results are returned:

• The product version (for example, 10.0.1600.22)
• The product level (for example, RTM)
• The edition (for example, Enterprise)

For example, the results resemble the following:

10.0.1600.22 RTM Enterprise Edition

Note The SERVERPROPERTY function returns individual properties that relate to the version information, although the @@VERSION function combines the output into one string. If your application requires individual property strings, you can use the SERVERPROPERTY function to return them instead of parsing the @@VERSION results.

VERSION INFORMATION

SQL Server 2012 version information

The following table lists the major releases of SQL Server 2012:

Release	Product Version
SQL Server 2012 Service Pack 1	11.00.3000.00
SQL Server 2012 RTM	11.00.2100.60

SQL Server 2008 R2 version information

The following table lists the major releases of SQL Server 2008 R2:

Release	Product version
SQL Server 2008 R2 Service Pack 2	10.50.4000.0
SQL Server 2008 R2 Service Pack 1	10.50.2500.0
SQL Server 2008 R2 RTM	10.50.1600.1

SQL Server 2008 version information

The following table lists the major releases of SQL Server 2008:

Release	Product version
SQL Server 2008 Service Pack 3	10.00.5500.00
SQL Server 2008 Service Pack 2	10.00.4000.00
SQL Server 2008 Service Pack 1	10.00.2531.00
SQL Server 2008 RTM	10.00.1600.22

SQL Server 2005 version information

The following table lists the major releases of SQL Server 2005:

Release	Product version
SQL Server 2005 Service Pack 4	9.00.5000.00
SQL Server 2005 Service Pack 3	9.00.4035
SQL Server 2005 Service Pack 2	9.00.3042
SQL Server 2005 Service Pack 1	9.00.2047
SQL Server 2005 RTM	9.00.1399

SQL Server 2000 version information

The following table lists version number of the Sqlservr.exe file:

Release	Product version
SQL Server 2000 Service Pack 4	8.00.2039
SQL Server 2000 Service Pack 3	8.00.760
SQL Server 2000 Service Pack 3	8.00.760
SQL Server 2000 Service Pack 2	8.00.534
SQL Server 2000 Service Pack 1	8.00.384
SQL Server 2000 RTM	8.00.194

For more information, please refer to Microsoft KB321185 – How To Identify your SQL Server Service Pack Version and Edition.

Ref : lumension

Resolving VS 2010 solution deployment issues for SharePoint 2010 projects

In my new SharePoint 2010 book, I touch base on variety of deployment approaches; in this article I wanted to focus on Visual Studio 2010 feature allowing to deploy SharePoint 2010 solutions right to the portal. However, you haven’t configured your development environment properly – you will run into issues. Here I’m talking about the following error:

Error occurred in deployment step ‘Recycle IIS Application Pool’: The local SharePoint server is not available. Check that the server is running and connected to the SharePoint .

Or this:

Error occurred in deployment step ‘Recycle IIS Application Pool’: Cannot connect to the SharePoint site: http://localhost/. Make sure that this is a valid URL the SharePoint site is running on the local computer. If you moved this project to a new computer or if the URL of the SharePoint site has changed since you created the project, update the Site URL property of the project

Visual studio uses the following process to deploy your solution: vssphost4.exe
Open your task manager and find the process in the list; take a note of the User Nameunder which this process is running, let’s say it’s myadmin_account

Now, open your SQL Management Studio and ensure this Username is added as a DBOWNER to the following databases:

SharePoint_Config
SharePoint_AdminContent_[guid]
SharePoint Site Content DB

Close and Open your Visual Studio again, this will ensure the service is recycled; this should fix above deployment error. If you’re still having same issue, End the process in taskmanager and then VS 2010.

Good luck!

Ref : Sharemuch

How to access deleted rows in a typed dataset?

Sometimes after doing some processing on a dataset and before finally committing the changes in the database we need to know some information about added, modified, deleted or dispatched rows in the dataset. One of the well known approaches  is to loop the rows of a data set and check the ‘RowState’ value of each row which could be added, modified, deleted or dispatched. But when you are using a transaction in your code then you will notice that after updating the changes in database and before committing the transaction you will lose the deleted rows although you will still be able to get the rowstate of added and modified rows. This was irritating for me as i wanted to get the count of deleted rows in my code. The fortunately i came accross another nicer method of accessing added, modified, deleted and dispatched rows which is Table.GetChanges(‘RowsState’). In this way you can separately make tables for each kind of rows and then use them for your purpose. Here is an example of ‘Customer’ table.

 DataTable tableAddedRows, tableModifiedRows, tableDeletedRows, tableDispatchedRows;

tableAddedRows = myDataSet.tables[“Customer”].Rows()[0].Table.GetChanges( DataRowState.Added );
tableModifiedRows = myDataSet.tables[“Customer”].Rows()[0].Table.GetChanges( DataRowState.Modified);
tableDeletedRows = myDataSet.tables[“Customer”].Rows()[0].Table.GetChanges( DataRowState.Deleted );
tableDispatchedRows = myDataSet.tables[“Customer”].Rows()[0].Table.GetChanges( DataRowState.Dispatched);

Now you can use these tables to do whatever you want. Please note that if there is no row of any one of these rowstates then its corresponding table will be null.

Ref : Zee Malik

Best Practices to follow before installing a SQL Server Service Pack

1.  Perform a full backup of all User, System and Resource database.

2. Note down of the important SQL Server Configuration Settings, Startup Parameters, Linked Servers, and Script out SQL Server Agent Jobs, Script out SQL Server Logins, Memory Utilization, CPU and Disk Utilization etc.

3. Create an appropriate Service Pack Deployment and Rollback Plan

4. Always install Service Packs first in Development environment and then test all applications which are using SQL Server.

5. Once everything looks good in development environment, then only install Service Pack in QA environment. Test all applications which are using SQL Server in QA environment and also test your rollback plan.

6. If everything look good in both Development and QA environment then plan to install Service Pack in a Production environment by communicating an appropriate downtime window to the stake holders and database/application users.

7. Once the Service Pack is installed successfully in a Production environment perform sanity checks to confirm all applications are working fine.

8. Reboot the SQL Server once Service Pack / Cumulative Updates or a Security Updates are applied successfully on the server.

9. If everything looks goods then release the Production environment for user activities and monitor the environment closely for a week or two to make sure there are no unusual spikes in CPU and Memory utilization.

“There is insufficient system memory in resource pool ‘internal’ to run this query”

During Initial versions(RTM) of SQL 2008 and R2 I have observed multiple posts related to the error “There is insufficient system memory in resource pool ‘internal’ to run this query”.

Mostly the error comes up if a Full Text Query is ran which uses compound words,however the same error comes up on different situations too and there was a BUG which was opened for this case too

http://connect.microsoft.com/SQLServer/feedback/details/484787/there-is-insufficient-system-memory-in-resource-pool-internal-to-run-this-query

The good news is that SQL Server Product team have fixed this issue and if you are facing this error in your systems(RTM) right now,then you can go ahead and deploy the latest service pack for SQL Server 2008 and R2.

SP3 for SQL Server 2008 –

http://www.microsoft.com/download/en/details.aspx?id=27594

SP1 for SQL Server 2008 R2 –

http://www.microsoft.com/download/en/details.aspx?id=26727