Category: Chicago

Splunk 2020 Predictions

Jan 7, 2020 by Sam Taylor

Around the turn of each new year, we start to see predictions issued from media experts, analysts and key players in various industries. I love this stuff, particularly predictions around technology, which is driving so much change in our work and personal lives. I know there’s sometimes a temptation to see these predictions as Christmas catalogs of the new toys that will be coming, but I think a better way to view them, especially as a leader in a tech company, is as guides for professional development. Not a catalog, but a curriculum.

We’re undergoing constant transformation — at Splunk, we’re generally tackling several transformations at a time — but too often, organizations view transformation as something external: upgrading infrastructure or shifting to the cloud, installing a new ERP or CRM tool. Sprinkling in some magic AI dust. Or, like a new set of clothes: We’re all dressed up, but still the same people underneath. 

I think that misses a key point of transformation; regardless of what tools or technology is involved, a “transformation” doesn’t just change your toolset. It changes the how, and sometimes the why, of your business. It transforms how you operate. It transforms you.

Splunk’s Look at the Year(s) Ahead

That’s what came to mind as I was reading Splunk’s new 2020 Predictions report. This year’s edition balances exciting opportunities with uncomfortable warnings, both of which are necessary for any look into the future.

Filed under “Can’t wait for that”: 

  • 5G is probably the most exciting change, and one that will affect many organizations soonest. As the 5G rollouts begin (expect it to be slow and patchy at first), we’ll start to see new devices, new efficiencies and entirely new business models emerge. 
  • Augmented and virtual reality have largely been the domain of the gaming world. However, meaningful and transformative business applications are beginning to take off in medical and industrial settings, as well as in retail. The possibilities for better, more accessible medical care, safer and more reliable industrial operations and currently unimagined retail experiences are spine-tingling. As exciting as the gaming implications are, I think that we’ll see much more impact from the use of AR/VR in business.
  • Natural language processing is making it easier to apply artificial intelligence to everything from financial risk to the talent recruitment process. As with most technologies, the trick here is in carefully considered application of these advances. 

On the “Must watch out for that” side:

  • Deepfakes are a disturbing development that threaten new levels of fake news, and also challenge CISOs in the fight against social engineering attacks. It’s one thing to be alert to suspicious emails. But when you’re confident that you recognize the voice on the phone or the image in a video, it adds a whole new layer of complexity and misdirection.
  • Infrastructure attacks: Coming into an election year, there’s an awareness of the dangers of hacking and manipulation, but the vulnerability of critical infrastructure is another issue, one that ransomware attacks only begin to illustrate.

Tools exist to mitigate these threats, from the data-driven technologies that spot digital manipulations or trace the bot armies behind coordinated disinformation attacks to threat intelligence tools like the MITRE ATT&CK framework, which is being adopted by SOCs and security vendors alike. It’s a great example of the power of data and sharing information to improve security for all.

Change With the Times

As a leader trying to drive Splunk forward, I have to look at what’s coming and think, “How will this transform my team? How will we have to change to be successful?” I encourage everyone to think about how the coming technologies will change our lives — and to optimize for likely futures. Business leaders will need greater data literacy and an ability to talk to, and lead, technical team members. IT leaders will continue to need business and communication skills as they procure and manage more technology than they build themselves. We need to learn to manage complex tech tools, rather than be mystified by them, because the human interface will remain crucial. 

There are still some leaders who prefer to “trust their gut” rather than be “data-driven.” I always think that this is a false dichotomy. To ignore the evidence of data is foolish, but data generally only informs decisions — it doesn’t usually make them. An algorithm can mine inhuman amounts of data and find patterns. Software can extract that insight and render an elegant, comprehensible visual. The ability to ask the right questions upfront, and decide how to act once the insights surface, will remain human talents. It’s the combination of instinct and data together that will continue to drive the best decisions.

This year’s Splunk Predictions offer several great ways to assess how the future is changing and to inspire thought on how we can change our organizations and ourselves to thrive.

Tips and Tricks with MS SQL (Part 8)

Dec 23, 2019 by Sam Taylor

Tame Your Log Files!

By default, the recovery model for database backups on Microsoft‘s SQL Server is set to “full”. This could cause issues for the uninitiated. If backups aren’t fully understood and managed correctly it could cause log files to bloat in size and get out of control. With the “full” recovery model, you get the advantage of flexibility in point-in-time restores and high-availability scenarios, but this also means having to run separate backups for log files in addition to the data files.


To keep things simple, we’ll look at the “simple” recovery model. When you run backups, you’re only dealing with data backups whether it’s a full or differential backup. The log file, which holds transactions between full backups, won’t be something you need to concern yourself with unless you’re doing advanced disaster recovery, like database mirroring, log shipping, or high-availability setups.


When dealing with a “full” recovery model, you’re not only in charge of backing up the data files, but the log files as well. In a healthy server configuration, log files are much smaller than data files. This means you can run log backups every 15 minutes or every hour without much IO activity as a full or differential backup. This is where you get the point-in-time flexibility. This is also where I often see a lot of issues…


Log files run astray. A new database might be created or migrated, and the default recovery model is still in “full” recovery mode. A server that relies on a simpler setup might not catch this nor have log backups in place. This means the log file will start growing exponentially, towering over the data file size, and creating hordes of VLFs (look out for a future post about these). I’ve seen a lot of administrators not know how to control this and resort to shrinking databases or files – which is just something you should never do unless your intentions are data corruption and breaking things.


My advice here is keep it simple. If you understand how to restore a full backup, differential backups, and log backups including which order they should be restored in and when to use “norecovery” flags,  or have third-party software doing this for you, you’re all set. If you don’t, I would suggest setting up log backups to run at regular and short interval (15 mins – 1 hour) as a precaution and changing the database recovery models to “simple”. This can keep you protected when accidentally pulling in a database that defaulted to the “full” recovery model and having its log file eat the entire disk.


Pro Tip: Changing your “model” database’s recovery model will determine the default recovery model used for all new databases you create.


Any questions, comments, or feedback are appreciated! Leave a comment or send me an email to for any SQL Server questions you might have!

3CX Phone System on Campus

Dec 23, 2019 by Sam Taylor

Higher Learning at a Lower Cost​

Universities are places where ideas can be communicated freely. What better way to do this, than through a unified communications system like 3CX. As the central communications system on-campus, 3CX offers multiple opportunities to encourage and facilitate learning. It can connect staff members and students with benefits for everyone, including free audio/video calls, low-cost external calls, access to all areas, integrations with other used systems, and more. Let’s examine this use case in more detail.

Affordable Communication on a Shoe-string Budget​

3CX is the ideal tool for universities that require all the advanced features of a unified communication system, without the hefty price tag. Apart from a PBX server, 3CX requires no additional hardware to be installed, making it easily accessible to your staff. The only requirement is a PC with a modern web browser. This simplifies administration, drastically reduces support requests and is a more cost-effective solution overall. What’s more, 3CX provides built-in support for a multitude of IP phones and SIP devices, making it easy to choose a desk phone or SIP device that suits everyone’s budget.

Keep in Contact, at the Lecture Theatre, Dorm or While Roaming

Add the 3CX Android and iOS apps to the mix, and your staff can talk, chat and access a university-wide shared phonebook/directory from their smartphones – wherever they may be. When calling on the move, the app reconnects calls automatically through available WiFi or 4G networks. They can also use Chat to exchange messages and documents while at the campus or anywhere else. 3CX can really empower you to do more with your devices!

Extend Your Reach to Facilitate Teamwork

Universities can typically span multiple buildings and areas, which makes setting up difficult under a single communications solution. Not so with 3CX, as it can unify all your remote offices and dorms using bridges and SBCs (Session Border Controllers), to allow your personnel and students to communicate, irrespective of their location. Academic staff and students can also use WebMeeting at no extra cost, to join on-line video meetings for study groups, or webinar sessions with teaching assistants, lab technicians, and so on.

Never Alone. Integrate & Automate

Traditionally a phone system functions in isolation, with little or no ability to interface with other university systems and services. On the contrary, 3CX includes built-in integration options with Office 365, databases, CRMs and other network-enabled systems.

As a quick example, consider a 3CX script-based IVR (Interactive Voice Response) menu, that services students’ course enrollment requests. The student calls the IVR, enters the ID for the chosen course and 3CX will deliver the student’s telephone number and course selection to the university’s course management system. What’s more, by using the Call Flow Designer (CFD), you can create call flows to automate your procedures, from course billing to announcements via text-to-speech. And CFD does not require any programming knowledge!

Keep in Control of Access & Security

Universities need to maintain controlled and secure access to areas like offices, labs, and dorms. 3CX supports popular video door phone devices which can be used with 3CX. Through this, you can attend to visitors seeking entry, or even control activity and access to specific areas – doing away with employing costly security personnel. You can also use PA systems connected to 3CX, to perform announcements in university common areas, classrooms and halls.

No Master’s Degree Required to Administer

With 3CX, administrators have freedom of choice! Install with ease on LinuxWindowsRaspberry Pi and on popular cloud providers like Google CloudAzure, and AWS. Not only is it easy to install, but easy to manage too. Keep your data safe by securing and managing your backups, recordings and voicemails with flexible options, on local or remote storage (FTP, SSH and SMB). What’s more, administrators can use the built-in Instance Manager to remotely monitor, manage and update a Linux PBX.

In Conclusion​

Universities are by definition communities of teachers and scholars. 3CX bridges the communication gap between these communities facilitates learning and strengthens relationships. It is the perfect fit for organizations that value communication as the primary means of education. And it comes with an affordable price tag, to boot!

Tips and Tricks with MS SQL (Part 6)

Dec 6, 2019 by Sam Taylor

Increase the Number of TEMPDB Data Files

If you’re having issues with queries that contain insert/update statements, temp tables, table variables, calculations, or grouping or sorting of data, it’s possible you’re seeing some contention within the TEMPDB data files. A lot of Microsoft SQL servers I come across only have a single TEMPDB data file. That’s not a Best Practice according to Microsoft. If you have performance issues when the aforementioned queries run it’s a good idea to check on the number of TEMPDB files you have because often times just one isn’t enough.


SQL Server places certain locks on databases, including TEMPDB, when it processes queries. So, if you have 12 different databases all running queries with complex sorting algorithms and processing calculations of large datasets, all that work is first done in TEMPDB. A single file for TEMPDB doesn’t only hurt performance and efficiency but can also slow down other processes running alongside it by hogging resources and/or increased wait times. Luckily, the resolution is super simple if you’re in this situation.


Increase the number of data files in TEMPDB to maximize disk bandwidth and reduce contention. As Microsoft recommends, if the number of logical processors is less than or equal to 8 – that’s the number of data files you’ll want. If the number of logical processors is greater than 8, just use 8 data files. If you’ve got more than 8 logical processors and still experience contention, increase the data files by multiples of 4 while not exceeding the number of logical processors. If you still have contention issues, consider looking at your workload, code, or hardware to see where improvements can be mode.


PRO TIP: When you increase the number of your TEMPDB data files (on its separate drive… remember?) take this time to pre-grow your files. You’ll want to pre-grow all the data files equally and enough to take up the entire disk’s space (accounting for TEMPDB’s log file).


Any questions, comments, or feedback are appreciated! Leave a comment or send me an email to for any SQL Server questions you might have!

Tips and Tricks with MS SQL (Part 5)

Dec 6, 2019 by Sam Taylor

Separate Your File Types

It’s too common and important of an occurrence to not mention the need for file separation in this series. If you’re running Microsoft SQL Server of any version, it’s important you separate your file types to different logical or physical locations. “Data” files, “Log” files, and “TEMPDB” files shouldn’t ever live in the same logical drive. This has a big impact on performance and makes troubleshooting issues much harder to isolate when it comes to finding read/write contention as a suspect.

It’s understandable, the quick need of a SQL Server pops up and you install a Development Edition or Express Edition in 10 minutes leaving file types to their default locations. However, once this system becomes a production server, you better know how to relocate these files to new locations or do it right the first time around. It’ll be easier earlier on rather than after the data grows and needs a bigger maintenance window to move.

To keep with Microsoft Best Practices, you can use a drive naming convention similar to what I’ve listed below to help remember where to place your files. If you’re fortunate enough to have physical drive separation, all the power to you. For most servers I see in this situation, it’s best to start with logical separation at a minimum to yield some powerful results.

Filetype Mapping:

– C:\ – System Databases (default MS SQL installation location)

– D:\ – Data Files

– L:\ – Log Files

– T:\ – TEMPDB Files

– B:\ – Backup Files (with redundancy of course…)

Any questions, comments, or feedback are appreciated! Leave a comment or send me an email to for any SQL Server questions you might have!

Tips and Tricks with MS SQL (Part 2)

Dec 6, 2019 by Sam Taylor

Database Compatibility Levels Left Behind Post-Upgrades & Migrations

What’s common with almost every Microsoft SQL Server I come across that’s recently been upgraded or migrated to? The user database compatibility levels are still stuck in the past on older SQL versions. The compatibility level remains on version of SQL the database was created on. This could be several versions back or a mixed bag of databases, all on different versions. When Microsoft SQL is upgraded or databases are migrated to newer versions, the compatibility levels don’t update. It must be done manually. It’s important to update those databases to the most recent version to take advantage of all the newer version’s features. Good news is it’s very simple to change and only take a minute.

Changing the compatibility level upwards doesn’t really hold any risks unless there’s linked servers involved that run on much older versions of SQL. Even then, it’s usually relatively safe change. If you’re unsure, check with your DBA or reach out to me for questions. All you need to do is right-click the database is SQL Server Management Studio, select “Properties”, choose “Options”, and update the drop-down selector for “Compatibility Level” to your current version of SQL Server. It’s important you don’t forget to update these settings after migrating or upgrading to a newer version of MS SQL Server.

Any questions, comments, or feedback are appreciated! Feel free to reach out to for any SQL Server questions you might have! 

Plants with Sam: Golden Pothos

Nov 8, 2019 by Sam Taylor

Hi, Sam here with our latest issue of Plants with Sam, a blog about plants and how to take care of them. I am writing this series to go hand in hand with CrossRealms’ Let’s Grow initiative. My first post with more details can be found here.

Today I would like to talk about the Golden Pothos. The Golden Pothos is known by many other names, including Devil’s Ivy, because it is impossible to kill. These houseplants are very fast growing so they can be extremely rewarding for beginners.

Golden Pothos are trailing plants so many people put them in hanging baskets, letting them drop towards the ground. You could allow it to climb on a trellis or a stand as well.

Golden Pothos are perfect friendship plants. They are extremely easy to propagate so many people will take cuttings and give them to their loved ones. Just cut it with scissors right below a node, and stick it in water for a while. It takes almost no time for your plant to start growing new roots! Once it has plenty of roots, it will be able to be transplanted into soil. You can also choose to leave it in water for as long as you want, they will thrive pretty much anywhere.

Here are a few tips on how to keep your Golden Pothos plant healthy:


They do well in bright, indirect light, and can handle low light as well. If your pothos is variegated with white, it might not grow as well in low light, or it could start to lose its variegation after a while and become mostly green.


Any well draining houseplant soil will work fine for a Golden Pothos, or no soil at all if you choose to plant in water.


Golden Pothos will be happiest in temperatures between 60-85 degrees Fahrenheit. It can survive occasional chills down to 50 degrees, but it will die if it gets any colder than that.


Golden Pothos will prosper if they are given a balanced houseplant fertilizer once a month with their watering.


Golden Pothos prefer the average household humidity during summer. Think of adding some misting or a humidifier in the winter if your house gets really dry.

If you follow these plant care tips, your Golden Pothos will be happy and healthy. Don't forget to stay tuned for more plant care tips!

Plants with Sam: ZZ Plants

Nov 8, 2019 by Sam Taylor
  • Edit
  • Edit

Hi, Sam here with our latest issue of Plants with Sam! This blog talks about plant care and how to best care for your leafy friends. I am writing this to go hand in hand with CrossRealms’ Let’s Grow initiative. To read more about this, my first post with more details can be found here. 

Today I would like to talk about the ZZ plant. Zamioculcas zamiifolia is it’s full name. This is another houseplant that is very popular amongst new plant owners, due to the fact that it’s hard to kill.

ZZ plants are known for their waxy leaves that reflect light, as well as the interesting pattern the leaves grow in. It is said that the ZZ can help purify the air of toxins as well.

ZZ plants, like the other two plants previously mentioned in this blog, will be fine if neglected. They are drought tolerant and can live in low light without putting up a fight. Although they are notoriously slow growers, these plants can grow to be about 3 feet tall and wide so they won’t completely take over your living room like some others can.

Here are a few tips on how to keep your ZZ plant healthy:


The ZZ can survive in almost any kind of light, aside from full sun or absolutely no light. I would suggest moderate indirect light to keep it happy.


Let the soil dry out completely between waterings, I only water mine about twice a month. These plants could become easily susceptible to root rot or rhizome rot due to its thick stems.​


Most houseplant soils will work fine for the ZZ, as long as they’re fairly quickly draining. If the water sits too long it could start to rot, so try to add some sand or perlite if that happens. ​


Average house temperature is fine for the ZZ, between 60 and 75 degrees fahrenheit would be best. Don’t let the temperature drop below 45 degrees.​


Average house temperature is fine for the ZZ, between 60 and 75 degrees fahrenheit would be best. Don’t let the temperature drop below 45 degrees.​

Plants with Sam: Spider Plants

Jul 16, 2019 by Sam Taylor

Hi, it’s Sam with the next segment of Plants with Sam! If you’re a little late to the plant party, my first post with more details about this blog series and why I’m doing it can be found here. 


Today I would like to talk about the spider plant. These plants are pretty popular for two reasons: they’re super easy to take care of, and given the right conditions, they produce babies like crazy!


I got my own spider plant from a friend, and it was a baby from one of her main plants. The way this works is if the conditions are right (lots of light and warm temperatures, as well as a snug pot), they will send out a shoot from the middle of the plant and at the end of that shoot, a miniature spider plant will grow. It’s best to wait until the tiny spider plant is starting to grow its own roots, then you can just pinch it off and stick it in the soil!

Here are some tips and tricks that will help you care for your spider plant:


Spider plants prefer nice, bright light, but they will also be alright in lower light conditions.


They don’t need water too often, just about every other week or so. Let the soil dry out completely in between waterings. If your water has a lot of salts or minerals in it, it would be best to use distilled water or rainwater.


Most soils that drain quickly work fine for these plants. It’s best to use soils that don’t have a lot of fertilizer in them.


Spider plants like it a bit on the warmer side, so it’s best to keep the temperature between 70 and 90 degrees Fahrenheit. They will survive in temperatures as low as 35 degrees, but they will not grow much if the temperature is under 65.


Less is more when it comes to fertilizer for spider plants. Use a diluted houseplant fertilizer in spring and summer.

If you follow these tips, your spider plant will have no issues being happy and healthy! Don’t forget to stay tuned for more plant care tips!

My Experience at CrossRealms

Jul 16, 2019 by Sam Taylor

Hi, my name is Dayoung KO, I’m from Korea and I am working as a marketing intern at CrossRealms. I am studying abroad here at IIT, and this internship is a part of my schooling. Since the internship class that I’m in is only scheduled for 6 weeks, this will be my last week here at CrossRealms.


Thinking back over the past few weeks at CrossRealms, I can describe the experience in a few words: “I’ve learned a lot.” I remember the very first day I met Usama, the president of CrossRealms. He told me that he wants me to learn as much as I can from here as well as share my culture with my co-workers who are from different cultures. As a result, I learned not only about the marketing field I’ve been working in, but I’ve also learned about building personal relationships with coworkers with different cultural backgrounds.


One thing I enjoyed about CrossRealms, is that every employee is free to speak their mind. Regardless of what kind of work I’ve done, I participate in almost every meeting for marketing. My co-workers always asked my opinion and had me speak out during the meeting. I felt totally free to give my opinion and ask questions when I did not understand certain things. I could feel myself building real relationships with them and felt that they have truly respected me. My co-workers were interested in Korean things, so we went out as a company to Korean restaurant so that I could talk about Korean culture and food. I know that not all the companies in the US have the same culture, but the culture of CrossRealms is totally different from Korea, in a positive way.


I really appreciate having been a part of CrossRealms though it was only for 6 weeks. Thanks to Usama, Sam, Unme, Johanna, Candice, Matt, Constantine, and Jasper! I hope to see you guys again.


안녕하세요, CrossRealms에서 마케팅 인턴으로 일하고 있는 한국에서 온 고다영입니다. 인턴십 과정이 포함된 프로그램으로 IIT에서 방문학생으로 수학 중입니다. 이 인턴십 과정이 6주로 예정되어 있기 때문에 이번주가 CrossRealms에서의 마지막 주가 될 것입니다.


CrossRealms에서의 지난 몇 주를 회고해보면 딱 한 문장으로 설명할 수 있을 것 같습니다. “많은 것을 배웠습니다.” 창업자인 Usama를 만났던 첫 날을 떠올리면 그가 저에게 했던 말이 기억에 남습니다. 그가 제게 기대하는 유일한 것은 제가 여기서 배울 수 있는 최대한 많은 것을 배우고 다양한 문화권의 동료들과 저의 문화를 나누는 것이라고 했습니다. 그 결과로 저는 제가 일했던 마케팅 분야뿐만이 아니라 문화적 차이와 인간관계를 맺어가는 과정을 배울 수 있었습니다.


이 회사에서 좋았던 점 중 하나는 모든 동료들이 서로의 의견에 스스럼없이 자신의 생각을 말합니다. 제가 어떤 업무를 하고 있던 상관없이 저는 거의 모든 마케팅 회의에 참여했는데


동료들과 상사는 항상 제 견해를 물어봤고 회의 중에 제 의견을 피력할 수 있도록 도와주었습니다. 그 결과로 자유롭게 제 의견을 말하고, 궁금한 것이 있거나 이해가 안됐을 때 스스럼없이 질문할 수 있었습니다. 저는 그들과 개인적인 인간관계를 형성해가고 있음을 느꼈고 그들이 저를 존중해준다는 느낌을 받았습니다. 또한 모든 동료들이 한국에 관심이 많아서 다같이 한국음식점에 가서 문화와 음식을 나누기도 했습니다. 미국의 모든 회사의 문화가 이와 같지 않은 것은 사실이지만, CrossRealms의 사문화는 완전히 긍정적인 의미에서 한국과는 몹시 달랐습니다.


비록 6주에 불과했지만 그 동안 CrossRealms의 구성원이 될 수 있음에 감사했습니다. 제 인턴십 과정은 끝났지만 저는 계속해서 CrossRealms와 함께 나아갈 예정입니다. Usama, Sam, Unme, Johanna, Candice, Matt, Constantine, 그리고 Jasper까지 모두에게 고맙습니다! 다시 만나기를 기대할게요

Written by Dayoung KO

글: 고다영