views:

515

answers:

4

I want to save an object (of any type) into a field in a database in SQL Server 2005. Is it possible? Do I have to convert the object into something, like a byte array for example and cast it back when retrieving it?

+1  A: 

To do this you need to serialize your object. You can look here at examples:

http://www.c-sharpcorner.com/UploadFile/bipinjoshi/serializingObjectsinCS11102005234746PM/serializingObjectsinCS.aspx

Thinker
But I don't want to save it on hard disk. I just want to put it in a databse.
Ahmad Farid
BinaryFormatter is a **very bad choice** for long term storage.
Marc Gravell
+2  A: 

You can use the VARBINARY(MAX) field type in SQL Server, if you like. You can store any type of object in there, up to 2 GB in size.

To access it, you can use ADO.NET - something like this:

object yourMysteryObject = (whatever you like it to be);

MemoryStream memStream = new MemoryStream();
StreamWriter sw = new StreamWriter(memStm);

sw.Write(yourMysteryObject);

SqlCommand sqlCmd = new SqlCommand("INSERT INTO TableName(VarBinaryColumn) VALUES (@VarBinary)", sqlConnection);

sqlCmd.Parameters.Add("@VarBinary", SqlDbType.VarBinary, Int32.MaxValue);

sqlCmd.Parameters["@VarBinary"].Value = memStream.GetBuffer();

sqlCmd.ExecuteNonQuery();

Marc

marc_s
but how can i transfer an object into a VARBINARY type?
Ahmad Farid
but this is an image read from a file. What if I have a class or an object created during runtime. Nothing to do with files.
Ahmad Farid
any type of object can be written to a MemoryStream and thus assigned to the value of the SqlParameter which will then write it down into the database.
marc_s
how can i write an object to a memory stream? without dealing with the hard disk? can u give me an example plz?
Ahmad Farid
Look at my code - create a MemoryStream and a StreamWriter and write your object to this MemoryStream -- that's all done in memory, no disk
marc_s
LOL @ yourMysteryObject :D thx dude :)and when retrieving it back, normal type casting right?
Ahmad Farid
Well, if you want it back, you'll have to know what you get back! SQL Server is just going to send you any number of bytes - it's YOU who has to know what it is and how to convert the stream of bytes into an object again.
marc_s
oh what do you mean. I know that it is, I mean its type. Can't I just say like:DataTable dt;while(reader.Read()){ dt = (DataTable)reader[2];}
Ahmad Farid
+2  A: 

As others have said, serialization may be the key here (assuming you don't want to use ORM to store the properties as columns in a table, which seems much more direct).

Some caveats though; a database is:

  • long term storage
  • not related to your .NET code

As such, you do not want to use any serialization technique that is platform-specific or version-specific. You will often see people mention BinaryFormatter for persistance, but this falls into both of the above traps. You would be scuppered if you ever changed platform, or even if you just change some properties.

You need an implementation-independent approach; the simplest (which also retains the ability to be human readable) is xml or json, perhaps via XmlSerializer or Json.NET (stored in a [n]varchar(max)). If you don't care about human readable, "protocol buffers" (fast/binary) would do well (stored in a varbinary(max)), and is available for most platforms (including C#/.NET/etc).

Marc Gravell
+1  A: 

I would use JSON to convert the object to a string, and store it in a VARCHAR or TEXT field. Not only the data is stored in a human-readable format, but it's also also readable from different languages, since pretty much every mainstream language has a JSON parser available.

The link I posted has links to several libraries in many languages (including C#), I have used this one a couple times in the past.

Badaro