Robert Marda

I have worked for bigdough.com since 18 May 2000 as an SQL Programmer. My duties include backup management for all our SQL Servers, mentoring junior SQL Programmers, and serving as DBA while our DBA is on vacation. I develop, test, and deploy stored procedures and DTS packages as well as manage most major SQL projects. Our offices are located in Bethesda, Maryland. Before working for bigdough, I worked for Telos Corporation in Ashburn, Virginia. I started learning T-SQL and using SQL Server 7.0 on 22 March 1999. In April 1999 I was given the position of Senior Database Analyst/Administrator at Telos Corporation. I have been married to Leoncia Guzman since 23 Jul 1994. We met in the Dominican Republic where I lived for about 2 years as a missionary. We have 4 children, Willem (age 8), Adonis (age 6), Liem (age 4 and a half), and Sharleen (age 3 and a half). My hobbies include spending time with our 4 children (we play chess, dominos, mancala, and video or computer games together), keeping tropical freshwater fish, breeding and training parakeets, coin collecting (US and foreign), and geneology. I have a 55 gallon tank and 20 gallon tank. I have many kinds of fish (such as a pleco, tiger barbs, mollies, cichlids, tetras, and guppies) I also have a small aquatic turtle. I last updated my bio 30 Mar 2004.
  • Interests: Sailing, camping, computers, reading and writing sci-fi and fantasy books.

SQLServerCentral Article

Case Study: Importing New Data Without Emptying Existing Tables

The challenge for Robert Marda was to devise a way to keep the data available at all times while importing the new data, detect if a full or daily update was received and run appropriate data pumps, put in sufficient fail safes to ensure bad data would not get imported, and to make the process automatic including notification to pagers upon failure. Robert shows you how he did it here.

You rated this post out of 5. Change rating

2003-01-09

8,200 reads

SQLServerCentral Article

Performance Adding Hints

During the process of performance tuning queries and stored procedures there comes a time when you will notice that the execution plan selected by SQL Server is not the best plan. On occasion, everything you try doesnt cause SQL Server to choose the best way to execute your code. These are the times when hints can improve performance.

5 (2)

You rated this post out of 5. Change rating

2002-09-10

9,405 reads

SQLServerCentral Article

Understanding Execution Plans Part 1

The purpose of this article is to give you a working knowledge of how to view and understand query execution plans for SQL Server. This is part 1 in a series of articles that will walk you through understanding execution plans to help you improve your queries.

4.44 (16)

You rated this post out of 5. Change rating

2002-07-26

24,222 reads

SQLServerCentral Article

Multi-Server Administration

Multi server administration allows you to create jobs and maintenance plans once. You can then monitor and change them from one SQL Server. View job histories and statuses for 2, 4, 10, or more SQL Servers from one master SQL Server. See how you can simplify your administration duties with multi server administration.

5 (3)

You rated this post out of 5. Change rating

2002-05-06

13,184 reads

Blogs

A New Word: Vicarous

By

vicarous – adj. curious to know what someone else would do if they were...

SQL Server Cross Platform Availability Groups and Kubernetes

By

Say we have a database that we want to migrate a copy of into...

Using Managed Identities with Azure SQL DB

By

We are trying to get apps and users off of using SQL accounts to...

Read the latest Blogs

Forums

We Stink!

By Grant Fritchey

Comments posted to this topic are about the item We Stink!

View works for me ...but doesn't return results for a user in SSMS but no errors

By krypto69

Hi I have this view to check if a job is running:   SELECT...

Dark mode, other color schemes

By mjdemaris

All, if you are like me and do not care for the built-in color...

Visit the forum

Question of the Day

Internal Checkpoints

Certain internal SQL Server actions cause internal checkpoints. Which of these actions does not cause an internal checkpoint?

See possible answers