Home Forums Reporting Services Reporting Services Check the configuration and deployment settings for SSIS, SSRS and SSAS RE: Check the configuration and deployment settings for SSIS, SSRS and SSAS

  • Benki Chendu - Thursday, March 8, 2018 12:09 PM

    Sue_H - Thursday, March 8, 2018 11:56 AM

    Benki Chendu - Thursday, March 8, 2018 8:28 AM

    It all sounds a bit odd but maybe I'm missing something.
    How are you going to run scripts if you don't have access to any of the systems?
    Is someone going to run them for you and if so, do you know what information you need?  - This is correct. Someone is going to run it.
    Are you the one who will be moving all of these or are you expected to come up with a plan to move them and deliver it to someone else? I feel bad for you already... - Yes at a later point of time

    As for how everything runs today, you would need identify what information you need that would impact migrating. It's just seems too broad at this point - unknown versions, package storage and usage, how you plan to upgrade reports, hardware/OS changes, etc.
    In terms of deployment settings, that seems like something you need to figure out based upon what and how you deploy based on business needs, versions. There are hundreds of questions you need to ask the business. Maybe sit down and come up with all the questions to ask the business and come up with a list of things you need to know about each component and work on your scripts from there. 

    Sue

    Thanks Sue. Is there one such checklist/List of questions?
    I have tried to ask how much I could.but certainly need some help  more

    There are some checklists out there on blogs and such but there is no one size fits all. Every environment is different. I've had different upgrade processes when working at the same company. You need to ask for specifics on how and what different pieces are used such as asking what the different packages do. Those are more complex due to some of the dependencies. Where to get information on the packages depend on how they use SSIS in terms of storage - on disk, in msdb, ssisdb, etc. If they have any developers or source control, you can probably access rdl and dtsx files as well as various SSAS files (database, cube, ds). Those will give you some information in XML.
    But you will be the one coming up with questions to ask - do you know how they store or execute packages now? What do they do with maintenance? How do they manage access control? Some ideas around checklists and links to those:
    The Migration Checklist
    SQL Server Migration Plan
    SQL Server Database Migration Checklist

    There are quite a few like that if you search on SQL Server migration checklist.
    Any action item is something you need to know about so just start asking them questions related to that. For example, all the checklists will mention backups so you would want to know how they do those for all of those components - do they schedule them, do they use SQL jobs, do they use third party products, where are things backed up to, etc. So the migration checklists would drive the questions you ask them.

    Sue