Database

KORCARI wrote: Is this possible to merge data from table1 table2 table3 in a SQL database without creating problems with ID colums of each table Yes. Add a column called "sourceDatabaseName", make it part of the primary key, and when importing write the name of the database that you're importing into that column. If you're moving a lot of data, then this would be the time to consider upgrading to Sql Server (express) :) I are Troll :suss:

But why use a stored procedure at all? Just do the same thing but in regular code.

OK Deal :cool: thatraja |Chennai|India| Brainbench certifications Down-votes are like kid's kisses don't reject it :-) Do what you want quickly because the Doomsday on 2012 :-)

search[^] :) Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

Connectionstring.com [^]is an excellent resource for this information Never underestimate the power of human stupidity RAH

digicd1 wrote: Thank you for your reply My pleasure, I hope you don't mind me rambling on about the importance of normalizing too much. It may eat away a bit of your time, but it's well worth the investment. digicd1 wrote: In summary it appears that using a database that is too normalized would really affect cpu time. A database can't be "too" normalized. A "good" level of normalization would be BCNF[^]. That should give you a correct model, without (much) redundancy. Keep in mind that most RDBMS-es are optimized to work with relational data, in a relational format. digicd1 wrote: it would be better to have some information duplicated vs. slowing the entire system down That sounds like a statement on optimization again :) I are Troll :suss:

What if it's in hex? :-D At a previous job of mine, the company stored 64-bit IDs in strings as hex (in RDB*) and there was no native way of converting them back and forth within the database, you had to fetch the data out and then work on it (in C). Eventually I wrote functions (like CLR extended stored procedures in SQL server) to do it. * Which still doesn't support 64-bit integers?

You're welcome. "When did ignorance become a point of view" - Dilbert

Hi Ray, it was a pleasure helping you out. My database experience is young and limited (I'm more a reader than a writer in this forum), however at the start this looked like a challenge I might just be able to cope with and certainly would learn from. And I tend to like potential win-wins. See you. :) Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

Manish_84 wrote: Convert Image field in Varbinary(Max) It'd be 'sweet' if you could create a hash to represent your image, and store that in a column next to the image itself :) I are Troll :suss:

You're welcome. :) Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

jrahma wrote: how can id o the same in mySQL stored procedure? select sequence_name_goes_here.currval from dual; There's an example both on using sequences and returning values in the manual over here[^] :) I are Troll :suss:

which version of SQL server are you using? As barmey as a sack of badgers Dude, if I knew what I was doing in life, I'd be rich, retired, dating a supermodel and laughing at the rest of you from the sidelines.

Thanks Pete.. just Google'd that and as its part of the report services I might be rethinking that part that I was going to use notification services As barmey as a sack of badgers Dude, if I knew what I was doing in life, I'd be rich, retired, dating a supermodel and laughing at the rest of you from the sidelines.

Try UUID Niladri Biswas

Cheers will do As barmey as a sack of badgers Dude, if I knew what I was doing in life, I'd be rich, retired, dating a supermodel and laughing at the rest of you from the sidelines.

Thanks again! Great article - definitely helped me understand.

Excellent answer! I was about to same the same thing.

I'd either store it as a number (in seconds), or as two datetimes. I are Troll :suss:

Well your error message suggest the problem. Close all applications using the database you want to restore. Close all SSMS windows using the database you want to restore. And when you are running restore query use master database. Try to read the error messages in all cases. That will help you understand any problem.