New answers tagged

0

This simple query on MSDB should get you started: SELECT s2.subsystem AS [TypeOfJobStep]-- when subsystem = 'SSIS' then 'SSIS job step' , s2.command AS [JobStepCommand] , s.name AS [JobName] FROM dbo.sysjobs AS s JOIN dbo.sysjobsteps AS s2 ON s2.job_id = s.job_id You can identify SSRS subscriptions because their name will be alternating ...


0

One of the easiest ways to create an XSD is open the XML (not XSD) file in Visual Studio or SQL Server Management Studio (SSMS) and click the 'XML' menu then 'Create Schema ...': I think this will be easier for you than using SSIS. Create some XML which looks how you want, and create the XSD from that. Make sense?


5

The OLE DB Destination Component's Data Access Modes comes in two flavors - fast and non-fast. Fast, either "table or view - fast load" or "table or view name variable - fast load" means that data will be loaded in a set-based fashion. Slow - either the "table or view" or "table or view name variable" will result in SSIS issuing singleton insert ...


5

Fast Load is well documented under FAST LOAD options Keep identity values from the imported data file or use unique values assigned by SQL Server. Retain a null value during the bulk load operation. Check constraints on the target table or view during the bulk import operation. Acquire a table-level lock for the duration of the bulk load ...


0

If you can manually change the encoding (to one that includes the Byte Order Mark) and have it work such that no characters are lost, then the file itself is fine. It seems that the tablediff utility does not allow for specifying the encoding type of the output file, so you are left with two options: Configure SSIS to specify that script as being UTF-8 ...


2

Yesterday when I was working with the file I went to the preview tab and I set the Data rows to skip to around 45k so I could preview what some of those rows were looking like. I was under the impression that the Data rows to skip value would only affect the preview and not actually be used at run time. Setting the Data rows to skip back to 0 made it so ...


4

I suspect the issue appears because you are referencing the view twice in the UPDATE statement, once in UPDATE [dbo].[vwMP_VOL] clause and then in FROM clause and the second time you are giving it an alias. But you are not using the alias in the SET clause, only the first reference. The result is that the the two references are unrelated and the rows are ...


1

Change your update to UPDATE [dbo].[vwMP_VOL] SET [vwMP_VOL].[id_batch] = inserted.id_batch ,[vwMP_VOL].[id_invoice] = inserted.id_invoice ,[vwMP_VOL].[text_vchr] = inserted.text_vchr ,[vwMP_VOL].[amt_frt_tcur] = inserted.amt_frt_tcur ,[vwMP_VOL].[amt_line_hcur] = inserted.amt_line_hcur ,[vwMP_VOL].[line_total_hcur] = ...


2

If you trace the query the report is generating you'll see that the executions are stored in the [catalog].[executions] of the database behind the Integration Services Catalog. You can just modify your [end_time] there and you should be able to 'fix' the report. I haven't managed to reproduce your exact scenario (i.e. hard resetting a VM to get a package ...



Top 50 recent answers are included