Sorry GSquared.

Thanks SSCarpal Tunnel, I will try your suggestions!

Great advise

Thanks Michelle

Just so I'm clear on this, you all think that SQL should be able to handle 300 unique inserts per second and still be able to handle queries run against...

Thanks Michelle, will do.

Yeah..I know what u mean about adding a second table.

I guess I was thinking that the (#1) insert table would have no indexes or pkeys, and the (#2) searchable...

I haven't seen it yet, But I'm told it's diagnostic data. Users, transactions, searches that sorta thing. The table only has about 10 columns tho, fwiw.

Yes, they are querying...

You guys are right.

I tried it and it was no real benefit.

Thanks very much for your time, and knowledge.

Thanks Noel.

I was really just going to give it a shot and see what happens.

Here's the proc, sorry it's a long one..

Can anyone tell me where the hint would go?

ALTER...

Thanks everyone, very informative.

I meant to write back sooner, but have been busy with your suggestions.

Thanks again, you all rock.

Okay here ya go...

Here's the table & the indexes..

CREATE TABLE [dbo].[EventItems_rob](

[LogId] [int] NOT NULL,

[Company] [varchar](50) NOT NULL,

[CompanyId] [int] NOT NULL,

[Department] [varchar](50) NOT NULL,

[DepartmentId] [int] NOT NULL,

[CompanyCRN] [varchar](50) NOT NULL,

[DepartmentCRN] [varchar](50)...

Thanks Jeff

Thanks Matt

It would be far more efficent if you put the values that are in the function into a look-up table and then use a join to update the values...

Thanks for the quick replys.

I'm thinking I should create a new table with state, county, abbrev...