by Robert Wait » Thu, 16 Nov 2000 04:00:00
Initially, I was going to merge them to eliminate a join for performance.
Question: Is it better to leave them split? What if the data in the second
were changed everyday?
Thanks to all in Advance.
Robert Waite
by Doo » Thu, 16 Nov 2000 04:00:00
However, unless there is some REAL GOOD reason to split a table into a 1-1
relationship I wouldn't do it. Why make work for yourself?
Yes, JOINs cost resources...how much depends on how many times you do it.
--
Doo
Senior Data Architect / DBA
PlanetJam Media Group
Quote:> I am moving a client's database from Access to SQL Server 2000. Employee
> info (10 fields) is split into two linked tables (one-to-one). Data in one
> is rarely changed and only with admin priviledges. Data in the other is
> occasionally changed by the employee.
> Initially, I was going to merge them to eliminate a join for performance.
> Question: Is it better to leave them split? What if the data in the second
> were changed everyday?
> Thanks to all in Advance.
> Robert Waite
1. SQL 7 Performance & Table Structure
Please pardon this elementary question - but I am being
told that if a table in a SQL 7 database has more than 6
columns, that Db performance will be compromised. I
cannot believe that this is the case. Does anyone have
any / know where I can get information on this topic to
bring to this person's manager?
Thanks,
Jordanna
2. Error Type: Microsoft OLE DB Provider for SQL Server (0x80004005) Timeout expired
3. Table join performance & datatypes
4. osql
5. NEEDED: BETTER JOIN PERFORMANCE ON BIG TABLE WITH BIG INDEXES (NESTED LOOPS AND MERGE JOINS)
6. Need to restore data from Mentor (NCR - MOE) 8mm filesave.
7. performance on SELECT-statement joining 3 tables?
8. Cannot create MFC recordset using Oracle 9i and Visual Studio .NET
9. Join performance after 7.0 Upgrade (>10 tables)
10. Slow Performance with Joined tables
11. improving join performance on huge tables