saving SSIS package

Hi,
Let me know if this is possible...
We have a SQL 2000 SP3a cluster on Windows 2003 Server that is inside our
network.
We have a SQL 2005 server, that is also our web server, out in the DMZ.
We are trying to copy some tables from a database on our SQL 2000 cluster,
out to the SQL 2005 server. We want this to happen every night.
So from his workstation, our db admin, installed the SQL 2005 tools, started
creating an SSIS package, didn't save it, and it copied the tables out to
the server, no problem. However, he created the SSIS package again, this
time tried to save it to the SQL2000 server, so that he could schedule it to
run every night.
This makes sense that you cannot save an SSIS package to an SQL2000 server.
How do we get around this?
Note: the web server cannot be allowed to initiate the table copy. In
other words, the data can only be Pushed from the inside, not Pulled from
the DMZ. So what is the best way for us to copy tables from SQL2000 to the
SQL2005 server?
Thanks in advance!SSIS packages differ a lot from DTS ones, so you would need a completely
different tables in SQL 2000 msdb. You can save the SSIS package into file
system of the SQL 2000 server and use SQL 2005 DteExec command-prompt
utility (replaces DTSRun) to execute the package from the SQL 2000 server.
--
Dejan Sarka, SQL Server MVP
Mentor, www.SolidQualityLearning.com
Anything written in this message represents solely the point of view of the
sender.
This message does not imply endorsement from Solid Quality Learning, and it
does not represent the point of view of Solid Quality Learning or any other
person, company or institution mentioned in this message
"JJP" <anonymous@.discussions.microsoft.com> wrote in message
news:uHFefvEHGHA.2836@.TK2MSFTNGP14.phx.gbl...
> Hi,
> Let me know if this is possible...
> We have a SQL 2000 SP3a cluster on Windows 2003 Server that is inside our
> network.
> We have a SQL 2005 server, that is also our web server, out in the DMZ.
> We are trying to copy some tables from a database on our SQL 2000 cluster,
> out to the SQL 2005 server. We want this to happen every night.
> So from his workstation, our db admin, installed the SQL 2005 tools,
> started creating an SSIS package, didn't save it, and it copied the tables
> out to the server, no problem. However, he created the SSIS package
> again, this time tried to save it to the SQL2000 server, so that he could
> schedule it to run every night.
> This makes sense that you cannot save an SSIS package to an SQL2000
> server. How do we get around this?
> Note: the web server cannot be allowed to initiate the table copy. In
> other words, the data can only be Pushed from the inside, not Pulled from
> the DMZ. So what is the best way for us to copy tables from SQL2000 to
> the SQL2005 server?
> Thanks in advance!
>

SAN abreviation

Hi all,
Can anyone light the question what is the difference between System Area
Network (mentioned in SQL Server EE features) and Storage Area Network.
Or i should advice ms to change abreviation in BOL ...System Area Network is basically a replacement to IP or NetBEUI. Consider a small network with
perhaps only two computers (your SQL Server and your web server). No need to carry the heavy IP
protocol on this, use something which is "closer to the metal". System Are Network is such, and if
you are running Enterprise Edition or Developer Edition of SQL server, you have such netlib: ViaSAN.
You probably know what Storage Area Network is already, and this is what we generally mean when we
say "SAN". If you don't know what SAN is, let us know.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Eli Milkova" <EliMilkova@.discussions.microsoft.com> wrote in message
news:6C6ECE6B-21D4-465F-8023-8C26C4B7E26E@.microsoft.com...
> Hi all,
> Can anyone light the question what is the difference between System Area
> Network (mentioned in SQL Server EE features) and Storage Area Network.
> Or i should advice ms to change abreviation in BOL ...
>|||Thank you ...precious answer...thanks
"Tibor Karaszi" wrote:
> System Area Network is basically a replacement to IP or NetBEUI. Consider a small network with
> perhaps only two computers (your SQL Server and your web server). No need to carry the heavy IP
> protocol on this, use something which is "closer to the metal". System Are Network is such, and if
> you are running Enterprise Edition or Developer Edition of SQL server, you have such netlib: ViaSAN.
> You probably know what Storage Area Network is already, and this is what we generally mean when we
> say "SAN". If you don't know what SAN is, let us know.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Eli Milkova" <EliMilkova@.discussions.microsoft.com> wrote in message
> news:6C6ECE6B-21D4-465F-8023-8C26C4B7E26E@.microsoft.com...
> > Hi all,
> > Can anyone light the question what is the difference between System Area
> > Network (mentioned in SQL Server EE features) and Storage Area Network.
> > Or i should advice ms to change abreviation in BOL ...
> >
> >
>