changeing the table name while using transfer sql server object

Hi,
I am wondering using transfer sql server objects task in a sub-package and feeding tableslist property from the parent package. which works fine.
problem :

I want to be able to change the name in the fly so if I have
TableA I want to copy it for the destination as TableB
is there any work arround this just using transfer sql server objects task.
Thanks

A link to a similar thread of yours on this topic: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1094010&SiteID=1|||Thanks Phil for checking.
Although it is similar question but it is pointing to a different functionality of Transfer sql server object task.
I want to be able to copy a table between servers the tricky part is that I don not have the table in the destination and task creates the table in the target server.

so it captures a snapshot of the schema of the source table and applies it to the remote server and the then standard data copy between to tables.

problem: I want to be able to have a different table name for the target database. so I am wondering if it is possible with scripting to do so ( that is fi the task it self has got such a property ) or the task only will create the table with the same name (as the source).

Thanks
|||Just asking and am not trying to take away from your issue, but aren't there better tools for performing schema management rather than using SSIS? I'm not a DBA, so I don't really know the answer to that question, but it seems here that you're stretching the limits of what SSIS was designed to do (even if it *can* do it).

Are you going to run this one time, or many times?|||many times and con-currently
|||Not supported in the Transfer Objects task. However, you could use an Execute SQL after the table is copied to call sp_rename.|||yes, that's how I've done it , but I was wondering if there was a a nyway to stretch the Transfer sql server object task capability.
Cheers

Changeing Remote ports

I have two instances of SQl 2005 running on a server. One I'm going to allow outside remote access to. But I don't want to do it on the default port. though I have it allowing remote and that seems to be working. I can seem to find where to change the default listening port.

and I scimmed the help and topics I saw. But didn't see one relevant to this question.

Open the Server Configuration Manager > Protocols for [InstanceName] > TCP/IP Properties > TCP Port > Restart the service

Jens K. Suessmeyer.

http://www.sqlserver2005.de

Changeing default value of tempdb

Hi All
For one of our SQL server 2000 database tempdb size is origionally set to
"8KB"(That is default value). After monitoring it for some time, I think we
need to change the default value to "650 KB".
Can I change the default value while the server is online (so that on next
reboot it automatically changes) or I need to reboot the server.
In any case what is the best way and commands to do this?
Thanks
Hi db
Where are you getting this value from? Are you sure you don't mean MB?
In any case, you can change the tempdb startup size with the ALTER DATABASE
command, to change the size of the primary file. Look up ALTER DATABASE in
the Books Online, and read about the MODIFY FILE option for the details
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://sqlblog.com
"db" <db@.discussions.microsoft.com> wrote in message
news:4F42449A-8D85-4287-906A-5B90F3AA115A@.microsoft.com...
> Hi All
> For one of our SQL server 2000 database tempdb size is origionally set to
> "8KB"(That is default value). After monitoring it for some time, I think
> we
> need to change the default value to "650 KB".
> Can I change the default value while the server is online (so that on next
> reboot it automatically changes) or I need to reboot the server.
> In any case what is the best way and commands to do this?
> Thanks
> --
>
|||I got the values from Best practice analyzer tool results for sql server
2000. Also I am monitoring size of tempdb.mdf/ldf files on the disk. Few
months back tempdb shot up to few GB, but that may be a bad query or
something.
From your response it looks like I need not reboot the server?
Thanks .. go through books on line now.
"Kalen Delaney" wrote:

> Hi db
> Where are you getting this value from? Are you sure you don't mean MB?
> In any case, you can change the tempdb startup size with the ALTER DATABASE
> command, to change the size of the primary file. Look up ALTER DATABASE in
> the Books Online, and read about the MODIFY FILE option for the details
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.InsideSQLServer.com
> http://sqlblog.com
>
> "db" <db@.discussions.microsoft.com> wrote in message
> news:4F42449A-8D85-4287-906A-5B90F3AA115A@.microsoft.com...
>
>
|||> I got the values from Best practice analyzer tool results for sql server[vbcol=seagreen]
> 2000. Also I am monitoring size of tempdb.mdf/ldf files on the disk. Few
> months back tempdb shot up to few GB, but that may be a bad query or
> something.
> From your response it looks like I need not reboot the server?
> Thanks .. I will go through books on line for details.
> --
>
> "Kalen Delaney" wrote:
|||How did you get the value for YOUR tempdb from the BPA tool? How do you know
YOUR tempdb is 8KB?
650 KB is still way too small. Can you elaborate on how you got this value?
Whether or not you need to reboot your server depends on what you want to
accomplish. The default size of tempdb means the size it starts up with,
when you reboot. So if you change the size with ALTER DATABASE, it won't
take affect until you reboot. But if tempdb is large enough for right now,
maybe you don't need to reboot.
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://sqlblog.com
"db" <db@.discussions.microsoft.com> wrote in message
news:A7749815-A31F-453E-BC3F-2839977BA763@.microsoft.com...[vbcol=seagreen]
>I got the values from Best practice analyzer tool results for sql server
> 2000. Also I am monitoring size of tempdb.mdf/ldf files on the disk. Few
> months back tempdb shot up to few GB, but that may be a bad query or
> something.
> From your response it looks like I need not reboot the server?
> Thanks .. go through books on line now.
> --
>
> "Kalen Delaney" wrote:
|||My Typo. Tempdb.mdf file is 655 MB or 670,700 KB on disk. Tempdb is set to
autogrow and it grow from 8MB to 655MB. I do not want to reboot the server
now, but change the default value of tempdb(Whenever reboot happens it should
change) .
Can i change it from
sql enterprise manager --> database-->properties-->datafiles-->space
allocated (Change value here)
"Kalen Delaney" wrote:

> How did you get the value for YOUR tempdb from the BPA tool? How do you know
> YOUR tempdb is 8KB?
> 650 KB is still way too small. Can you elaborate on how you got this value?
> Whether or not you need to reboot your server depends on what you want to
> accomplish. The default size of tempdb means the size it starts up with,
> when you reboot. So if you change the size with ALTER DATABASE, it won't
> take affect until you reboot. But if tempdb is large enough for right now,
> maybe you don't need to reboot.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.InsideSQLServer.com
> http://sqlblog.com
>
> "db" <db@.discussions.microsoft.com> wrote in message
> news:A7749815-A31F-453E-BC3F-2839977BA763@.microsoft.com...
>
>

Changeing default value of tempdb

Hi All
For one of our SQL server 2000 database tempdb size is origionally set to
"8KB"(That is default value). After monitoring it for some time, I think we
need to change the default value to "650 KB".
Can I change the default value while the server is online (so that on next
reboot it automatically changes) or I need to reboot the server.
In any case what is the best way and commands to do this?
Thanks
--Hi db
Where are you getting this value from? Are you sure you don't mean MB?
In any case, you can change the tempdb startup size with the ALTER DATABASE
command, to change the size of the primary file. Look up ALTER DATABASE in
the Books Online, and read about the MODIFY FILE option for the details
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://sqlblog.com
"db" <db@.discussions.microsoft.com> wrote in message
news:4F42449A-8D85-4287-906A-5B90F3AA115A@.microsoft.com...
> Hi All
> For one of our SQL server 2000 database tempdb size is origionally set to
> "8KB"(That is default value). After monitoring it for some time, I think
> we
> need to change the default value to "650 KB".
> Can I change the default value while the server is online (so that on next
> reboot it automatically changes) or I need to reboot the server.
> In any case what is the best way and commands to do this?
> Thanks
> --
>|||I got the values from Best practice analyzer tool results for sql server
2000. Also I am monitoring size of tempdb.mdf/ldf files on the disk. Few
months back tempdb shot up to few GB, but that may be a bad query or
something.
From your response it looks like I need not reboot the server?
Thanks .. go through books on line now.
--
"Kalen Delaney" wrote:
> Hi db
> Where are you getting this value from? Are you sure you don't mean MB?
> In any case, you can change the tempdb startup size with the ALTER DATABASE
> command, to change the size of the primary file. Look up ALTER DATABASE in
> the Books Online, and read about the MODIFY FILE option for the details
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.InsideSQLServer.com
> http://sqlblog.com
>
> "db" <db@.discussions.microsoft.com> wrote in message
> news:4F42449A-8D85-4287-906A-5B90F3AA115A@.microsoft.com...
> > Hi All
> >
> > For one of our SQL server 2000 database tempdb size is origionally set to
> > "8KB"(That is default value). After monitoring it for some time, I think
> > we
> > need to change the default value to "650 KB".
> >
> > Can I change the default value while the server is online (so that on next
> > reboot it automatically changes) or I need to reboot the server.
> >
> > In any case what is the best way and commands to do this?
> >
> > Thanks
> > --
> >
>
>|||> I got the values from Best practice analyzer tool results for sql server
> 2000. Also I am monitoring size of tempdb.mdf/ldf files on the disk. Few
> months back tempdb shot up to few GB, but that may be a bad query or
> something.
> From your response it looks like I need not reboot the server?
> Thanks .. I will go through books on line for details.
> --
>
> "Kalen Delaney" wrote:
> > Hi db
> >
> > Where are you getting this value from? Are you sure you don't mean MB?
> >
> > In any case, you can change the tempdb startup size with the ALTER DATABASE
> > command, to change the size of the primary file. Look up ALTER DATABASE in
> > the Books Online, and read about the MODIFY FILE option for the details
> >
> > --
> > HTH
> > Kalen Delaney, SQL Server MVP
> > www.InsideSQLServer.com
> > http://sqlblog.com
> >
> >
> > "db" <db@.discussions.microsoft.com> wrote in message
> > news:4F42449A-8D85-4287-906A-5B90F3AA115A@.microsoft.com...
> > > Hi All
> > >
> > > For one of our SQL server 2000 database tempdb size is origionally set to
> > > "8KB"(That is default value). After monitoring it for some time, I think
> > > we
> > > need to change the default value to "650 KB".
> > >
> > > Can I change the default value while the server is online (so that on next
> > > reboot it automatically changes) or I need to reboot the server.
> > >
> > > In any case what is the best way and commands to do this?
> > >
> > > Thanks
> > > --
> > >
> >
> >
> >|||How did you get the value for YOUR tempdb from the BPA tool? How do you know
YOUR tempdb is 8KB?
650 KB is still way too small. Can you elaborate on how you got this value?
Whether or not you need to reboot your server depends on what you want to
accomplish. The default size of tempdb means the size it starts up with,
when you reboot. So if you change the size with ALTER DATABASE, it won't
take affect until you reboot. But if tempdb is large enough for right now,
maybe you don't need to reboot.
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://sqlblog.com
"db" <db@.discussions.microsoft.com> wrote in message
news:A7749815-A31F-453E-BC3F-2839977BA763@.microsoft.com...
>I got the values from Best practice analyzer tool results for sql server
> 2000. Also I am monitoring size of tempdb.mdf/ldf files on the disk. Few
> months back tempdb shot up to few GB, but that may be a bad query or
> something.
> From your response it looks like I need not reboot the server?
> Thanks .. go through books on line now.
> --
>
> "Kalen Delaney" wrote:
>> Hi db
>> Where are you getting this value from? Are you sure you don't mean MB?
>> In any case, you can change the tempdb startup size with the ALTER
>> DATABASE
>> command, to change the size of the primary file. Look up ALTER DATABASE
>> in
>> the Books Online, and read about the MODIFY FILE option for the details
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://sqlblog.com
>>
>> "db" <db@.discussions.microsoft.com> wrote in message
>> news:4F42449A-8D85-4287-906A-5B90F3AA115A@.microsoft.com...
>> > Hi All
>> >
>> > For one of our SQL server 2000 database tempdb size is origionally set
>> > to
>> > "8KB"(That is default value). After monitoring it for some time, I
>> > think
>> > we
>> > need to change the default value to "650 KB".
>> >
>> > Can I change the default value while the server is online (so that on
>> > next
>> > reboot it automatically changes) or I need to reboot the server.
>> >
>> > In any case what is the best way and commands to do this?
>> >
>> > Thanks
>> > --
>> >
>>|||My Typo. Tempdb.mdf file is 655 MB or 670,700 KB on disk. Tempdb is set to
autogrow and it grow from 8MB to 655MB. I do not want to reboot the server
now, but change the default value of tempdb(Whenever reboot happens it should
change) .
Can i change it from
sql enterprise manager --> database-->properties-->datafiles-->space
allocated (Change value here)
--
"Kalen Delaney" wrote:
> How did you get the value for YOUR tempdb from the BPA tool? How do you know
> YOUR tempdb is 8KB?
> 650 KB is still way too small. Can you elaborate on how you got this value?
> Whether or not you need to reboot your server depends on what you want to
> accomplish. The default size of tempdb means the size it starts up with,
> when you reboot. So if you change the size with ALTER DATABASE, it won't
> take affect until you reboot. But if tempdb is large enough for right now,
> maybe you don't need to reboot.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.InsideSQLServer.com
> http://sqlblog.com
>
> "db" <db@.discussions.microsoft.com> wrote in message
> news:A7749815-A31F-453E-BC3F-2839977BA763@.microsoft.com...
> >I got the values from Best practice analyzer tool results for sql server
> > 2000. Also I am monitoring size of tempdb.mdf/ldf files on the disk. Few
> > months back tempdb shot up to few GB, but that may be a bad query or
> > something.
> >
> > From your response it looks like I need not reboot the server?
> >
> > Thanks .. go through books on line now.
> > --
> >
> >
> >
> > "Kalen Delaney" wrote:
> >
> >> Hi db
> >>
> >> Where are you getting this value from? Are you sure you don't mean MB?
> >>
> >> In any case, you can change the tempdb startup size with the ALTER
> >> DATABASE
> >> command, to change the size of the primary file. Look up ALTER DATABASE
> >> in
> >> the Books Online, and read about the MODIFY FILE option for the details
> >>
> >> --
> >> HTH
> >> Kalen Delaney, SQL Server MVP
> >> www.InsideSQLServer.com
> >> http://sqlblog.com
> >>
> >>
> >> "db" <db@.discussions.microsoft.com> wrote in message
> >> news:4F42449A-8D85-4287-906A-5B90F3AA115A@.microsoft.com...
> >> > Hi All
> >> >
> >> > For one of our SQL server 2000 database tempdb size is origionally set
> >> > to
> >> > "8KB"(That is default value). After monitoring it for some time, I
> >> > think
> >> > we
> >> > need to change the default value to "650 KB".
> >> >
> >> > Can I change the default value while the server is online (so that on
> >> > next
> >> > reboot it automatically changes) or I need to reboot the server.
> >> >
> >> > In any case what is the best way and commands to do this?
> >> >
> >> > Thanks
> >> > --
> >> >
> >>
> >>
> >>
>
>|||Yes, the change you do in EM will define the new size for tempdb for next startup.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"db" <db@.discussions.microsoft.com> wrote in message
news:936E7677-57D2-4720-A537-84083B502622@.microsoft.com...
> My Typo. Tempdb.mdf file is 655 MB or 670,700 KB on disk. Tempdb is set to
> autogrow and it grow from 8MB to 655MB. I do not want to reboot the server
> now, but change the default value of tempdb(Whenever reboot happens it should
> change) .
> Can i change it from
> sql enterprise manager --> database-->properties-->datafiles-->space
> allocated (Change value here)
> --
>
> "Kalen Delaney" wrote:
>> How did you get the value for YOUR tempdb from the BPA tool? How do you know
>> YOUR tempdb is 8KB?
>> 650 KB is still way too small. Can you elaborate on how you got this value?
>> Whether or not you need to reboot your server depends on what you want to
>> accomplish. The default size of tempdb means the size it starts up with,
>> when you reboot. So if you change the size with ALTER DATABASE, it won't
>> take affect until you reboot. But if tempdb is large enough for right now,
>> maybe you don't need to reboot.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://sqlblog.com
>>
>> "db" <db@.discussions.microsoft.com> wrote in message
>> news:A7749815-A31F-453E-BC3F-2839977BA763@.microsoft.com...
>> >I got the values from Best practice analyzer tool results for sql server
>> > 2000. Also I am monitoring size of tempdb.mdf/ldf files on the disk. Few
>> > months back tempdb shot up to few GB, but that may be a bad query or
>> > something.
>> >
>> > From your response it looks like I need not reboot the server?
>> >
>> > Thanks .. go through books on line now.
>> > --
>> >
>> >
>> >
>> > "Kalen Delaney" wrote:
>> >
>> >> Hi db
>> >>
>> >> Where are you getting this value from? Are you sure you don't mean MB?
>> >>
>> >> In any case, you can change the tempdb startup size with the ALTER
>> >> DATABASE
>> >> command, to change the size of the primary file. Look up ALTER DATABASE
>> >> in
>> >> the Books Online, and read about the MODIFY FILE option for the details
>> >>
>> >> --
>> >> HTH
>> >> Kalen Delaney, SQL Server MVP
>> >> www.InsideSQLServer.com
>> >> http://sqlblog.com
>> >>
>> >>
>> >> "db" <db@.discussions.microsoft.com> wrote in message
>> >> news:4F42449A-8D85-4287-906A-5B90F3AA115A@.microsoft.com...
>> >> > Hi All
>> >> >
>> >> > For one of our SQL server 2000 database tempdb size is origionally set
>> >> > to
>> >> > "8KB"(That is default value). After monitoring it for some time, I
>> >> > think
>> >> > we
>> >> > need to change the default value to "650 KB".
>> >> >
>> >> > Can I change the default value while the server is online (so that on
>> >> > next
>> >> > reboot it automatically changes) or I need to reboot the server.
>> >> >
>> >> > In any case what is the best way and commands to do this?
>> >> >
>> >> > Thanks
>> >> > --
>> >> >
>> >>
>> >>
>> >>
>>

Changeing default value of tempdb

Hi All
For one of our SQL server 2000 database tempdb size is origionally set to
"8KB"(That is default value). After monitoring it for some time, I think we
need to change the default value to "650 KB".
Can I change the default value while the server is online (so that on next
reboot it automatically changes) or I need to reboot the server.
In any case what is the best way and commands to do this?
Thanks
--Hi db
Where are you getting this value from? Are you sure you don't mean MB?
In any case, you can change the tempdb startup size with the ALTER DATABASE
command, to change the size of the primary file. Look up ALTER DATABASE in
the Books Online, and read about the MODIFY FILE option for the details
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://sqlblog.com
"db" <db@.discussions.microsoft.com> wrote in message
news:4F42449A-8D85-4287-906A-5B90F3AA115A@.microsoft.com...
> Hi All
> For one of our SQL server 2000 database tempdb size is origionally set to
> "8KB"(That is default value). After monitoring it for some time, I think
> we
> need to change the default value to "650 KB".
> Can I change the default value while the server is online (so that on next
> reboot it automatically changes) or I need to reboot the server.
> In any case what is the best way and commands to do this?
> Thanks
> --
>|||I got the values from Best practice analyzer tool results for sql server
2000. Also I am monitoring size of tempdb.mdf/ldf files on the disk. Few
months back tempdb shot up to few GB, but that may be a bad query or
something.
From your response it looks like I need not reboot the server?
Thanks .. go through books on line now.
--
"Kalen Delaney" wrote:

> Hi db
> Where are you getting this value from? Are you sure you don't mean MB?
> In any case, you can change the tempdb startup size with the ALTER DATABAS
E
> command, to change the size of the primary file. Look up ALTER DATABASE in
> the Books Online, and read about the MODIFY FILE option for the details
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.InsideSQLServer.com
> http://sqlblog.com
>
> "db" <db@.discussions.microsoft.com> wrote in message
> news:4F42449A-8D85-4287-906A-5B90F3AA115A@.microsoft.com...
>
>|||> I got the values from Best practice analyzer tool results for sql server[vbcol=seagreen]
> 2000. Also I am monitoring size of tempdb.mdf/ldf files on the disk. Few
> months back tempdb shot up to few GB, but that may be a bad query or
> something.
> From your response it looks like I need not reboot the server?
> Thanks .. I will go through books on line for details.
> --
>
> "Kalen Delaney" wrote:
>|||How did you get the value for YOUR tempdb from the BPA tool? How do you know
YOUR tempdb is 8KB?
650 KB is still way too small. Can you elaborate on how you got this value?
Whether or not you need to reboot your server depends on what you want to
accomplish. The default size of tempdb means the size it starts up with,
when you reboot. So if you change the size with ALTER DATABASE, it won't
take affect until you reboot. But if tempdb is large enough for right now,
maybe you don't need to reboot.
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://sqlblog.com
"db" <db@.discussions.microsoft.com> wrote in message
news:A7749815-A31F-453E-BC3F-2839977BA763@.microsoft.com...[vbcol=seagreen]
>I got the values from Best practice analyzer tool results for sql server
> 2000. Also I am monitoring size of tempdb.mdf/ldf files on the disk. Few
> months back tempdb shot up to few GB, but that may be a bad query or
> something.
> From your response it looks like I need not reboot the server?
> Thanks .. go through books on line now.
> --
>
> "Kalen Delaney" wrote:
>|||My Typo. Tempdb.mdf file is 655 MB or 670,700 KB on disk. Tempdb is set to
autogrow and it grow from 8MB to 655MB. I do not want to reboot the server
now, but change the default value of tempdb(Whenever reboot happens it shoul
d
change) .
Can i change it from
sql enterprise manager --> database-->properties-->datafiles-->space
allocated (Change value here)
--
"Kalen Delaney" wrote:

> How did you get the value for YOUR tempdb from the BPA tool? How do you kn
ow
> YOUR tempdb is 8KB?
> 650 KB is still way too small. Can you elaborate on how you got this value
?
> Whether or not you need to reboot your server depends on what you want to
> accomplish. The default size of tempdb means the size it starts up with,
> when you reboot. So if you change the size with ALTER DATABASE, it won't
> take affect until you reboot. But if tempdb is large enough for right now,
> maybe you don't need to reboot.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.InsideSQLServer.com
> http://sqlblog.com
>
> "db" <db@.discussions.microsoft.com> wrote in message
> news:A7749815-A31F-453E-BC3F-2839977BA763@.microsoft.com...
>
>|||Yes, the change you do in EM will define the new size for tempdb for next st
artup.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"db" <db@.discussions.microsoft.com> wrote in message
news:936E7677-57D2-4720-A537-84083B502622@.microsoft.com...[vbcol=seagreen]
> My Typo. Tempdb.mdf file is 655 MB or 670,700 KB on disk. Tempdb is set to
> autogrow and it grow from 8MB to 655MB. I do not want to reboot the server
> now, but change the default value of tempdb(Whenever reboot happens it sho
uld
> change) .
> Can i change it from
> sql enterprise manager --> database-->properties-->datafiles-->space
> allocated (Change value here)
> --
>
> "Kalen Delaney" wrote:
>

changeing Dataflow tasks propeties by coding

Hi,
Is it possible to change the Dataflow tasks properties with VB coding? I've managed to change the properties of the control Flow tasks with VB code! as I wan to create a generic dataflow that will change everytime I run it.
CheersYes, you can. It is a bit more complicated, as many of the properties are contained in a CustomProperties collection on the data flow objects, so you need to find the names of the specific properties that you are interested in.|||

Kolf wrote:

Hi,
Is it possible to change the Dataflow tasks properties with VB coding? I've managed to change the properties of the control Flow tasks with VB code! as I wan to create a generic dataflow that will change everytime I run it.
Cheers

Kolf,

You know that you cannot change this stuff while the package is running right? You need to affect the change prior to the package running.

-Jamie

|||would you be able to give me on example so it will keep me going, yes and I am aware of the issue that I need to change the properties prior to running the package. therefore it dataflow should be in a sub-package.
Thanks|||

Kolf wrote:

would you be able to give me on example so it will keep me going, yes and I am aware of the issue that I need to change the properties prior to running the package. therefore it dataflow should be in a sub-package.
Thanks

This is quite a big area and I don't know of one example that covers everything. What in particular are you having trouble with? Navigating through the package to the property or knowing how to change it?

-Jamie

|||Thanks again Jamie, you've been very helpful

So there is no escape or work around this issue. I was hoping instead on using Transfer SQL Server object task (to copy the table to destination server, which dynamic tablelist feed – and using sub-package ), I could use dataflow tasks within one package (and avoid using sub-package and changing the property of the sub-package from parent package – as this is how it works now and it’s very slow) .

So I can use execute sql task to populate the table schema on the destination and then use a dataflowtask to push the data across , all in one package. And be able to put this in a loop to do for a list of tables.

I hope I’ve explained it clearly

|||

Kolf wrote:

would you be able to give me on example so it will keep me going, yes and I am aware of the issue that I need to change the properties prior to running the package. therefore it dataflow should be in a sub-package.
Thanks

Kolf,

Jessica Elise has posted some great code here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1404157&SiteID=1&mode=1 that may be of use.

-Jamie

changeing Dataflow tasks propeties by coding

Hi,
Is it possible to change the Dataflow tasks properties with VB coding? I've managed to change the properties of the control Flow tasks with VB code! as I wan to create a generic dataflow that will change everytime I run it.
Cheers

Yes, you can. It is a bit more complicated, as many of the properties are contained in a CustomProperties collection on the data flow objects, so you need to find the names of the specific properties that you are interested in.|||

Kolf wrote:

Hi,
Is it possible to change the Dataflow tasks properties with VB coding? I've managed to change the properties of the control Flow tasks with VB code! as I wan to create a generic dataflow that will change everytime I run it.
Cheers

Kolf,

You know that you cannot change this stuff while the package is running right? You need to affect the change prior to the package running.

-Jamie

|||would you be able to give me on example so it will keep me going, yes and I am aware of the issue that I need to change the properties prior to running the package. therefore it dataflow should be in a sub-package.
Thanks
|||

Kolf wrote:

would you be able to give me on example so it will keep me going, yes and I am aware of the issue that I need to change the properties prior to running the package. therefore it dataflow should be in a sub-package.
Thanks

This is quite a big area and I don't know of one example that covers everything. What in particular are you having trouble with? Navigating through the package to the property or knowing how to change it?

-Jamie

|||Thanks again Jamie, you've been very helpful

So there is no escape or work around this issue. I was hoping instead on using Transfer SQL Server object task (to copy the table to destination server, which dynamic tablelist feed – and using sub-package ), I could use dataflow tasks within one package (and avoid using sub-package and changing the property of the sub-package from parent package – as this is how it works now and it’s very slow) .

So I can use execute sql task to populate the table schema on the destination and then use a dataflowtask to push the data across , all in one package. And be able to put this in a loop to do for a list of tables.

I hope I’ve explained it clearly

|||

Kolf wrote:

would you be able to give me on example so it will keep me going, yes and I am aware of the issue that I need to change the properties prior to running the package. therefore it dataflow should be in a sub-package.
Thanks

Kolf,

Jessica Elise has posted some great code here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1404157&SiteID=1&mode=1 that may be of use.

-Jamie