Re: Upsizing from Access doubles varchar columns
From: Robert Schuldenfrei (schuldenfrei_at_comcast.net)
Date: 02/18/05
- Next message: --CELKO--: "Re: One table versus two tables"
- Previous message: languy: "Re: exists rowguidcol on table?"
- In reply to: David Portas: "Re: Upsizing from Access doubles varchar columns"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 18 Feb 2005 10:12:43 -0500
Hi David & NG,
Thanks again for your sagely advice and insight. Clearly I was a victim of
taking the easy way out. I had this Access application that I had done to
prototype an MRP II COBOL system. Without much knowledge of SQL Server, C#,
or Crystal Reports I stumbled upon Upsizing as a great way to get a running
start with my project. Foolish me... Actually, I have learned a lot. This
NG has been particularly helpful. But, as the old saying goes: "Experience
is a great teacher, but she teaches a hard school." Fortunately, I am doing
this as a hobby and there is no deadline hanging over my head.
I think what I am going to do is scrap the old tables and start over. I am
going to think about it over the weekend before I do something rash. I
really do need to think about the tables and their relationships. Not all
of the tables have been built at this point and I need to proceed in an
orderly manner least I get further down the road and run into something else
that may cause me to rip up and start over.
Cheers,
Bob
-- Robert Schuldenfrei S. I. Inc. 32 Ridley Road Dedham, MA 02026 bob@s-i-inc.com 781/329-4828 "David Portas" <REMOVE_BEFORE_REPLYING_dportas@acm.org> wrote in message news:1108732465.722915.280820@f14g2000cwb.googlegroups.com... > If you don't need unicode columns then change them all to non-unicode > (VARCHAR, CHAR, TEXT). This is trickier than it sounds because indexes > on those columns have to be recreated - not difficult for one or two > columns, harder if there are many dependent objects. If you are still > in development and happy to drop and recreate everything then the > easiest way is probably be to generate a table creation script (All > Tasks > Generate Script in Enterprise Manager), search and replace all > the references to NVARCHAR, NCHAR and NTEXT then re-run the script. > Take a backup before you do this please! Obviously you'll have to > recreate any data but you will hopefully have mechanisms to do that > anyway in development. > > I'm not a fan of Upsizing Wizards. It is unwise to assume that a schema > design in Access will also be appropriate for SQL Server. The best way > is to review what you have and redesign where necessary. > > -- > David Portas > SQL Server MVP > -- >
- Next message: --CELKO--: "Re: One table versus two tables"
- Previous message: languy: "Re: exists rowguidcol on table?"
- In reply to: David Portas: "Re: Upsizing from Access doubles varchar columns"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
