Forum Replies Created

Viewing 11 posts - 1 through 12 (of 12 total)

  • RE: Database connection loss

    I am sure you can use the disconnected feature of ADO.NET implemented using Datasets.

    You can store all the data in the dataset and then in the end post all the...

    You have to dig for tons of dirt to get an ounce of Gold

  • RE: SqlConnection.ConnectionString parts

    Starrting with SQL Server 2000. It is possible to have more than one instance of sql server on a single windows server. These instances are isolated from one another, they...

    You have to dig for tons of dirt to get an ounce of Gold

  • RE: SqlConnection.ConnectionString parts

    I am sure you are trying this with SQl server 2000.

    The connecting string should be

    sConn = "Provider=sqloledb;Data Source=myServerName\myInstanceName;Initial Catalog=myDatabaseName;User Id=myUsername;Password=myPassword"

    You have to dig for tons of dirt to get an ounce of Gold

  • RE: Flattening several rows into one row

    You can create a UDF for returning the third column. The UDF would accept claimID  as the parameter and would loop to create a string separated with commans.

    e.g. SELECT Claim.Claim_ID,Cust_Name,Entry_Date,UDF(CLaimID)

       group...

    You have to dig for tons of dirt to get an ounce of Gold

  • RE: interesting query

    While using wild chaaracters one needs to use the escape characters while using symbols like % and [. Look in BOL for the syntax for I am not recollecting it...

    You have to dig for tons of dirt to get an ounce of Gold

  • RE: URGENT - Problem with read commited isolation level

    The Problem lies in how sql server handles locking mechanism. If sql server feels that placing 4 row locks would be more resource intensive than placing a single page lock...

    You have to dig for tons of dirt to get an ounce of Gold

  • RE: MSAccess --> SQL Server Migration

    One major difference is the way date is handled, MS-Access uses # for dates while SQl server uses single quotes.

     

     

    You have to dig for tons of dirt to get an ounce of Gold

  • RE: Arrays in TSQL ?

    One more option I can remember is using the charAt function.

    You have to dig for tons of dirt to get an ounce of Gold

  • RE: Update sql table from another sql table

    I guess you can use linked table features provided in access database. this would ensure that you have the data from the sql...

    You have to dig for tons of dirt to get an ounce of Gold

  • RE: Value in Trigger

    You can use scope_identity for finding the last Id that was inserted.Also look in BOL for difference between @@identity and @@scope_identity

    You have to dig for tons of dirt to get an ounce of Gold

  • RE: Trigger on invalid ID

    Normally it's best to autogenerate the primary keys use identity columns if you are not in any way allowing users of your application to use them directly. You can define...

    You have to dig for tons of dirt to get an ounce of Gold

Viewing 11 posts - 1 through 12 (of 12 total)