Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.ms-sqlserver    |    Notorious Rube Goldberg contraption    |    19,505 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 18,143 of 19,505    |
|    =?windows-1252?Q?Arne_Vajh=F8j?= to Erland Sommarskog    |
|    Re: Extracting Image datatype content wi    |
|    04 Mar 11 19:36:14    |
      XPost: microsoft.public.dotnet.languages.csharp       From: arne@vajhoej.dk              On 04-03-2011 12:18, Erland Sommarskog wrote:       > Arne Vajhøj (arne@vajhoej.dk) writes:       >>>> I am well aware that the image datatype (as well as others) are being       >>>> phased out in some future version of SQL Server. For that reason, in       >>>> all of my personal C#.NET projects that store images use the       >>>> varbinary(max) datatype.       >>       >> That is what the docs says.       >>       >> I am somewhat skeptical about how soon it will happen.       >>       >> Using *var*(max) for new stuff absolutely makes sense.       >>       >> But I would hurry slowly to convert existing code.       >       > Given how much simpler the MAX data types are over text/image/ntext I see       > all reason to change existing code. At least if you run into one of the       > many quirks with the old data types.              That is an OK reason to change. It can sometimes be frustrating.              I am a lot more skeptical about the datatypes disappearing       in SQLServer 2012 (or 2015 for that matter). It would just       create too much chaos.              Arne              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca