Re: SQLVariant and indices
From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 09/29/04
- Next message: rick: "Re: NULL Records"
- Previous message: Tibor Karaszi: "Re: Error 87 from GetProxyAccount on line 604"
- In reply to: Adam Machanic: "Re: SQLVariant and indices"
- Next in thread: Adam Machanic: "Re: SQLVariant and indices"
- Reply: Adam Machanic: "Re: SQLVariant and indices"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 29 Sep 2004 19:02:42 +0200
My guess is stuffing different types of things in one column... :-)
-- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ "Adam Machanic" <amachanic@hotmail._removetoemail_.com> wrote in message news:uy1w7aipEHA.3252@TK2MSFTNGP14.phx.gbl... > Michael, > > Could you post DDL for some of your current tables and DDL for what you're > suggesting? I'm having a difficult time understanding what your situation > is, or what you think you might gain from using the SQL_VARIANT datatype. > > > "Michael Zdarsky" <zdarsky@zac-it.com.(nospamplease)> wrote in message > news:FC06F017-3D12-4223-B835-2691BF4DD74A@microsoft.com... >> Hello, >> >> we have a high generic database design with some table for each data type >> like int, real, ... >> >> now we think about to merge some of them into one table with sqlvariant as >> its column type. >> >> Now my questions: >> >> How wil the index be organised on an sqlvariant? >> >> What are pros and cons for sqlvariants, despite the always to cast > problem? >> >> Greettings. >> Michael > >
- Next message: rick: "Re: NULL Records"
- Previous message: Tibor Karaszi: "Re: Error 87 from GetProxyAccount on line 604"
- In reply to: Adam Machanic: "Re: SQLVariant and indices"
- Next in thread: Adam Machanic: "Re: SQLVariant and indices"
- Reply: Adam Machanic: "Re: SQLVariant and indices"
- Messages sorted by: [ date ] [ thread ]