May 31, 2012 at 12:41 pm
All,
I would really appreciate your help in providing any advice for learing vb.net scripting for the SSIS script components. I dont know where to begin learning. I wrote a sample script with lot of difficulty a few months ago, but now I am going to use this a whole lot in my current project. Any advice/help will be appreciated. Any book names, online tutorials etc will be great!.
May 31, 2012 at 12:54 pm
I just googled "ssis vb.net tutorial" and get over 200,000 hits. The first page all look good sources of information. One of which is a link from this very site to an article that looks to be a great starting point.
http://www.sqlservercentral.com/articles/Integration+Services+%28SSIS%29/76438/[/url]
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
May 31, 2012 at 1:58 pm
Thank you Sean! This is indeed a good starting point for a novice like me. 🙂
May 31, 2012 at 3:47 pm
Pick a few problems to solve. For example, read the SSIS forums, find a question on scripting and try to solve it. Or re-implement it on your system, using someone else's solution. Using it will help the most.
June 1, 2012 at 3:13 pm
Nothing against VB.net (I used to develop lots of VB6 and learned VB.net before I learned C#) but C# has earned a dominant position in terms of the amount of adoption in the coder community a few years ago and has never looked back. SSIS in SQL Server 2005 only supported VB.net Script. C# Script support was added to SSIS in SQL Server 2008. I would recommend learning C# if starting from scratch on SQL Server 2008.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
June 1, 2012 at 3:19 pm
opc.three (6/1/2012)
Nothing against VB.net (I used to develop lots of VB6 and learned VB.net before I learned C#) but C# has earned a dominant position in terms of the amount of adoption in the coder community a few years ago and has never looked back. SSIS in SQL Server 2005 only supported VB.net Script. C# Script support was added to SSIS in SQL Server 2008. I would recommend learning C# if starting from scratch on SQL Server 2008.
It really depends on the environment you are working in which you should learn. VB.NET may be easier to pick up initially than C#. I would suggest working with both. As you work through problems, do them in both languages.
June 1, 2012 at 3:33 pm
Lynn Pettis (6/1/2012)
opc.three (6/1/2012)
Nothing against VB.net (I used to develop lots of VB6 and learned VB.net before I learned C#) but C# has earned a dominant position in terms of the amount of adoption in the coder community a few years ago and has never looked back. SSIS in SQL Server 2005 only supported VB.net Script. C# Script support was added to SSIS in SQL Server 2008. I would recommend learning C# if starting from scratch on SQL Server 2008.It really depends on the environment you are working in which you should learn. VB.NET may be easier to pick up initially than C#. I would suggest working with both. As you work through problems, do them in both languages.
If you have the time that would be a great approach. There are some subtle differences in how you will accomplish common tasks across the two languages. It can be an invaluable skill to be able to crossover from one to the other, especially if you work in shops where both languages exist and you have to troubleshoot or enhance people's code as part of your primary job function.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
June 1, 2012 at 3:46 pm
opc.three (6/1/2012)
Lynn Pettis (6/1/2012)
opc.three (6/1/2012)
Nothing against VB.net (I used to develop lots of VB6 and learned VB.net before I learned C#) but C# has earned a dominant position in terms of the amount of adoption in the coder community a few years ago and has never looked back. SSIS in SQL Server 2005 only supported VB.net Script. C# Script support was added to SSIS in SQL Server 2008. I would recommend learning C# if starting from scratch on SQL Server 2008.It really depends on the environment you are working in which you should learn. VB.NET may be easier to pick up initially than C#. I would suggest working with both. As you work through problems, do them in both languages.
If you have the time that would be a great approach. There are some subtle differences in how you will accomplish common tasks across the two languages. It can be an invaluable skill to be able to crossover from one to the other, especially if you work in shops where both languages exist and you have to troubleshoot or enhance people's code as part of your primary job function.
Previous employer couple times removed, started relearning VB.NET because that is what they wanted future development in since that is what the only developer knew and they didn't want things done in both languages. Like I said, it depends on your environemnt. If you are working through books on your own time, you should take the time to learn both. You never know when knowledge of the other may be of benefit (such as when working with an application that was developed using both because multiple developers were involved). Of course, this doesn't mean I would suggest also learning COBOL.NET, and yes it exists but perhaps not with that exact name.
June 1, 2012 at 3:53 pm
Lynn Pettis (6/1/2012)
opc.three (6/1/2012)
Lynn Pettis (6/1/2012)
opc.three (6/1/2012)
Nothing against VB.net (I used to develop lots of VB6 and learned VB.net before I learned C#) but C# has earned a dominant position in terms of the amount of adoption in the coder community a few years ago and has never looked back. SSIS in SQL Server 2005 only supported VB.net Script. C# Script support was added to SSIS in SQL Server 2008. I would recommend learning C# if starting from scratch on SQL Server 2008.It really depends on the environment you are working in which you should learn. VB.NET may be easier to pick up initially than C#. I would suggest working with both. As you work through problems, do them in both languages.
If you have the time that would be a great approach. There are some subtle differences in how you will accomplish common tasks across the two languages. It can be an invaluable skill to be able to crossover from one to the other, especially if you work in shops where both languages exist and you have to troubleshoot or enhance people's code as part of your primary job function.
Previous employer couple times removed, started relearning VB.NET because that is what they wanted future development in since that is what the only developer knew and they didn't want things done in both languages. Like I said, it depends on your environemnt. If you are working through books on your own time, you should take the time to learn both. You never know when knowledge of the other may be of benefit (such as when working with an application that was developed using both because multiple developers were involved). Of course, this doesn't mean I would suggest also learning COBOL.NET, and yes it exists but perhaps not with that exact name.
C# adoption outpaces VB.net by a significant margin these days, and I suspect COBOL.net as well. That doesn't mean however that if I took a job where they required me as a COBOL.net resource I would still aim to learn C# first. I am only saying that if one were starting from scratch with no preconditions to which direction to go I would recommend going by the numbers and learning C#.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
June 1, 2012 at 3:56 pm
opc.three (6/1/2012)
Lynn Pettis (6/1/2012)
opc.three (6/1/2012)
Lynn Pettis (6/1/2012)
opc.three (6/1/2012)
Nothing against VB.net (I used to develop lots of VB6 and learned VB.net before I learned C#) but C# has earned a dominant position in terms of the amount of adoption in the coder community a few years ago and has never looked back. SSIS in SQL Server 2005 only supported VB.net Script. C# Script support was added to SSIS in SQL Server 2008. I would recommend learning C# if starting from scratch on SQL Server 2008.It really depends on the environment you are working in which you should learn. VB.NET may be easier to pick up initially than C#. I would suggest working with both. As you work through problems, do them in both languages.
If you have the time that would be a great approach. There are some subtle differences in how you will accomplish common tasks across the two languages. It can be an invaluable skill to be able to crossover from one to the other, especially if you work in shops where both languages exist and you have to troubleshoot or enhance people's code as part of your primary job function.
Previous employer couple times removed, started relearning VB.NET because that is what they wanted future development in since that is what the only developer knew and they didn't want things done in both languages. Like I said, it depends on your environemnt. If you are working through books on your own time, you should take the time to learn both. You never know when knowledge of the other may be of benefit (such as when working with an application that was developed using both because multiple developers were involved). Of course, this doesn't mean I would suggest also learning COBOL.NET, and yes it exists but perhaps not with that exact name.
C# adoption outpaces VB.net by a significant margin these days, and I suspect COBOL.net as well. That doesn't mean however that if I took a job where they required me as a COBOL.net resource I would still aim to learn C# first. I am only saying that if one were starting from scratch with no preconditions to which direction to go I would recommend going by the numbers and learning C#.
Okay, you're right and I am wrong.
June 1, 2012 at 4:04 pm
Lynn Pettis (6/1/2012)
opc.three (6/1/2012)
Lynn Pettis (6/1/2012)
opc.three (6/1/2012)
Lynn Pettis (6/1/2012)
opc.three (6/1/2012)
Nothing against VB.net (I used to develop lots of VB6 and learned VB.net before I learned C#) but C# has earned a dominant position in terms of the amount of adoption in the coder community a few years ago and has never looked back. SSIS in SQL Server 2005 only supported VB.net Script. C# Script support was added to SSIS in SQL Server 2008. I would recommend learning C# if starting from scratch on SQL Server 2008.It really depends on the environment you are working in which you should learn. VB.NET may be easier to pick up initially than C#. I would suggest working with both. As you work through problems, do them in both languages.
If you have the time that would be a great approach. There are some subtle differences in how you will accomplish common tasks across the two languages. It can be an invaluable skill to be able to crossover from one to the other, especially if you work in shops where both languages exist and you have to troubleshoot or enhance people's code as part of your primary job function.
Previous employer couple times removed, started relearning VB.NET because that is what they wanted future development in since that is what the only developer knew and they didn't want things done in both languages. Like I said, it depends on your environemnt. If you are working through books on your own time, you should take the time to learn both. You never know when knowledge of the other may be of benefit (such as when working with an application that was developed using both because multiple developers were involved). Of course, this doesn't mean I would suggest also learning COBOL.NET, and yes it exists but perhaps not with that exact name.
C# adoption outpaces VB.net by a significant margin these days, and I suspect COBOL.net as well. That doesn't mean however that if I took a job where they required me as a COBOL.net resource I would still aim to learn C# first. I am only saying that if one were starting from scratch with no preconditions to which direction to go I would recommend going by the numbers and learning C#.
Okay, you're right and I am wrong.
Wow, nothing to be right or wrong about. Sorry if my style grinds on you, Lynn. I do not mind which CLR Language anyone decides to or is compelled to pickup. I was just clarifying my opinion from a generalist point of view. Have a good afternoon.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
June 1, 2012 at 4:37 pm
opc.three (6/1/2012)
Lynn Pettis (6/1/2012)
opc.three (6/1/2012)
Lynn Pettis (6/1/2012)
opc.three (6/1/2012)
Lynn Pettis (6/1/2012)
opc.three (6/1/2012)
Nothing against VB.net (I used to develop lots of VB6 and learned VB.net before I learned C#) but C# has earned a dominant position in terms of the amount of adoption in the coder community a few years ago and has never looked back. SSIS in SQL Server 2005 only supported VB.net Script. C# Script support was added to SSIS in SQL Server 2008. I would recommend learning C# if starting from scratch on SQL Server 2008.It really depends on the environment you are working in which you should learn. VB.NET may be easier to pick up initially than C#. I would suggest working with both. As you work through problems, do them in both languages.
If you have the time that would be a great approach. There are some subtle differences in how you will accomplish common tasks across the two languages. It can be an invaluable skill to be able to crossover from one to the other, especially if you work in shops where both languages exist and you have to troubleshoot or enhance people's code as part of your primary job function.
Previous employer couple times removed, started relearning VB.NET because that is what they wanted future development in since that is what the only developer knew and they didn't want things done in both languages. Like I said, it depends on your environemnt. If you are working through books on your own time, you should take the time to learn both. You never know when knowledge of the other may be of benefit (such as when working with an application that was developed using both because multiple developers were involved). Of course, this doesn't mean I would suggest also learning COBOL.NET, and yes it exists but perhaps not with that exact name.
C# adoption outpaces VB.net by a significant margin these days, and I suspect COBOL.net as well. That doesn't mean however that if I took a job where they required me as a COBOL.net resource I would still aim to learn C# first. I am only saying that if one were starting from scratch with no preconditions to which direction to go I would recommend going by the numbers and learning C#.
Okay, you're right and I am wrong.
Wow, nothing to be right or wrong about. Sorry if my style grinds on you, Lynn. I do not mind which CLR Language anyone decides to or is compelled to pickup. I was just clarifying my opinion from a generalist point of view. Have a good afternoon.
So was I, but I was obviously wrong and I am willing to admit it. Nothing more need be said.
June 1, 2012 at 5:33 pm
Thank you all for your valuable suggestions. I think I will just try and learn new things as I encounter new problems. I will try to learn both the languages depending on the situation. If VB.NET is better at solving a given problem, I will use it; or otherwise I will use C# 🙂
June 1, 2012 at 5:38 pm
rajiv.varma (6/1/2012)
Thank you all for your valuable suggestions. I think I will just try and learn new things as I encounter new problems. I will try to learn both the languages depending on the situation. If VB.NET is better at solving a given problem, I will use it; or otherwise I will use C# 🙂
Awesome, couldn't agree more that the you should use the best tool for the job.
June 1, 2012 at 10:39 pm
I will add my two cents here, so rajiv.varma won't get confused 🙂
Which language to learn C# or Vb.Net depends on:
Both these languages share the same framework, they differ on the syntax to write their statements, their performance is exactly the same so there is not performance benefits by using one or the other.
Their syntax differs within their standard commands, no in the way you refer to framework objects, by example, a single if statement is written like
If Balance > 20 Then
' do whatever
Balance = Balance + 2.5
Else
Balance = Balance - 2.5
End If
The same condition is C# looks like:
if (Balance > 20)
{
// do whatever
Balance = Balance + 2.5;
}
else
{
Balance = Balance - 2.5;
}
There is a claim that Visual Basic syntax is more english like and easier to read, not so C#; C# is case sensitive, so the variable Balance is not the same as balance while for Vb.Net Balance and balance has the same meaning.
The demands for C# developers is bigger, you will find more examples written for C# than Vb.Net as well.
Hope this helps,
Rock from VbCity
Viewing 15 posts - 1 through 15 (of 32 total)
You must be logged in to reply to this topic. Login to reply