sql-server-data-tools

问题 We have many SSIS imports in our environment all created with SQL / Visual Studio 2008 version. We run a lot of imports from SharePoint and for that we have been using SharePoint List Adapters that we got from CodePlex long time ago. It works great in SSIS 2008. However we are trying to upgrade all of our jobs to run with newer version and using SQL Server Data Tools 2015. I installed SQL Server Data Tools 2015 on the same machine as SQL Server 2008 Developer Tools. I am still able to use the

问题 We have many SSIS imports in our environment all created with SQL / Visual Studio 2008 version. We run a lot of imports from SharePoint and for that we have been using SharePoint List Adapters that we got from CodePlex long time ago. It works great in SSIS 2008. However we are trying to upgrade all of our jobs to run with newer version and using SQL Server Data Tools 2015. I installed SQL Server Data Tools 2015 on the same machine as SQL Server 2008 Developer Tools. I am still able to use the

问题 I want to read an Excel file which is 250 Mb large and has more than 300 000 rows. So when I try to process it in Excel source in SSIS it takes too much time and at last fails to process. Can anyone tell me how to split the big file into small ones or any other method that can help? 回答1: Best way is to read data by chunks, i have done this to read huge tables from SQL databases. But to read big excel files, i implemented this in a C# application not in SSIS since it is more complicated. I

问题 I am using SSIS to create some packages. I have gotten confused around the Data Conversion Transformation component and changing columns data types from Advanced editor If I can go into the advanced editor and change the data type of my output, why would I need to input the Data Conversion Transformation? Is this just down to preference or is there a difference between using both approaches? 回答1: Before showing the difference between both approaches, i will try to give an overview of the data

问题 I am testing SSIS package that I upgraded from VS2005 project to VS2013 (package deployment model) project. This is very simple package which just processes files one by one from specific location and updates database based on those files and once done it moves file to archive or non-parsing directory based on outcome. And I am getting odd error and I cant find solution for that. Issue is my package runs fine and it does exactly what it suppose to do (extracting data from file and inserting

问题 Related to a question I've asked earlier regarding SSRS, could anyone please tell me - Is it possible to reuse an existing dataset in SSRS? I know we can have shared datasets and we can convert a dataset to a shared one too. Currently we are using Crystal Reports. We are trying to migrate to SSRS. So we were trying to reuse the existing dataset which we've used to create Crystal Reports. There is no option I could see to convert this dataset to a shared dataset so that I can reuse it. I could

问题 Related to a question I've asked earlier regarding SSRS, could anyone please tell me - Is it possible to reuse an existing dataset in SSRS? I know we can have shared datasets and we can convert a dataset to a shared one too. Currently we are using Crystal Reports. We are trying to migrate to SSRS. So we were trying to reuse the existing dataset which we've used to create Crystal Reports. There is no option I could see to convert this dataset to a shared dataset so that I can reuse it. I could

问题 I'm having a seemingly identical problem to what is described here: SSDT Refactor Rename is ignored by the Schema Comparison script generation. Essentially, the refactor component of SQL Server Data Tools is not working on schema comparison/update. Instead of renaming a table, for instance, the table with the old name is dropped and the table with the new name is created. Unfortunately, I do not see an accepted answer to that question. I found a similar question, which seems to be have been

问题 Is there a way to ignore some SQL files in the build of a SQL Server Database Project but include them on the schema compare? I mean, we have some SQL files that cause failures in the build (they point to a linked server which we have no access). What we want is to exclude it from the build (so the build passes) but include it on schema comparisons (so we can see if it was modified). Any suggestions? 回答1: When you deploy use a deployment filter to stop the object being deployed, either write

问题 Is there a way to ignore some SQL files in the build of a SQL Server Database Project but include them on the schema compare? I mean, we have some SQL files that cause failures in the build (they point to a linked server which we have no access). What we want is to exclude it from the build (so the build passes) but include it on schema comparisons (so we can see if it was modified). Any suggestions? 回答1: When you deploy use a deployment filter to stop the object being deployed, either write