Featured Article(s)
Business Process Management, Workflow and Business Process Rules – a close look [Part II]
As we already know, Business Process Management is a revolution in the industry today. It promotes improved efficiency, increased flexibility and adaptability to future changes. BPM integrates business and IT into a unified whole – a paradigm shift from the way the traditional applications are designed and maintained. Enterprises the world over are now switching over to BPMS (Business Process Management Systems) so as to increase the operational agility and increase in ROI and the overall productivity of the organization as a whole. This article is the concluding part of this series of articles on Business processes, Business Process Management, Workflow and Business Process Rules. In this part we will take a look at Business Process Rules, Business Process Rules Engines and the advantages, the benefits of integrating Business Process Rules Engine into the Business Process Management Systems.
Password problems? Imagine forgetting all your passwords… Now you can. Manage and share your organization’s critical passwords with Secret Server, a highly secure web-based password management system With our Active Directory integration system, all you need remember is one password to access all of your secrets. Free 30-day trial so you can work with it and see exactly how it works.
Video Programs/Shows available:
[Watch] SelectViews – Accidental DBA Tips II, Security, Data Masking and more
[Watch] Disaster Recovery and Response Planning
[Watch] SelectViews – the Accidental DBA – tips, tricks and thoughts
Different Titles Mean More Hires???
Dan writes: "Now I need to hire two people with the same acronym title with different jobs. Sell that too management. Hire one person who knows the business and he will be able to architect and administer the database. Get on the right platform, and administration is a breeze.
The more I read these emails and all the philosophizing on roles and responsibilities, the more I realize that we’ve made the world way to complicated. All these niche jobs are killing the efficiency of databases and applications. Let me make one thing clear:
It’s the PROCESS that drives the database and the code. The PROCESS is what makes business better and faster.
The reason most poorly architected databases exist is because business changes, not because the original creator was a moron. Years go by, and processes must change. That means code must change and the database must change. Anticipation can only get you so far. In this day and age of integrating with customer, the amount of insane requirements is endless."
This is a very important point – and I wonder how everyone is addressing it. SQL Server has certainly been around long enough now that applications are facing some of the same challenges Microsoft is in terms of legacy code. Things get better, things get more efficient, things are updated. How do you handle this in a SQL Server-based application where your team is the architect? I’ve hit this wall many times – with applications we’ve built, then SQL Server and other technologies evolve… and we need to update the application, the architecture, the approach taken ‘the first time around" to take advantage of new lessons learned, new technologies and the like. BUT, to the customer, it works just fine right now.
This is a slightly different point from Dan’s – but it does talk to the business changes, code changes, technology changes that we must face and address. For some, this is why they’re on V6x of SQL Server to this day. "If it ain’t broke, don’t fix it."
I’m digressing a bit from the topic at hand. That of creating new positions with new titles to address what I’d call technology trends. I’d rather see traditional architect/engineer/admin roles simply evolve and be included in these new approaches, and then we can learn to bring applications forward to new versions and so-on. (See, I can tie it all together, sort of).
Featured White Paper(s)
The Keys to Recoverability, from ESG
ESG Analyst, Lauren Whitehouse, discusses Double-Take Software’s concept of “recoverability” – which involves layers of prote… (read more)
Enterprise IT Migration for the Software AG Environment
Migrating away from ADABAS and Natural is not a simple task. Organizations have typically used these products to write missio… (read more)