@JNK That's kind of what I thought... They were offering really good money for London, but seemed to be looking for odd and arbitrary skills and were proud of dubious things like building their own SQL Server monitoring system
I nearly walked from this place based on the pre-screening questions. "How many threads does SSIS use natively" and it's some stupid formula that has never affected my ability to design a package
My old boss and I differed on interview styles. He liked to see that someone knew X, Y and Z. I prefer a conversational style - talk to me about what you've done and see how well they understand and can communicate what they did. What went well, what blew up in their face, what lesson did they learn
But then you might throw out someone like James who couldn't remember the syntax for unpivot. Or, you get them flustered thinking "god, it's one of these interviews"
As an admin, if I'm interviewing for a position, I need to establish skill set. Because if they don't have certain abilities, hiring them means I have to baby sit them.
When checking the backups for this database it appears that the last backup was done on 10/10/2014. I don't think that backing up to that date is going to be a possibility. We would lose several months of data. — jbartley1 min ago
@billinkc I approach pre-cons differently than regular sessions, I actually fill the slides with info because I know half of them will fall asleep at various points, and want them to take the info with them
But yeah I do tend to talk fast. At intersection I finished my 75 minute talk on SQL Server 2014 features in 45 minutes.
It wasn't for shortage of info, I was just a motor mouth
I need to experiment with longer (and shorter) talks. I think I can put a talk together for the 60-75 minute format. The 2 hour session I did at Mile High Tech Con got painful after a while
I am not a DBA...it is not my responsibility. It has become my responsibility because this allocation error is not allowing a backup to run on the server that I need to run a backup on. As I stated earlier, the database team here should be replaced with competent DBAs. — jbartley34 mins ago
I've never understood the "it's not my responsibility" response. Unless you're a consultant with a SOW spelling out what you're supposed to do, we all work for the same company and it's your responsibility to correct things that are broken. If you aren't physically capable of changing it, escalate until you get someone who is
@Zane It depends on what they are going for. Some SQL Sats go for big names first, others go for encouraging new speakers first, some try to strike a nice balance.
And some don't look at the speaker at all, and just pick based upon session abstracts.
It looks like they had about 35 speakers submit, so there is a possibility they could take everyone, depending on the size of the venue.
We found the danger in accepting everyone last year... some people had little to no people in their room. Although that might have been the combination of Bob Ward + Glenn Berry hogging all the DBA audience.
The query below returns the following error:
"Invalid length parameter passed to the LEFT or SUBSTRING function."
When it runs correctly, it returns the case_id and the data between the 8th and 9th tab characters in the ct.case_text column.
The parameters for the SUBSTRING function in the que...
use a famous modulo procedure ( http://esolangs.org/wiki/brainfuck_algorithms will help you)
>+++++++++++[-<+++++++++++++++>] # initialize 165 at first cell
>++++++++++<<[->+>-[>+>>]>[+[-<+>]>+>>]<<<<<<]>>[-]>>>++++++++++<[->-[>+>>]>[+[-
<+>]>+>>]<<<<<]>[-]>>[>++++++[-<++++++++>]<.<<+>+>[-]]<[<[->-
@swasheck pretty much, these poor sheep have been brainwashed into thinking this thing is the panacea of all T-SQL problems. It works, ok, but stop calling it fast, because it is anything but.
throwing hardware at a performance problem is never going to solve the issue. Not sure how Pagination has anything to do with this. I don't use PIVOT in t-sql. I use cross tabs instead. They are easier to code and the performance is better too. All things being equal I would much rather push clean data to the application layer and let it deal with the formatting. — Sean LangeJan 29 at 16:10
but that is if you wnat delete all, but in this case is to avoid errors like that guy that just execute the first line, he has the where in the second line
@EmilioGort There is no way for SQL Server to know that the user meant to highlight a where clause. If you want to allow delete everything if they really mean it, then support that through a specific stored procedure.
thanks @AaronBertrand, I was thinking in BEGIN TRANSACTION @TranName; GO USE AdventureWorks; GO DELETE FROM AdventureWorks.HumanResources.JobCandidate WHERE JobCandidateID = 13; GO
@EmilioGort stop thinking about "delete without a where clause" and think about either (a) forcing DML through stored procedures or (b) using an instead of trigger to prevent deletes that delete all rows.
@AaronBertrand well there's a shock. i was right about something. i dont think i'd want to implement dynamic sql for something so important, though :)
> A conspiracy theory was out late Sunday night after the 28-24 loss to the New England Patriots in the Super Bowl that Carroll changed the play to a pass so Russell Wilson would win the MVP award and not Marshawn Lynch.
Because of the SQL standards that are enforced we have to follow these restrictions: - Cannot use Stored Procedures - No single piece of code to contain **more than 3 table joins** - No single piece of code to result in more than 30 million rows of output
I have been using and loving Jeff Moden's string splitter just about since it came out.
Tally OH! An Improved SQL 8K “CSV Splitter” Function
The query below returns the following error:
"Invalid length parameter passed to the LEFT or SUBSTRING function."
When it runs correctly, it returns the case_id and the data between the 8th and 9th tab characters in the ct.case_text column.
The parameters for the SUBSTRING function in the que...
