hmm good question. My knee jerk reaction would be to union the tables together (probably make a view) and do a fuzzy grouping to find the grouping of common customers.(

I agree with Mr Dougherty, in a perfect world we would not want or need to do this. Unfortunately when you get patients in the ER, getting a correct spelling...

Depending on how big your production system is (# users, transactions ...) I would also recommend you either take a copy of you DB and work "offline" or build an...

I agree, the fewer number of fields you check, the less likely you are to exclude someone due to a spelling (or name change ...) error. If you feel the...

Did anyone happen to see this http://autos.msn.com/advice/article.aspx?contentid=4024682

The comparison is between 92 vehicles and today. The big take home is that obesity is a problem for our cars (as well...

I suspect it is the Workload Governor in MSDE that is killing your performance. You can test the by running the following in a SQL window (during a busy time):

DBCC...

We don't VM SQL Server for the reasons above (I/O, Grabbing CPU...) We did review and are discussing with our software vendors - PolyServe as a method of reducing our SQL Servers...

I'm not sure this is the best way, but here goes. This is dependent on your data being exactly as you state above where each record has 2 rows! First...

I work for a hospital - definitly not smart - but caring. Actually I think all the crap we have to do to process a bill to someones insurance is...

I don't think its dead, but its unnecessary. My degrees are in Forest Management. During grad school I spent more time making databases, writing FORTRAN, building COBOL reports and sysadmin...

I guess I've lost the value you are looking for in creating an index on this table. Since you have no control over the writes to it (IIS is in charge!), what...

I really don't think you will get too much performance increase out of indexes on this table. Mainly because, except for date and time, most of the values in the...

This is obviously a log file from a web server, so the table setup is probably the default log created by IIS when you choose ODBC logging. I've done a lot...

Are you using fuzzy lookup or fuzzy grouping?

Your stuck with 1 ID column. Could you build a view and concatenate the fields, then rip apart after the grouping?

You may want to review the network topology of the SAN. The SAN may be faster (typically you have way more spindles so writes can be broken up into small...