July 19, 2004 at 9:06 am
When our db was upsized some time ago, the sql server upsizer converted our Access text columns to nvarchar.
We do not have any unicode requirements so it seems pointless having these columns set to nvarchar.
Does the act of just changing the datatype for the these columns to varchar, change the size requirements for the fields within the db or is there more to it than that.
Note that the intention is to do a straight swap of for example nvarchar(50) for varchar(50).
Thanks,
Kevin.
Windows 2008 Server | SQL Server 2008
July 19, 2004 at 9:44 am
I did this a couple of month ago.
It doesn't change anything. Before doing so I checked my data to be sure nothing changes (my database is in french), and nothing changed.
All it will do is take less space. But, as always, be sure to have a good backup before doing any change.
Erik
July 19, 2004 at 9:52 am
Less space used sounds good to me.
Can I take it that you ran no other procedure to recover this space?
Windows 2008 Server | SQL Server 2008
July 20, 2004 at 1:10 am
Running the usual maintenance stuff should be sufficient.
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
July 20, 2004 at 9:27 am
That's what I did, I let the maintenance plan run as usual.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply