* ExecuteReader
* ExecuteNonQuery
* ExecuteScalar

.NET Framework is around for 5 years already now, but these 3 methods are among the most misused in application development. The problem is that ExecuteReader will work for every query via SqlCommand, so most people use it everywhere. The direct result – slow and non-scalable solution. Other results include database bottlenecks, locks and connection leaks.

So I decided to provide a small cheat-sheet that clearly demonstrates when to use each method.

ExecuteReader

Do not use: when database query is going to provide for sure exactly 1 record. It may be getting record by its id (which is PK in the database) – GetOrderById and such. In this case use ExecuteNonQuery with output parameters.

Use: when database query is going to provide a set of records. It may be search or report.

ExecuteNonQuery

Use: when we are talking about a single database record – in Update, Insert, Delete and Get by Id. In all these cases we can use input/output/input-output parameters. Please note that from the application architecture point of view it is also good practices when your Insert and Update stored procedure returns changed record exactly like Get By Id method does.

ExecuteScalar

Do not use: when database query returns a single value and this value can be defined as parameter in T-SQL. ExecuteNonQuery with output parameter(s) is always preferred in this case since it is more flexible, tomorrow there will be 2 values therefore having ExecuteNonQuery we do not need to change method signatures.

Use: when database query returns a single value and this value cannot be defined as output parameter, because of T-SQL type limitation for variables. For example type image cannot be output parameter in MSSQL.

The most common example for ExecuteScalar is fetching a single image stored in the database and converting it to array of bytes. If you google it – most examples will demonstrate using of ExecuteReader to accomplish image handler, however ExecuteScalar will be more scalable and faster.

Conclusion

Always use ExecuteNonQuery except: when you have a set of records – use ExecuteReader and when you have a single output value that cannot be defined as a parameter – use ExecuteScalar. Hope this helped to clarify something.

GOTO > Start > Run > RegEdit

GOTO > HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\<version>\ProjectMRUList
remove unnecessary items from list.

Similarly repeat the steps for FileMRuList
GOTO > HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\<version>\FileMRUList
remove unnecessary items from list.

To Clear the Find and Replace List
GOTO > HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\<version>\Find
remove unnecessary items from list.

devenv /installvstemplates

This will rebuild your item and project template cache

Another Option is

Open the Options window in Visual Studio.
Select Projects and Solutions.
Change the Visual Studio user item template location to the folder where the standard templates are located ( C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\ItemTemplates ).

2.  Now go to “C:\Inetpub\wwwroot\wss\VirtualDirectories\80\” directory and create one folder name “CustomWebPage”

 3. Compile you aspx page and copy your aspx page to the “C:\Inetpub\wwwroot\wss\VirtualDirectories\80\CustomWebPage” folder

4. Now copy your asp.net app dll to the “C:\Inetpub\wwwroot\wss\VirtualDirectories\80\bin\” folder

5. You are done, now can brows your page http://yourmachineName:defaultport(inwhich sharepoint is running) / CustomWebPage/YourPage.aspx

6. Now you can create a simple WebPart and deploy it in the share point, i the web part you can give the link for your aspx page

Now for AJAX integration with MOSS, you have to brows this link, it will explain you steps to integrate AJAX

http://sharepoint.microsoft.com/blogs/mike/Lists/Posts/Post.aspx?ID=3

1) http://directory.google.com/Top/Science/Educational_Resources/ then scroll down the page and you would find

Click on Submit a Site

2) Now you would have to enter the credentials and submit your site. Wait for like 1-2 weeks and your site would come up in the google or any other search engine sites

2. Click All Programs.

3. Go into Accessories.

4. Right-click on Command Prompt.

5. Select Run as administrator.

6. When the UAC Prompt appears, click Continue.

Once you have your elevated command prompt, input the following:

msiexec /a filepath to MSI file /qb TARGETDIR=filepath to target folder

example: msiexec /a c:\downloads\sqlserversamples.msi /qb

1. Click `Start` button > `Control Panel` > `Add or Remove Programs`
2. Click `Add/Remove Windows Components`
3. Highlight `Application Server`
4. Click `Details`
5. Make sure `ASP.NET` is checked
6. Click `OK`

Now you need to register this version of ASP.NET with IIS.

1. Click `Start` button > `Run`
2. Type `cmd`
3. Click `OK`
4. Type `cd C:\WINNT\Microsoft.NET\Framework\v1.1.4322`
5. Press `Enter` key
6. Type `aspnet_regiis.exe -i`
7. Press `Enter` key

This will install and register ASP.NET v1.1.4322 with IIS.

At this point try to reinstall SRS Standard Edition and see if you can bypass the error message. If the error message still appears there is one more thing you can do.

Still Getting ASP.NET 1.1 Error Messages After Registering ASP.NET v1.1?
I had this problem too after registering ASP.NET with IIS. After browsing my installed programs I noticed that I now had ASP.NET versions 1.1 and 2.0 on my machine. After searching the Internet I found that there is an installation log file for SRS that might give some more information.

C:\Program Files\Microsoft SQL Server\80\RS Setup Bootstrap\Log\*.cab

In this file you are looking for the following:

<Prerequisite Name="IsASPNET4322Installed" Checked="Registry" Item="HKLM\SOFTWARE\Microsoft\ASP.Net\RootVer"
Found="Can not get value" Expected="1.1.4322.x" Result="Fail" />

Now simply open Registry Editor (`Start` > `Run` > Type `regedit` > `OK`) and browse to the ASP.NET folder by using the path from above and check to see what (if any) root version you have. Make sure that the `RootVer` value is `1.1.4322.0` and close Registry Editor. Now try reinstalling SRS Standard Edition.

Original savior: Jon Swoveland via Google Groups

Permissions issues
Now after successfully installing SRS things should go smoothly right? Well for me: wrong, completely wrong. If you are new to SRS (and don’t have networking experience) then you are probably falling into an endless pit of permissions-issues. The following instructions are for setting up SRS in a way similar to my installation.

First you need to disable anonymous access to the ReportServer and Reports applications.

1. Click ‘Start’ > ‘Run’
2. Type ‘inetmgr’ > ‘OK’
3. Click ‘Default Website’ (could be different depending on your setup)
4. Right-click ‘Reports’ application > ‘Properties’ > Click ‘Directory Security’ tab > Click ‘Edit’
5. Uncheck ‘Enable anonymous access’
6. Check ‘Integrated Windows authentication’
7. Click ‘OK’ > Click ‘OK’
8. Right-click ‘Reports’ application > ‘Permissions’
9. Highlight the user that will access the reports (Most likely Domain\I_USR) – If user doesn’t exist Click ‘Add’ > ‘Advanced’ > ‘Find Now’ > Select the users > ‘OK’ > ‘OK’
10. Give this user (check) everything but ‘Full Control’ and ‘Special Permissions’ (just to be safe!)
11. Repeat the steps above for the ‘Report Server’ application

Now it’s time to create permissions in SQL Server. You will need to remember all the users that you added above. While we are on the subject this would be a good time to create a Group (i.e. SQLReportUsers) and add users to it. This way instead of adding multiple users each time you create a new report you could simply add that user (or users) to the Group and they will inherit the permissions. Feel free to configure however you want though.

1. Open Enterprise Manager
2. Click ‘Your_Server_Name’ > ‘Security’ > ‘Logins’
3. Create new logins for the users you granted permissions to above
4. Right-click ‘Logins’ > ‘New Login’ > Click ‘…’ button > Select user/users > Click ‘OK’
5. Make sure ‘Windows Authentication’ is selected
6. Make sure the appropriate domain is selected
7. Make sure ‘Grant access’ selected
8. Select ‘ReportServer’ for the default database
9. Click ‘Database Access’ tab
10. Select (check) all the databases this user needs to access (everything the Report Service touches)
11. For each database selected make sure that you select at least: ‘public’, ‘db_datareader’, ‘db_datawriter’
12. Open the database that includes the stored procedure used to generate the report
13. Click ‘Users’ > Right-click the login > ‘Properties’ > Click ‘Permissions’ button
14. Scroll down to the stored procedure object and make sure that the ‘Exec’ column is checked
15. Make sure the user has ‘Exec’ privileges on any other relevant stored procedures

Time to Configure the Reports in Report Manager
Upon installing SQL Reporting Services there will should be a folder called ‘SQL Reporting Services’ in the ‘Start’ > ‘All Programs’ > ‘Microsoft SQL Server’ directory. In this folder you should find the ‘Report Manager’ shortcut. Opening this takes you to the Report Manager homepage. From here you can edit existing reports, publish new reports, and most importantly: configure report security and user roles. If you are still getting permissions-related issues then this module is where you would hopefully correct the problem(s).

The permissions granted to user 'DOMAIN\user' are insufficient for performing this operation.

That error threw me off for the longest time. I performed all of the operations above and still had no luck. Here are insructions for how I solved this problem via Report Manager.

1. Navigate to the report you are configuring by drilling down to the folder where the .rds and .rdl file(s) reside.
2. Click ‘Properties’ tab (top navigation bar)
3. Click ‘Security’ tab (on left navigation bar)
4. Click ‘New Role Assignment’ (top navigation bar)
5. Type ‘Group_or_Username_From_Above’ in the ‘Group or user name’ textbox
6. Select ‘Browser’ for the role (May view folders, reports and subscribe to reports) > click ‘OK’
7. Click ‘ReportFileName’
8. Click ‘Properties’ tab (top navigation bar)
9. Repeat above steps

Update Your web.config File Accordingly
This was the crucial piece to the puzzle for me. I had the authentication section set correctly but forgot to include the authorization section in my web.config! I was impersonating the user correctly but said user wasn’t allowed. Don’t let this happen to you.

<system.web>

<authentication mode=”Windows” />
<identity impersonate=”true” />

<authorization>
<deny users=”?” />
<allow users=”*” />
</authorization>

</system.web>

Related: Authentication, Role-based Security, and SQL Reporting Services Web Service

Hopefully now SRS will work for you from your web applications. Feel free to post questions or e-mail me and I will try my best to respond with a fix or something close to it!

1. In Control Panel, click Programs, and then double-click Programs and Features.
2. In the User Account Control dialog box, click Continue.
3. Click Turn Windows features on or off.
4. In the Windows Features dialog box, expand Internet Information Services, expand Web Management Tools, expand IIS 6 Management Compatibility, and then click to select the following check boxes:
   • IIS 6 WMI Compatibility
   • IIS Metabase and IIS 6 configuration compatibility
5. Expand World Wide Web Services, expand Application Development Features, and then click to select the following check boxes:
   • ASP.NET
   • ISAPI Extensions
   • ISAPI Filters
6. Expand Common HTTP Features, and then click to select the following check boxes:
   • Default Document
   • Directory Browsing
   • HTTP Errors
   • HTTP Redirection
   • Static Content
7. Expand Security, and then click to select the Windows Authentication check box.

Note If you do not enable all these features, the Reporting Services option does not appear in the Feature Selection dialog box of the SQL Server Setup program.

Zoom is another IE specific feature available only to IE

Copy and paste this into the Run Command from the Start Menu.
%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i

This will reinstall asp.net for use with IIS and in most cases fixes the error stated above.