-
I have a big table with around 50 columns. I've to upload it to a SQL Server 6.5 and then write an asp page to search the records. Since SQL 6.5 has a limit on the length of a row, I've to vertically partition my table into 2. These two tables have exactly the same number of records and a common ID column. Now when I'm writing the ASP page, is it better to join to two tables and do the query, or open another recordset for the 2 tables? In other words, is it more expensive to join two tables or open a recordset? Thanks!
-
Hi HMCheung,
I think, joining two tables will be more expensive than creating a new recordset.
Cheers
