What is Code Drop? As a Prod DBA How to work on the Crop Drop in SQL Server

Question

What is Code Drop? As a Prod DBA How to work on the Crop Drop in SQL Server

nagkarjun1

Ten Centuries

Points: 1020
More actions
July 16, 2012 at 8:01 am

#264216

What is Code Drop? As a Prod DBA How to work on the Crop Drop in SQL Server?
Can any one explain me with this concept?

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Lowell SSC Guru Points: 323504 More actions · Answer 1

it sounds like the promotion of a specific set of both database changes and application changes that would occur together, like when an application upgrades from version 1 to version 2.

it could have a more specific meaning to your company, but that's what it sounds like to me.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Orlando Colamatteo SSC Guru Points: 182276 More actions · Answer 2

One place I worked use the term "Code Drop" to mean exactly that, a synchronized deployment of database code and however many applications relied on the database changes.

There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato

Revenant SSC-Forever Points: 42467 More actions · Answer 3

In my culturally sanctioned dictionary it means passing of the code that is related to a particular deliverable to QA. It means that the respective dev says "I am done, now tell me what is wrong with it and I will fix it."

In a reasonably managed shop this means that the dev will not make another drop until s/he gets QA feedback, otherwise QA would be working with ever-changing base and spent inordinate time on regression testing.

Grant Fritchey SSC Guru Points: 398679 More actions · Answer 4

In general, to coordinate databases with code, the best approach I've found over the years is to get your database into source control. That used to be quite difficult, but there are several tools that make it pretty easy now. If this is what you're looking for, let me know and I'll explain further.

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning

Robert Davis One Orange Chip Points: 28027 More actions · Answer 5

A "code drop" is a completed build ready for deployment to an environment. That could be production, QA/Test, etc.

Your engineering team should be providing code drops that are automated processes as much as possible (not "as much as was easy to do") and includes clear instructions on how to deploy the code drop as well as a well-defined rollback plan in case the deploymnet is not sucessful. If it does not include these things, then it should not be deployed to production.

My blog: SQL Soldier[/url]
SQL Server Best Practices: SQL Server Best Practices
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring[/url]
Microsoft Certified Master: SQL Server, Data Platform MVP
Database Engineer at BlueMountain Capital Management[/url]

sujangurudu.sql SSC Rookie Points: 29 More actions · Answer 6

When i worked in a company, they were code drops from a different client for every consecutive weeks in a month.

My company acquired a new company. So, obvious reasons my company follows a different schema from the acquired ones. We used to ask for data according to our database schema.

Code drop may be in the format of store procedures or views or .bak files. When you execute the files /restore the databases it in your server the data should be flown and pushed from one server to other server.