Forum Moderators: open
Currently I am storing the .plan in the DB as varchar(7500). Which is a limited amount of data I can have in the DB for that field....and we can't have that right?! So I am strongly considering to switching that field to Datatype: 'image'. image datatypes are not fixed and they are basically a binary field that isn't fixed. So is there a reason at all that I SHOULDn't be using this change that I want to do? I figure that my tool will be doing all of the conversions before hand so there is no performace hit. But I am going to be using an ASP.NET web site and if I make the change in the DB I have to pull from the DB and convert the Binary to a string to be able to display it.
So Is there really a difference on the ASP.NET side? I would think that it would actually increase performance because that would be one less step for the TCPIP stack to do...because it eventually get converted to binary at some point. So any thoughts or suggestions would be great.
[databasejournal.com...]
Those data types are varaible length as well and that is what I am looking for on a large scale.
Well I can't thank you enough...and I have learned something today.