[HU]/[EN] Reminiscence Boulevard: Lengyel, magyar – két jó barát

Lengyel-magyar két jó barát
Együtt harcol s issza borát
Vitéz s bátor mindkettője
Áldás szálljon mindkettőre

This short and old story is about friendship between peoples from Poland and Hungary. Few months ago I meet in Budapest two new hungarian friends: Zoltán Horváth {TWITTER} and Janos Berke {TWITTER}. We talked about community, knowledge, experience, user groups… and I have been invited for Hungarian User Group for Microsoft SQL Server Meetup. In November I had chance for organizing my trips together and found the solution. In fact I should say: I maintained MeetUp Speech.

November végén két SQL Server MVP-től lesz
meghallgatható egy-egy előadás.
A magyar SQL Server MVP-k korlátozott száma
okán ennek a felét importból oldjuk meg

LOGO__HUH-MSSQLOn Wednesday 27th in LogMeIn HQ over forty Hungarian SQL Folks came for listening two sessions at MeetUp. Location is amazing, especially 5th floor, with big kitchen, open space with pool table, flippers, kinnect and beautiful terrace. Pleace where You want to work. Zoltán opening speech was in Hungarian, and I don’t understand anything except SQL Saturday. They have a plan (and formally started to executing this plan) for SQL Saturday in Budapest – this event will be held at 1st March 2014. Next I had a great honour to presenting session about Ad-Hoc Maintenance Plans for Beginners. Session based on Brad McGehee book (link for free ebook here) Brad’ Sure Guide to SQL Server Maintenance Plans published by RedGate. In one moment I recognized that something is wrong with me or audience. Asked and got answer: for forty attendees just obly TWO have been DBA! All athers (almost)… DEV. Yeah. Simple. But I tried to talk with them, and discovered that they are interesting in this subject, and having partial knowledge about administration od SQL Server databases. And they started to be more active (mayby by the swags from RedGate…).

All break we spend on discussions, some peoples were very focused for maintaining, especially for SHRINK (!sic) data and files. The conclusion is simple: bad architecture of environment, default installation and very, very limited space. Bad, bad patterns.

After break I take a part with second session provided by only one SQL Server MVP form Hungary Kővári Attila {TWITTER}. He presenting BI stack: Excel, PowerView, PowerMap and few other features. All in Hungarian: sessions, questions, answers, office, windows, maps, views. Interesting experiment for me. But I saw that audience like it. They have many questions, they were very active.  And Kővári is really good speaker. Wishing to know Hungarian in “understandable mode” for his next session.

At the end I want to say Köszönöm for organizers: Zoltán & Janos & magic girl from LogMeIn HQ, and for all attendees. Hope the new comers (about five peoples) will back in futures meetups. On my Facebook page You can see some Pictures at an Exhibiton and on my SlideShare profile You can download my slidedeck.

 

PS: See You in March in Budapest! HERE

[EN] How to DO IT? My Maintenance SUB-Plans doesn’t work.

Last night I discovered on one of my customers systems, that Maintenance Plan doesn’t work. After few hours I received request form customer with printscreen:

image

Pict. 01 | Error with execution of Maintenance Plans.

When we look into message error we get more details:

image

Pict. 02 | Weekly Batch contains multiple plans…

But what is wrong with that? Customer’s idea was: to executing one batch (in this case weekly) with four subplans such: DBCC CHECKDB, REORGANIZE INDEXES, UPDATE STATISTICS and BACKUP (type FULL) for All Systems Databases. All together looks like this:

Captura_MaintenancePlans2005_08

Pict. 03 | One batch, four subplans and errors

The administrator creates exactly the same weekly batch for Users Databases, but it’s one small and important difference:

Captura_MaintenancePlans2005_09

Pict. 04 | Executing “exactly” the same batch for All User Databases.

 

The difference is very clear: they are four plans in first example and one in second. Let’s comparing differences:

image

Pict. 05 | I’ve got You! Right side: System Databases and Leftt side: User Databases.

As we see our maintenance plans are different, and they cannot work the same. Now we have two options: we can change first batch in SSIS or creat the new one (simple and fast option). But be sure that we will not repeat the design error:

image

Pict. 06 | We must remember about second option: Single schedule for ENTIRE PLAN or no schedule

At the end we have two Maintenance Plans, designed and scheduler very similar (only schedule od execution and types od databases are different):

image

Pict. 07 | Comparing the batches.

Think twice (what you need), design (how it shoud work), think one more (how it looks) time and execute (to check).