Database

Perhaps this discussion will help you, http://social.msdn.microsoft.com/Forums/en/sqldatabaseengine/thread/711614c8-e67d-4137-8f46-3187ac0ce363[^] Why is common sense not common? Never argue with an idiot. They will drag you down to their level where they are an expert. Sometimes it takes a lot of work to be lazy Individuality is fine, as long as we do it together - F. Burns

You could put the database on a virtual drive[^] and crypt that. When moving the database, move the virtual drive. Bastard Programmer from Hell :suss:

To really understand how to solve this problem, you must know what commands are executed against your database. One way to solve this issue is to turn on CASCADE UPDATE in your foreign key definition.

You can link[^] servers within SSMS. Once set up, you can query both servers in a single statement, by prefixing the server-name before the database-name. Bastard Programmer from Hell :suss:

Gr8 sir .. it worked .. you made my weekend :) ... I wish you a wonderfull weekend. :)

I suspected something like that was happening. I've never used optimizer hints before; I will look into that. Thanks for the tip. :thumbsup:

Did you try to write query before you ask here? In your previous question you took good answers which are valid for your question which you are asking. I Love T-SQL "VB.NET is developed with C#.NET" If my post helps you kindly save my time by voting my post.

What you need is a common table expression[^] which is recursive processing of a table. This may not be correct as your structure seems to be rigid (you know how many level to the top) and therefor you simply do a bunch of inner joins. Select * From Fruit Inner join Category on Category.CategoryID = Fruit.CategoryID Inner Join level2.ID = Category.Level2.ID ... Never underestimate the power of human stupidity RAH

You're rather presumptuous. Although there are situations in which products and category have a many to many relationship, there are many real world situations in which a product belows to one category.

Also, check out EXCEPT http://weblogs.sqlteam.com/jeffs/archive/2007/05/02/sql-server-2005-using-except-and-intersect-to-compare-tables.aspx[^] Scott

If it's going to be a regular operation I open a Connection to each database, use a DataReader to read from one, and ExecuteNonQuery to INSERT into the other. A major benefit of this technique is that it allows the app to periodically log its progress (and speed in rows per minute) so you're not flying blind. This technique also allows you to catch and ignore selected Exceptions if you like and not have the whole process die.

Thanks, but I've uninstalled and re-installed SQL Server now and it's all working fine.

The answer to #2 is: HAVING Authors LIKE %SearchString% Thanks for the help... ***************** "We need to apply 21st-century information technology to the health care field. We need to have our medical records put on the I.T." —GW

You should probably repost this one in the Asp.net forum as it doesn't seem to have much to do with databases. Light moves faster than sound. That is why some people appear bright, until you hear them speak. List of common misconceptions

Only one instance with the name of the database is allowed on the server. Detach the database that's connected, or use an other name. Bastard Programmer from Hell :suss:

Simple; you ask the database-administrator. He'll know which database-application is installed. Each manufacturer has it's own implementation, and you can find examples for all major vendors on the internet. Happy searching :) Bastard Programmer from Hell :suss:

vanillaET wrote: There are two databases with the same data structure. One database is ok to insert that record, but another is not ok for data type conversion. I've checked all the data fields.Please give me any suggestion to solve it. Check the data-fields again. You're inserting something that cannot be converted, might be a text in a bit or a datetime field. Try logging all values that are going to be inserted, and have the app mail the offending values using a try-catch block. Next, simply try the offending values using your original insert-statement trough the Sql Management Studio. Bastard Programmer from Hell :suss:

This[^]may help

Did u check the amount of data the procedure is returning. In case the procedure is returning too many rows of data, then that might be the cause of timeout when you run the procedure programmatically. But when you run the same procedure from database itself which i guess is Sql Management studio, only top 500 or 1000 rows would be returned depending on the SSMS setting. Hence the result comes up without time out.