We currently possess over 300 servers, most of which have at least 10 databases and most of those databases contain at least 100 stored procedures. We know that we only use a small fraction of these procedures and for our cleaning effort (or, in some case
We haven't committed to using source control and we have SQL Server objects in production that reference objects that have changed and are therefore no longer valid. With hundreds of servers, and hundreds of objects per server, is there a way to minimize
SQL Server DBAs and Developers often get flat files that they need to import into SQL Server for queries and data manipulation. In this video tip, learn how you can use PowerShell to dynamically read and import flat files to SQL Server.
A task that often needs to be performed by SQL Server DBAs and Developers is the need to move and rename files that are sitting on the file system. In this video tip Tim Smith shows how this can be done using PowerShell. He will also show how you can cr
ETL and SQL developers often import files with invalid data in those files. This has limited challenges with small file sizes, but as files grow to gigabytes worth of data, this task can be tedious. One of these forms of invalid data are lines with extra
We have various data sets and we'd like to construct an automated process that builds additional data sets from these original sets by removing outlier data. Check out this tip to see how this can be done.
A few colleagues have asked me if PowerShell provides an easy way to export Excel as a CSV. Whether we have multiple Excel files, or just multiple worksheets in Excel, PowerShell simplifies the process. In addition to that, once the format is in CSV, we h
We recently faced an issue with an internal data provider where we imported a flat file at 1AM, but in the past few months, the data provider began providing an incomplete or inaccurate file because it lacked the proper length (or didn't exceed a certain
We're looking to minimize ETL costs by importing as much data as possible using a automated system. A data provider sends us flat file data and we extract, analyze and report on these data. In this tip we look at how this can be automated using PowerShell
We import a file once a day and after importing the file, we need it moved to an archive folder with a date stamp appended to the file name. We have had trouble in the past with this process, so we'd like this to run as its own step to help troubleshoot
Several executives tell us that they will be collecting data from thousands CSV or text files and we should expect to see at least ten new files a day. Instead of trying to import each file one by one, how can we create an SSIS package that pulls the data