15,886,026 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View Python questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by AFell2 (Top 2 by date)
AFell2
26-Dec-19 12:02pm
View
I need to reinforce Richard's good advice. Your best plan of attack is to design the system without writing any code FIRST. You should document which tools/frameworks your would like to use, but describing the ecosystem before you build anything will let you see the missing pieces and save you tons of time reconfiguring down the road. Once you have your design documented, you an then start breaking up the work so you can tackle the key infrastructure pieces first before you get bogged down in the detail pieces.
AFell2
18-Dec-19 17:27pm
View
Is that 390 files all with distinct column mappings? That would mean you would either have to create 390 SSIS packages, or 1 SSIS package with 390 configurations. I would lean towards the latter, as you can always containerize the configurations to a JSON or xml file and pull them in at processing time to handle the column configuration.