jh71283 said:

Have you thought about SQL Server Compact Edition

Matthew van Eerde said:

ferguslogic said:

*snip*

Yeah this question screams "dynamically built SQL" to me.

My suggestion: sanitize the input in the CGI to be word-ish tokens seperated by, oh, say, commas: @input = 'foo,bar,baz'

Then write T-SQL to loop over the input and build up the WHERE clause:
WHERE field like '%foo%' or field like '%bar%' or field like '%baz%'

Even without full-text searching, this should be doable if you have some good hardware, not very many tickets, and relatively infrequent queries.

spivonious said:

ferguslogic said:

*snip*

Oh, I thought this was for an application on top of the database, not in the database itself. :doh:

No this is a  sql serve stored procedure.

No full text indexing because this is a hosted database at a  webhost using sql server express with no full text indexing available.

spivonious said:

We run Oracle over here, so I can't help you if any SQL server functions exist for this, but why not just build the where clause dynamically?  Split the textbox.text on a space and loop through each one adding another "OR field LIKE blahblah" each time.

Dim searchItems() as String = textbox.text.Split(" ")

For Dim i as Integer = LBound(searchItems) to UBound(searchItems)
    whereClause &= " OR tick.descriptionStripped LIKE '%" & searchItems(i) & "%' "
Next

where

tick.descriptionStripped like '%' + @piSearchText + '%'

or tick.title like '%' + @piSearchText + '%'

or tick.ticketnumber like '%' + @piSearchText + '%'

or tick.keywords like '%' + @piSearchText + '%'

where

tick.descriptionStripped like '%rainy%'  or tick.descriptionstripped like  '%day%'

thank you so much. I really appreciate it.

System.Data.OleDb.OleDbConnection cn =DataHelper.GetConnection();

System.Data.OleDb.OleDbCommand cmd = cn.CreateCommand();

int numberOfRowsAffected = 0;

I went to a command prompt.

I navigated to c:\windows\system32

I ran msdtc - install

that installed Msdtc and the service now appears under the "services" area.  Everything appears to work fine now.

I have no idea why it was not installed.

The computer is running.
You have permissions to administer the computer.
The computer name is correct.

--------------------------------------------------------------------------


If I click on the "com+" folder under component services i receive this message.
-------------------------------
An error occurred while processing the last operation.
Error code 8004e00F - Com+ was unable to talk to the Microsoft Distributed Transaction
Coordinator

The event log may contain additional troubleshooting information.
---------------------------------

The event log does not contain any information and I am pretty stumped.  I double checked my  username and I am a member of the administrator group.  Any help is really appreciated.

thanks
Matt

 

using (TransactionScope ts = new TransactionScope())

aEntity.save();  //opens connection to database A
bEntity.save();  //also opens connection to database A

When MSDTC is utilized, MSDTC is turned off by default on XP home and Pro. (At least it appears to be on my development box - xp pro). 

So on my first transaction my application errors out until MSDTC is requested 1 time. After the first request MSDTC starts or "spins up" in COM+  and all subsequent calls work.  If I reboot the system MSDTC will stop and the first call to MSDTC errors out again for me.

If my users have to connect to another computer on a small LAN they have to enable MSDTC remote and incoming connections and even when I do that I can't seem to get remote MSDTC connections to work.  You have to ensure firewalls are disabled and that MSDTC can pass through firewalls if they are still enabled etc. etc. it is a huge nightmare.

My users are mechanics, book keepers and small business owners. They download our software from our website to try it out.

I am not going to take support call after support call trying to help non technical users configure MSDTC so that they can savea  customer record. 

Microsoft doesn't appear to have any way to programmatically configure MSDTC (maybe I am missing some .net assembly to do this somewhere)

It  just seems like such a huge hassle to try to deploy your application today as a Microsoft ISV.  I can't imagine making my users go through all this configuration just to network 2 computers together.

So thats my 2 cents on the new TransactionScope, Distributed Transactions and MSDTC anyway. I am going back to passing SQlTransaction objects around so my users don't have to deal with this administration nightmare of MSDTC configuration.

Can you imagine making mechanics, book keepers and other non technical users  have to configure MSDTC everytime they want to hook up a second computer? I just can't see it.

I am developing a simple C# 2.0 application. It is a winform app which is ran on small networks.  The app is divided in typical fashion into 3 logical layers UI, business and data. Pretty straight forward.

In C# 2.0 I can't seem to locate a good way to handle transaction management between layers.

Here is an example:

User needs to save an order.

Business Tier Code example #1

public int SaveOrder(Order myOrder)
{
       //verify the order meets our business requirements prior to saving
       Validate(myOrder)

       // make 2 calls to the Data Access Layer
        int orderId = DALOrder.SaveOrder(myOrder)
        DALOrderItems.SaveOrderItems(myOrder);
        return orderId;
}

Each Data Access method above is located in seperate class modules and each method opens and closes its own connection to the database.

Because the business tier is calling mutliple Data Access methods in the data tier, I need to create a transaction in the business tier and utilize this transaction across all of the data layer methods. Upon success the business tier can then commit the transaction.

Today I am handling this like so:

Business Tier Code example #2

public int SaveOrder()
{
       SqlConnection myConnection = DataHelper.GetConnection();
       SqlTransaction transaction = myConnection.BeginTransaction();

       try()
        {

       // makes 2 calls to the Data Access Layer, pass the transaction
        DAL.SaveOrder(order,transaction)
        DAL.SaveOrderItems(order,transaction);
        transaction.Commit();
         }
         catch(System.Exception)
         {
                  transaction.RollBack();
         }
         finally
         {
            myConnection.Close();
         }
}

In order for this to work my data access layer methods now have to accept a transaction parameter, look at the transaction parameter being passed and utilize the connection property of that transaction object (transaction.Connection) to connect to the database instead of opening and closing their own connections.

So if a transaction is not passed, the methods  open and close their own connection, otherwise they use Transaction.Connection and do not close a connection at all.

This works okay, but it is kind of messy.

I am looking for an easier way to handle transactions.
Perhaps, one that does not require me to pass a sqlTransaction object as a parameter to every single Data Access Layer Save, Update or delete method.

For example, what happens now if the above SaveOrder() business tier method needs to be called by the SaveCustomer() method and the SaveCustomer() method needs to be the transaction root.  Today the SaveOrder() method is hardcoded as the root and always begins a transaction each time it is fired so should that situation arrive, our current methodology may fail.

I am looking for someone who has faced this issue who can offer advice on how  to handle transactions between business and data tier layers of an application.

These layers today are logical only and all reside on the same server.

Microsofts examples seem to be simplified samples and only seem to  show you how to manage transactions in the same layer or even worse..the same exact function.  They do talk a bit about how to handle multiple connections to multiple databases (Distributed transactions) but that does not apply here.  I have multiple connections to the same exact database.

Any advice is greatly appreciated.

thank you in advance