ASP.NET
  Home arrow ASP.NET arrow Page 2 - Developing a Data Access Layer for Sybase ...
ASP Free Forums 
.NET  
ASP  
ASP Code  
ASP.NET  
ASP.NET Code  
BrainDump  
C#  
Code Examples  
Database  
Database Code  
IIS  
Microsoft Access  
MS SQL Server  
Visual Basic.NET  
Windows Scripting  
Windows Security  
XML  
ASP Web Hosting  
ASP.NET Web Hosting 
Mobile Linux 
App Generation ROI 
Windows Web Hosting
 
IBM® developerWorks 
Sun Developer Network 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
ASP.NET

Developing a Data Access Layer for Sybase Using ADO.NET: Essentials
By: Jagadish Chaterjee
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 5 stars5 stars5 stars5 stars5 stars / 8
    2006-03-20

    Table of Contents:
  • Developing a Data Access Layer for Sybase Using ADO.NET: Essentials
  • Configuring Sybase for data access using ADO.NET
  • The Constructor in the Data Access Layer
  • Getting a table (or data table) of information from Sybase database using ADO.NET
  • Getting a single value from Sybase database using ADO.NET

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    Developing a Data Access Layer for Sybase Using ADO.NET: Essentials - Configuring Sybase for data access using ADO.NET


    (Page 2 of 5 )

    To work with a Sybase database using ADO.NET natively, we need to have a Sybase database installed on our computer.  If the database exists on another server, then we need to install “Sybase client” (or “pc-client”) which is freely downloadable from Sybase's website.

    You need to select a custom installation during the installation of Sybase client.  You need to “switch on” all ODBC, OLEDB and ADO.NET components during the custom installation of Sybase client (to activate the full use of ADO.NET).  The installation also includes some samples of VB.NET solutions for getting connected with the Sybase database. You can have a trial run using those samples for testing connections, datasets, and so on.

    The following are the core DLLs of Sybase that deal with data access using ADO.NET:

    Sybase.Data.AseClient.dll
    sybdrvado11.dll
    sybdrvssl.dll

    Of all of the above DLLs, we will work with only the assembly “Sybase.Data.AseClient.dll” (which indeed works with the rest of the DLLs) in ADO.NET.  It is always suggested to copy all of the three into the “bin” folder of your ASP.NET application (for instance, if you are developing a web application).  You also need to add a reference to “Sybase.Data.AseClient” from the “.NET components” (and not from the “bin” folder) to your application, if it needs any data access to the Sybase database.

    Another most important issue is that the files “sybdrvado11.dll” and “sybdrvssl.dll” should also be copied into the folder “C:windowsassemblygacSybase.Data.AseClient
    1.1.327.0__26e0f1529304f4a7”.  The folder is not directly visible from Windows Explorer.  You need work with “Run” or “Command Prompt” to go to that folder and copy the files specified.  This is a step that everyone tends to forget. 

    Once the above is properly configured, your .NET applications can easily interact with the Sybase database.  A sample connection string (make it into a single line) to get connected to Sybase would be as follows:

    Data Source='172.28.4.175';
    Port='5000';UID='sa';PWD='';Database='databasename'

    You need to modify the above connection string based on the configurations of the Sybase server.  If you are not very familiar with such configurations, you need to consult your Sybase database administrator or system administrator. 

    It is always suggested that you have your connection string in “Web.Config” (if using web forms) or “app.config” (if using Windows forms).  You can encrypt the connection string, if you don’t want it to be simply readable.

    The “web.config” file may look something like the following:

    <?xml version="1.0" encoding="utf-8"?>
    <configuration>
        <appSettings>
        <add key="ConnectionString" value="Data
    Source='dbServernameORipaddress';Port='PortNo';UID='sa';
    PWD='';Database='databasename'
    "/>
        </appSettings>
      <system.web>
          .
          .
          .

    The next section will start with developing the DAL.

    More ASP.NET Articles
    More By Jagadish Chaterjee


       · Hello guys. In this article, I am introducing you to develop your own datahelper (or...
     

    ASP.NET ARTICLES

    - Developing a Mini ASP.NET AJAX Server Centri...
    - Disadvantages of the ASP.NET MVC Framework
    - Advantages of the ASP.NET MVC Approach
    - ASP.NET Web Forms Weaknesses
    - ASP.NET Web Forms Meets ASP.NET MVC
    - Source Code for Saving and Retrieving Data w...
    - Using GridView to Save and Retrieve Data wit...
    - Handling Dynamic Images in ASP.NET 3.5 AJAX ...
    - Retrieving Data with AJAX and the GridView C...
    - Playing with Images in ASP.NET 3.5 AJAX Appl...
    - Saving and Retrieving Data with AJAX
    - Enhancing PHP Via the ASP.NET AJAX Framework...
    - Enhancing PHP Programming with the ASP.NET A...
    - Classes and ASP.NET AJAX
    - Using ASP.NET AJAX

     
    Best Practices for Windows Vista Migration Presentation
    Dell and Microsoft recently held a series of face-to-face seminars entitled, &qu....

     
    Creating a Culture for Code Reuse
    If you oversee development teams you know that like it or not proprietary and ex....

     
    Keys to Web Application Acceleration: Advances in Delivery Systems
    Accelerate Web apps by up to 5x. Ensure significantly faster access to the Web a....

     
    Optimizing Application Monitoring
    Tired of finding out from your customers that you're offline? This white paper e....

     
    Solaris to Solaris Migration -- Migrating applications from Sun SPARC to Dell PowerEdge R900
    This comprehensive Migration Guide reviews the approach that Principled Technolo....

     




    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 6 hosted by Hostway
    Stay green...Green IT