Eric M Russell (2/14/2012)

---

The full Oracle client is a monster, and server admins are sometimes reluctant about intalling it. If all you need is connectivity for a linked server connection...

Matt Miller (#4) (2/14/2012)

---

ACtually - using an ORDER BY during the insert would guarantee the ID's be generated in the correct order. Conor Cunningham confirmed that to be true...

Well, the OP...

Rachel Byford (2/14/2012)

---

I have now got it working nicely using a sub-package to do the work on each pass through the loop.

If you can suggest a better way, however, I'm...

chandrika.r 91171 (2/14/2012)

---

Sorry for the Confusion

I am getting a time out issue when I am running my SSIS package through SQL Job. In the SSIS package I have a simple...

ID is an identity column, you shouldn't try to force it into a specific order.

Furthermore, it is useless to specify an ORDER BY on an INSERT.

ORDER BY Clause (Transact-SQL)

When used...

Indeed. For example, the databases on one server, the webservices on another web server and so on...

This article doesn't tell me much more than MSDN.

I would have liked a more in-depth discussion on some configuration topics, such as the service account (using a built-in one -...

Hugo Kornelis (2/14/2012)

However, it is not true that ;WITH will cause errors when all statements are semicolon terminated. There is no limit to how many semicolons you use and where...

And a happy valentine for you as well.

Glad to be part of this community.

kll 51891 (2/14/2012)

---

I would have expected it to fail due to no newline or semicolon.

But it were not so

Anywhere I can find specific rules about when to use and...

No problem, glad to help.

Maybe you could verify the backup first before dropping the database, just to make sure you don't run into...

Indeed! :w00t:

I'm missing the answer "after waiting for a few hours you eventually decide to go home..."

You need to create dynamic SQL for this using the EXEC statement (or sp_executeSQL).

Your statement would become:

CREATE PROCEDURE [dbo].[BackUpDatabase]

@BackupFilePath VARCHAR(200) = 'C:\DbBackup\SQ2005\', -- path for backup db

@DatabaseName VARCHAR(100) = 'DBTEST',...

Great question, thanks Henrico.

I stumbled across this issue a few times too many, so a real easy one for me 🙂