Databases
StackOverflow2013
Postsdbo
POUpgrading SQL Server 6.5
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUpgrading SQL Server 6.5
    primarykey
    data
    text
    <p>Yes, I know. The existence of a running copy of <code>SQL Server 6.5</code> in 2008 is absurd.</p> <p>That stipulated, what is the best way to migrate from <code>6.5</code> to <code>2005</code>? Is there any direct path? Most of the documentation I've found deals with upgrading <code>6.5</code> to <code>7</code>.</p> <p>Should I forget about the native <code>SQL Server</code> upgrade utilities, script out all of the objects and data, and try to recreate from scratch?</p> <p>I was going to attempt the upgrade this weekend, but server issues pushed it back till next. So, any ideas would be welcomed during the course of the week.</p> <p><em>Update. This is how I ended up doing it:</em></p> <ul> <li>Back up the database in question and Master on <code>6.5</code>.</li> <li>Execute <code>SQL Server 2000</code>'s <code>instcat.sql</code> against <code>6.5</code>'s Master. This allows <code>SQL Server 2000</code>'s OLEDB provider to connect to <code>6.5</code>.</li> <li>Use <code>SQL Server 2000</code>'s standalone <code>"Import and Export Data"</code> to create a DTS package, using <code>OLEDB</code> to connect to 6.5. This successfully copied all <code>6.5</code>'s tables to a new <code>2005</code> database (also using <code>OLEDB</code>).</li> <li>Use <code>6.5</code>'s Enterprise Manager to script out all of the database's indexes and triggers to a .sql file.</li> <li>Execute that .sql file against the new copy of the database, in 2005's Management Studio.</li> <li>Use 6.5's Enterprise Manager to script out all of the stored procedures.</li> <li>Execute that <code>.sql</code> file against the <code>2005</code> database. Several dozen sprocs had issues making them incompatible with <code>2005</code>. Mainly <code>non-ANSI joins</code> and <code>quoted identifier issues</code>.</li> <li>Corrected all of those issues and re-executed the <code>.sql</code> file.</li> <li>Recreated the <code>6.5</code>'s logins in <code>2005</code> and gave them appropriate permissions.</li> </ul> <p>There was a bit of rinse/repeat when correcting the stored procedures (there were hundreds of them to correct), but the upgrade went great otherwise.</p> <p>Being able to use Management Studio instead of <code>Query Analyzer</code> and <code>Enterprise Manager 6.5</code> is such an amazing difference. A few report queries that took 20-30 seconds on the <code>6.5 database</code> are now running in 1-2 seconds, without any modification, new indexes, or anything. I didn't expect that kind of immediate improvement.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPaulMcG
    1. USDave Ward
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUpgrading SQL Server 6.5
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POUpgrading SQL Server 6.5
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POUpgrading SQL Server 6.5
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload