komal145 (6/10/2016)

---

Here is the agebucket column: 12-24

need lowerbound :12 and upperbound:24

Right now I wrote expression in tsql something like below:

Substring([AgeBucket],0,CharIndex('-', [AgeBucket])) As LowerBound

,LTRIM(REPLACE(Substring([AgeBucket],CharIndex('-', [AgeBucket]),3),'-','')) As UpperBound

How can we re-write...

komal145 (6/10/2016)

---

i have destination table with not null columns. So in oledb destination mapping from source to destionation. i selected "ignore" and trying to insert data. The task keeps failing....

--deleted

etl2016 (6/9/2016)

---

Dear All,

We use ROW_NUMBER () to partition results and hand-pick the needed records, mostly to address duplicate records scenario.

However, how do we sense that there is a potential threat...

Try

Case when LogDate = cast(LogDate as date) ...

Lynn Pettis (6/8/2016)

---

Brandie Tarvin (6/8/2016)

---

<headdesk>

User asks me to move this bit of code into QA:

ALTER TABLE MyTable

ADD Col1 INT,

Col2 INT

GO

I push back and say "Please add...

Response removed as a result of the change from 'rows' to 'columns'!

Really? So what is this?

https://community.oracle.com/community/database/developer-tools/sql_and_pl_sql

So your problem is solved?

OK. Next step is to remove the WHERE conditions one by one and rerun. Hopefully, removing one of the conditions will make rows appear ... then we can focus troubleshooting...

This is difficult, because we don't know what your data looks like. But first of all, here is your query again, reformatted for readability:

SELECT CustomerAccount.AccountNumber

, ...

Snargables (6/8/2016)

---

OK, so you agree, it shouldn't run any faster simply because i'm remoted into the prod server.

What about querries? Should the same logic apply? It's been my experience...

GilaMonster (6/7/2016)

---

Luis Cazares (6/7/2016)

---

That's...

Yes, but ...

I'd suggest trying out a couple of non-destructive queries first ... and definitely in a test environment ... just to get familiar with it.

Note the comments about sp_msForeachDB...

Some pratting about is required to handle the single quotes embedded in your SQL, before it can be passed to an executor proc.

One way is to replace all single quotes...