I have been working in the Business Intelligence sector for over 7 years. The foundation for my interest in databases was laid at Kreissparkasse Heilbronn (a local bank in Germany): After my apprenticeship as a banker (which didn’t turn out to be my premier job choice 😉 ) I slipped in the local database team and first got into contact with SQL. My main job task was selecting adresses for mailings by writing SQL statements. SQL was quite fascinating for me at this point in time but challeging as well, as it was difficult to get a thorough understanding by “training on the job”. Later on I went to Hochschule Furtwangen University (HFU) and took my Bachelor of Science by studying Wirtschaftsinformatik. At university I was quite open for all topics like logistics, java programming, networking and database design. In the end SQL databases and BI was the most fascinating thing for me. I found a great supporting company for my bachelor thesis which focused on building a data warehouse on SAP using the BI content (kind of click and run BI building bricks for SAP modules). This gave me the chance to learn data warehousing from scratch.
I haven’t used SAP any more since then (which wasn’t a deliberate decision) but it was clear to me that business intelligence is the most interesting technology to work with. My first job after graduation was at Printus, a major german office supplier. This was a great time working at a company, which was really committed to their BI investment learning from some of the best DB and BI experts I have met so far. I have been working with Oracle and Microsoft database products there. After 3 years I moved on for a new challenge building a completely new data warehouse system from scratch at 3C, a small company focused on outsourcing services in claims management for insurance companies. Nowadays I am working with Microsoft SQL Server and BI still is very appealing to me. Since 2015 I also take responsibility as a DBA, which gives me the opportunity to learn a lot of new things. I am happy to extend my knowledge about databases in general and SQL Server in specific. In my free time I enjoy attending usergroup meetings of PASS.
Of course there’s a non-SQL-part of my live as well in which I am a husband and father, enjoy playing music (piano, accordeon) and singing as well as travelling with my wife.
Exclusion of liability and statutory references
This blog contains links to other sites in the Internet. Despite the care taken in their selection, I have no influence on the content and/or design of linked pages and therefore accept no responsibility for such. This declaration applies to all links on this blog and to the content of all pages to which the attached links lead.
In my blog entries I endeavour to respect the copyrights of texts, graphics and photographs used or to incorporate only texts, graphics and photographs that have been created by myself or do not require a license. Should an unintentional breach of copyright nevertheless occur, upon receipt of notification I will immediately remove the offending object from my blog or mark it with the appropriate copyright.
4 thoughts on “About me”
kannst Du mir bitte Deine Vortragsfolien von Dienstag PASS zusenden evt. inkl. Links zu GitHub? Ich konnte leider nicht bis zum Ende dabei sein. Aber ein sehr guter Vortrag. Und ich weiß nicht ob ich aus Hannover PASS Gruppe an Deine Vortragsfolien rankomme.
Viele Grüße und Danke für Deine Zeit und super Vortrag.
danke für das Feedback. Die Unterlagen findest du direkt hier auf der Seite unter http://www.martinguth.de/presentations/ .
Maybe you can shed some light on the SQL Server “Simple” recovery model. If you have open transaction(s) in “Simple” recovery model can the log file grow and can it grow to the extent that is runs out of disc space on the OS drive?
sorry for getting back to you that late. The Simple recovery model is no guarantee that your log file doesn’t grow. As explained in https://www.mssqltips.com/sqlservertutorial/4/sql-server-simple-recovery-model/: “Every transaction is still written to the transaction log, but once the transaction is complete and the data has been written to the data file the space that was used in the transaction log file is now re-usable by new transactions.”
In essence: If you have open transactions, SQL Server needs the space to write the transaction log information to the log to be able to rollback the transaction or do crash recovery on startup (might involve undoing (“rolling back”) work by transactions which didn’t get committed). So if you start a transaction modifying data and leave it open and running for a while you should experience log file grow and of course this growth could also fill up your drive if space is already scarce or the process runs for days without anybody noticing.
Technically space is reclaimed as soon as a CHECKPOINT operation is initiated (you can also but generally needn’t initiate it manually). You can read more about it here: https://docs.microsoft.com/en-us/sql/relational-databases/logs/database-checkpoints-sql-server?view=sql-server-ver15