March 4, 2017 at 12:00 pm
Comments posted to this topic are about the item Containing the Work
March 6, 2017 at 3:35 am
OMG wouldn't that contained jobs thing be saving me like days of work right now, especially if it contained the SSIS packages too!
March 6, 2017 at 7:35 am
Just considering the backup piece, I feel like this could lead to problems. Right now we use instance level backup jobs which loop through all the databases sequentially and back them up one at a time. What happens if each database contains its own backup job and they are all scheduled to start at exactly the same time? That could really put a strain on both the disks that hold the mdf files and the location where the backup is being written. I also feel like that would be complicating one of the parts of our jobs that are rather simple now. DBAs know which databases in an instance need which kinds of backups, and can manage them together. If the backups were managed at the database level, we suddenly have 10s, 100s, or even 1000s of individual backup jobs and schedules to maintain.
March 6, 2017 at 7:48 am
Once SQL Agent and SSIS are ported to Azure, I expect they will be contained at the database level, functionality which would probably trickle down to the on-prem version of SQL Server as well.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
March 6, 2017 at 7:56 am
david.gugg - Monday, March 6, 2017 7:35 AMJust considering the backup piece, I feel like this could lead to problems. Right now we use instance level backup jobs which loop through all the databases sequentially and back them up one at a time. What happens if each database contains its own backup job and they are all scheduled to start at exactly the same time? That could really put a strain on both the disks that hold the mdf files and the location where the backup is being written. I also feel like that would be complicating one of the parts of our jobs that are rather simple now. DBAs know which databases in an instance need which kinds of backups, and can manage them together. If the backups were managed at the database level, we suddenly have 10s, 100s, or even 1000s of individual backup jobs and schedules to maintain.
Easily. Microsoft could add logic that allows jobs with the same name to be scheduled sequentially.
Don't forget, this isn't something you manage and maintain constantly. How often do you revisit backup jobs and schedules? How often do you move databases? It's rare.
March 6, 2017 at 9:31 am
So would someone please be kind enough to give me a short synopsis as to what that link describes? I'd appreciate it.
Kindest Regards, Rod Connect with me on LinkedIn.
March 6, 2017 at 10:16 am
Actually both Chrome and Edge are complaining about the security certificate for the SimpleTalk site. Yikes!
March 6, 2017 at 11:22 am
Really it's an article that talks a bit about the history of containers and how they differ from VMs. Essentially a container reuses much of the host kernal and base system on Linux. On Windows, it uses most of the core Windows functionality, but provides some separation for applications. This is primarily to allow things like Java 8 and Java 9 to both exist in a single container, where they might not normally be allowed on the same OS host. Many types of applications struggle to have multiple versions of the app running at the same time. Containers allow separation.
March 6, 2017 at 11:23 am
j_e_o - Monday, March 6, 2017 10:16 AMActually both Chrome and Edge are complaining about the security certificate for the SimpleTalk site. Yikes!
Reported
March 15, 2017 at 6:53 am
Steve Jones - SSC Editor - Monday, March 6, 2017 7:56 AMdavid.gugg - Monday, March 6, 2017 7:35 AMJust considering the backup piece, I feel like this could lead to problems. Right now we use instance level backup jobs which loop through all the databases sequentially and back them up one at a time. What happens if each database contains its own backup job and they are all scheduled to start at exactly the same time? That could really put a strain on both the disks that hold the mdf files and the location where the backup is being written. I also feel like that would be complicating one of the parts of our jobs that are rather simple now. DBAs know which databases in an instance need which kinds of backups, and can manage them together. If the backups were managed at the database level, we suddenly have 10s, 100s, or even 1000s of individual backup jobs and schedules to maintain.Easily. Microsoft could add logic that allows jobs with the same name to be scheduled sequentially.
Don't forget, this isn't something you manage and maintain constantly. How often do you revisit backup jobs and schedules? How often do you move databases? It's rare.
I can imagine quite a flexible constraint system based on time, whether the database has (non-system) peers on the instance, signals/events, specifying whether parallelism is allowed or not, etc. These rules should be specified within the contain with values, events and signals passed in to each container to evaluate.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
October 6, 2017 at 10:41 am
I hope they add linked servers but for each database.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply