Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I want to start with SQL Server SSIS. Kindly guide how to start with it and what are the areas that need to be looked in first.
Before diving in and getting your hands dirty start with the basic theory first. You want to be able to provide an answer to the questions "What is SSIS and what is it used for?"
My advice, start at the beginning, read the Microsoft supporting documentation for SQL Server Integration Services and develop an overall understanding of the technology and its features.
Another good place to start would be the Getting Started (Integration Services)
Then why not have a go at some of the Tutorials that Microsoft make available.
Suggest you type 'SQL Server SSIS Tutorial' into google, or follow this link
http://www.google.co.uk/search?hl=en&q=sql+server+ssis+tutorial&aq=f&aqi=g10&aql=&oq=&gs_rfai=
Top result is http://www.accelebrate.com/sql_training/ssis_tutorial.htm
Alernatively, document exactly what it is you want to do, and then see if you can find something to help you.
I assunme you have SQL Server installed.
At the very start, click Start Menu -> Programs -> Microsoft SQL Server 2005 -> SQL Server Business Intelligence Development Studio.
From in Business Intelligence Development Studio (BIDS) you will be able to create a new SSIS project.
Searching Google (or Bing) for "SSIS tutorial" would yield lots of results.....
E.g.
SSIS Tutorial: SQL Server 2005 Integration Services Tutorial
SQL Server Integration Services (SSIS) (Introduction)
SSIS Tutorials - Introduction to SSIS Tasks
and many, many more...
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I'm working in a project related to databases and I'm using a server with SQL server 2008 installed, but I'm working remotely from the office where I'm developing the software that will work with the database in VS 2015, which has built-in SQL tools to create databases, queries and so on, I have seen some tutorials where people have both VS and SSMS installed to work.
My questions are simple: is it really needed? whats the difference in creating the DB in VStudio vs SSMS?
You sure can. See the following tutorial.
https://www.c-sharpcorner.com/UploadFile/raj1979/how-to-create-database-project-in-visual-studio-2015/
To my knowledge there is no difference between using VS and SSMS, it is probably personal preference. For example, application developers who need to create a database probably prefer the familiarity of VS as well as keeping the DB file within their solution for code checking and what not. DB developers probably prefer SSMS because it is more intuitive and the UI is built around creating and managing databases.
I recommend using SSMS for creating databases.
Update: If you want to load data into SQL Server using Visual Studio, then you accomplish this with SQL Server Integration Services (SSIS). This is a big subject and I am not aware of how well versed you are in it, but to summarize, you will need the following:
1.) Install SQL Server Data Tools, which contains the Visual Studio templates for creating the following three project types: SSIS, SSRS, SSAS,
Where: I = Integration; R = Reporting; and A = Analysis
You can download SSDT for free at: https://learn.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt
2.) Create an SSIS solution that loads your files. There are many steps to accomplish this, but a cursory check for SSIS file loaders online yielded the following:
https://www.red-gate.com/simple-talk/sql/ssis/moving-data-from-excel-to-sql-server-10-steps-to-follow/
One thing to note that is not contained in the above tutorial is that the versioning requirements of SSDT, VS, and SQL Server are nothing short of maddening. However, Microsoft seems to have tried to address this with VS2015 and up by allowing for SQL Server package targeting (I do not have VS2015 to confirm, I am using VS2017 and confirm that version). Once you create a solution, do the following:
1.) Right click on the project
2.) Click on Configuration Properties
3.) Set the TargetServerVersion to the version of SQL Server that you are running.
4.) Note: the components that are available in the toolbox will change - this is normal.
See the following SO post for this (read billinkc's answer): VS2013 not picking up SQL2012 SSIS Custom Components
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
I am new to SQL Server Management Studio. In my company it is used just to sink data from source table to convert into predefined format, for that I use few queries in query table.
Please guide what else SQL Server Management Studio can help me?
SQL Server Management Studio includes the following general features:
Supports most administrative tasks for SQL Server.
A single, integrated environment for SQL Server Database Engine management and authoring.
Dialogs for managing objects in the SQL Server Database Engine, Analysis Services, and Reporting Services, that allows you to execute your actions immediately, send them to a Code Editor, or script them for later execution.
A common scheduling dialog that allows you to perform action of the management dialogs at a later time.
Exporting and importing SQL Server Management Studio server registration from one Management Studio environment to another.
Save or print XML Showplan or Deadlock files generated by SQL Server Profiler, review them later, or send them to administrators for analysis.
A new error and informational message box that presents much more information, allows you to send Microsoft a comment about the messages, allows you to copy messages to the clipboard, and allows you to easily e-mail the messages to your support team.
An integrated Web browser for quick browsing of MSDN or online help.
Integration of Help from online communities.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I am a relative beginner and will be doing database development against SQL Azure. I am confused by what seems to be a dizzying array of choices for development workflow. What I want to accomplish, in a very general sense is:
Do development and debugging against localdb
Deploy the changes from localdb to Azure whenever
Repeat
With respect to making DDL and data operations it seems like I can:
Use SQL Server Management Studio to connect directly to Azure and make changes
Use SQL Server Object Explorer within Visual Studio to do the same
Use a Visual Studio Database Project to make schema and other changes
Use Azure's web interface
Probably more
What do you recommend?
Personally, I use Code First Entity Framework with a datacontext that points to my local db. When I am ready to deploy my code to SQL Azure, I simply change the connection string on my datacontext and use the Update-Database command on package manager to apply all recent changes to sql azure. You could of course just simply have two instances of Sql Azure, a development instance and a production instance. But the drawback of this, is that it means you will always need an internet connection when working against your development Sql Azure instance.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I need to move a lot of data from an OLD DB2 server to SQL Server. I'd like to create a linked server using the OLE DB Provider for DB2 on my SQL Server. What I don't know is what is required on the DB2 side. The DB2 server belongs to another organization and most of the people that worked with it have retired. The version is "DB2 for VSE 6.1". Can I connect to that from SQL Server by default? If not, is there optional software that can be installed that will provide connectivity? I believe I need DRDA application server support, but that is all I have been able to find so far. Because of the volume of data, I would prefer not to use intermediate text files if possible. Are there other options that will work with V6.1?
If you can use SSIS, which can be available or not, depending on your SQL Server Edition, I recommend you to use this tool for moving the data. It help you handle of the complexities of data type changes, conversions, validations...
As far as what you need to connect to DB2, have a look at this. It not only explains how to use SSIS to connect to DB2, but also explain where you can download a DB2 driver.
I can't assure this driver will work with you particular version of DB2.
Look also here.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I heard about SSIS, a new replacement of the old DTS. I believe it has the same functionality which I used to perform. Now, like any other product from Microsoft, you have to mess with 10 different choices for a single package.
I would like to get your opinion of which edition of SQL Server 2005 I should buy to ensure that I can replicate data between my host server and the local data store just the way DTS worked?
Sorry dude, but SSIS is not as easy and solid as DTS... if possible I would stay with a copy of SQL 2000 to use DTS
You can install the backward compatibility components for SQL Server 2005 which allows you to run your old DTS packages in SQL Server 2005 (and 2008). Here's the link :
http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en
You can use DTS in SQL Server 2005. My departmental server was upgraded to SQL Server 2005 from SQL Server 2000. My DTS packages were moved as well. You will need the Microsoft SQL Server 2000 DTS Designer Components in order to edit them.
http://msdn.microsoft.com/en-us/sqlserver/aa336314.aspx
The drawback to this is that it will be very hard to create new packages. You can do it, but you'll need to first export an existing package, change it, then import it with a new name.
SSIS has a pretty high learning curve. I've been using it for a couple years now, and it is a step forward in some things, but backwards in others.
You'll want to keep this in mind after you've upgraded, if you're doing web development:
One difference between DTS and SSIS packages is, if you want to execute them through code, although you have more control over the package with SSIS, the machine the code is executing from is required to have SQL server installed on it. Which means if you're writing this as an ASP.Net application, for example, whatever machine(s) it ends up running on will also need to have sql server installed on them (which is unlikely in most environments)
I believe you probably want SQL Server 2005 - Workgroup edition.
The SSIS is not available in the Express version, and as long as you are not wanting to replicate the data out to various subscribers then Workgroup is probably all you need. Here is a chart comparing the various features of 2005.
Before you decide to purchase a version, I would download the trial of the particular version you are interested in and verify it gives you the functionality needed.