Maybe I misread your initial post. Are you pulling from Oracle into SQL or the other way around?

All of your queries should be set to pull from your source,...

Hi,

I'm glad you appreciated the effort on that post.

To answer your questions:

1. This is the correct flow. You want the SQL statement to be set to the query you...

This is a link to the MS Technical Reference Guide for upgrading:

http://www.microsoft.com/downloads/details.aspx?FamilyID=66d3e6f5-6902-4fdd-af75-9975aea5bea7

there is a lot of information there.

I have attached a checklist that I put together based on...

that recommendation should work for you unless you get to a point where the variable cannot hold everything you need.

In that case, you'll need to use a script task, pass...

excellent script for 2005. Thanks for the post.

Steve

just an idea, and i don't know if its a good one or not, but couldn't you deny access to the tables to everyone except the account running the update?

declare...

one way that i have done this is to do the import through an SSIS package. Within the SSIS package, you can create a variable, and then you can...

this is a tricky topic. connecting to SSIS from SSMS is also another tricky scenario with regards to ssis security.

we like to store all ssis packages within msdb so...

great script. can certainly use this as a supplement to cluster monitoring that i have in place at my company. in case we miss an alert for a...

I've done it both ways with success 🙂

One way or another- the error message that gets generated if you forget to leave it in norecovery is not very intuitive.

While this might not be the same problem I had, please review this info and see if it helps you:

Try this:

Take a fresh backup (in full recovery) on the primary...

I had this similar problem.

Try this:

Take a fresh backup (in full recovery) on the primary DB.

Restore the DB on the mirrored location (MAKE SURE TO SPECIFY NORECOVERY).

Try starting your mirroring...

One important part of the code that I didn't post was causing the issue:

...Imports...

#Region " Global Variables "

Dim m_errorMessage As String = ""

...

A quick internet search returned a whole bunch of results:

http://www.lcard.ru/~nail/sybase/perf/1088.htm

http://manuals.sybase.com/onlinebooks/group-as/asg1250e/ptallbk/@Generic__BookTextView/8455

http://bytes.com/topic/sql-server/answers/637874-denormalized-database-inquiry

Basically, repeated data and referential integrity (mentioned above) are the main reasons.

To the query, the NDF file wouldn't even really matter. It is an administrative function to logically separate out tables and data.

In SQL 2005, you can do table partitioning...