5 Body Language Mistakes to Avoid in Interviews

Marissa Brassfield

Non-verbal cues can make or break an interview. This list of body language mistakes compiled by Jacquelyn Smith for Forbes will help you avoid unintentionally sending the wrong message.

1. Bad handshake. Ideally, your handshake should be firm yet not overbearing. "The secret to a great handshake is palm-to-palm contact," said body language expert Patti Wood to Forbes. "Slide your hand down into the web of theirs and make palm-to-palm contact. Lock thumbs with the hiring manager, and apply as much pressure as he or she does."
2. Close-talker. Respect your interviewer's personal space. Avoid standing too closely to him or her.
3. Defensive postures. Avoid crossing your arms at all costs. Instead, talk with your hands to engage your interviewer and convey your enthusiasm.
4. Fidgeting. Avoid bombarding your interviewer with distractions like asymmetrical body language, biting your nails or playing with your hair. Focus on making eye contact when your interviewer addresses you. "It's okay for the candidate to look away when he or she is talking," said Wood. "It's normal to look around when you're speaking because you're accessing different parts of the brain by moving your eyes. But be attentive and make eye contact when the interviewer is speaking."
5. Looking uninterested. Avoid checking your phone or watch during your interview. Pay close attention to your facial expressions, both while you talk and while you listen to others speak.

Do These 5 Things Before Your Next Interview and Get the Job

Jen Hubley Luckwaldt

Interview prep is tricky not because you don't know what to do to get ready, but because you know too much about what you could do. Before you get bogged down in endless practice interview questions, make sure you have these things checked off your pre-interview to-do list.

1. Research the company.

You probably know at least a little something about your prospective employer by the time you make it to the interview stage, or your resume and cover letter wouldn't have helped you snag the interview. Still, now's the time to make sure you have a full grasp of the company history, including its mission and founders, and are up-to-date on its latest news. Start with the corporate website and the organization's profile in PayScale's Research Center, and then do a Google News search, and take a look at the company's social media profiles. Know how long they've been around, what challenges they've faced, who their competitors are. Most importantly, figure out what their problems are -- especially the ones that hiring you would solve.

2. Investigate your role.

Look up the job title and find out what responsibilities typically go with that role. Think about your experience, and how it would fit. Take a salary survey to determine a salary range. Hopefully, you won't be asked to get into specifics, but if you are, have an idea of what you'd like to hear and what you'd accept.

3. Get to know the key people.

If possible, ask for the names of the people you'll be speaking with, so that you can look them up on LinkedIn before the interview. If you're interviewing with folks outside of HR, pay special attention to their background and experience. Note any points of commonality with your background.

4. Prepare for common questions.

Avoid giving canned answers to common interview questions by concentrating on demonstrating how your skills, experience, and passion can help the company solve its problems. Practice, but focus more on remembering your own best qualities than on memorizing pat replies.

5. Practice confident body language.

Sit up straight, make (just enough) eye contact, and shake hands firmly -- in short, practice looking like someone who deserves to get the job.

5 Reasons to Wake Up Earlier (and 2 Reasons to Skip It)

Jen Hubley Luckwaldt

Could you wake up two hours earlier every day? Rachel Gillett at Fast Company tried it for a week, rising at 6:30 a.m. and tallying up the ways in which it improved her productivity and happiness, both in her personal life and at work -- plus, a few of the challenges involved in resetting her daily clock.

First things first: waking up earlier won't work for everyone.

1. Experiments like these are easier if you're not a working parent.

"Many [parents] pointed out that they rarely have the luxury of sleeping until 6:30 a.m., which would make their wake-up time for this project much earlier," writes Gillett. "This seems implausible, though some have done it."

Her colleague Scott Thigpen, for example, regularly rises at 3:50 a.m., in order to have some peace and quiet before his two children wake up. He often meditates during his morning hours, which sometimes just consists of quietly enjoying a cup of coffee without interruption.

2. Not everyone's work and life rhythms are the same. 

If you're a morning person, waking up earlier buys you extra hours to create and think, but if you're a night person, you might just feel exhausted, as if you're tacking on more unproductive time long before your brain kicks in.

If you can get stuff done in the morning, however, there are rewards to getting up much earlier than usual, including:

1. Increased energy, especially if you, like Gillett, use the time to work out first thing in the morning.

2. Weight loss. Again, the early morning workouts might help, but so can having a bit more time to plan meals, eat slowly, and just generally reduce stress.

3. Improved punctuality. One reader tells Gillett that getting up earlier makes it easier for her to make early-morning meetings and flights.

4. More time to yourself. Want to train for a marathon, write a book, or pick up a hobby you abandoned years ago? Getting up earlier than everyone else is a great way to do it.

5. Less rushing around. Some stress is healthy, inspiring us to do our best work, strive for a goal, or improve ourselves. The pressure we feel when we're constantly just a few minutes behind isn't that healthy kind of stress. Get up earlier, and you start the day ahead, instead of behind.

 

Execute Sql Commands through Command Prompt

Here I am sharing that how can we execute SQL Commands through Command Prompt.

Using this command line utility, we can also fire queries and execute files, etc.

Sample Syntax:

SqlCmd -S servername -U "username" -P "password" -q "sql command"

 

Ex.

SqlCmd -E -S 192.168.0.1\Sql2008 -Q "BACKUP DATABASE Practice TO Disk='C:\dbbackups\db_Practice.bak';BACKUP LOG Practice TO Disk='C:\dbbackups\db_Practice.bak';"

 

SqlCmd -S 192.168.0.1\Sql2008 -U "sa" -P "sa@123" -q "RESTORE DATABASE Practice FROM DISK = 'e:\Backups\db_Practice.bak' WITH MOVE 'Practice' TO 'G:\DBBackups\Practice.mdf',MOVE 'Practice_log' TO 'G:\DBBackups\Practice.ldf';"

 

For more options check below detail:

 

sqlcmd 

   -a packet_size 

   -A (dedicated administrator connection)

   -b (terminate batch job if there is an error)

   -c batch_terminator 

   -C (trust the server certificate)

   -d db_name 

   -e (echo input)

   -E (use trusted connection)

   -f codepage | i:codepage[,o:codepage] | o:codepage[,i:codepage]

   -h rows_per_header 

   -H workstation_name 

   -i input_file 

   -I (enable quoted identifiers)

   -k[1 | 2] (remove or replace control characters)

   -K application_intent 

   -l login_timeout 

   -L[c] (list servers, optional clean output)

   -m error_level 

   -M multisubnet_failover 

   -N (encrypt connection)

   -o output_file 

   -p[1] (print statistics, optional colon format)

   -P password 

   -q "cmdline query" 

   -Q "cmdline query" (and exit)

   -r[0 | 1] (msgs to stderr)

   -R (use client regional settings)

   -s col_separator 

   -S [protocol:]server[\instance_name][,port]

   -t query_timeout 

   -u (unicode output file)

   -U login_id 

   -v var = "value" 

   -V error_severity_level 

   -w column_width 

   -W (remove trailing spaces)

   -x (disable variable substitution)

   -X[1] (disable commands, startup script, environment variables and optional exit)

   -y variable_length_type_display_width 

   -Y fixed_length_type_display_width 

   -z new_password  

   -Z new_password (and exit)

 

   -? (usage)

 

 

For Detail about "SqlCmd" Visit: http://msdn.microsoft.com/en-us/library/ms162773.aspx