You could use the linked server trick I used here: http://spaghettidba.com/2011/11/16/discovering-the-output-of-dbcc-commands/

I don't recommend it, though.

Sort order must be explicitly defined in the ORDER BY clause.

One way to accomplish what you're after could be this:

SELECT *

FROM (

Select 'table1' as SRC, employee,employeename...

Glenstr (1/3/2012)

---

I think Oracles alter database noarchivelog; basically does the same thing as putting an MSSQL database into simple recovery mode, it just has the database reuse the log space...

GilaMonster (1/3/2012)

---

Grant Fritchey (1/3/2012)

---

There is courseware you can purchase, but with only 2 days to prep, you're effectively going to be reading from the slides. Here's a place online that...

SQL Kiwi (1/3/2012)

---

Gianluca Sartori (1/3/2012)

---

Very popular in Oracle too (SELECT ... FOR UPDATE). Sometimes Often devs do this in PL/SQL code used in forms and hold the lock until the...

thatishari (1/3/2012)

---

Hi all,

I am modifying a table which has 6 columns with 1 column as not null. now what i have to do is have to add another column as...

We're not behind your shoulders and can't see your screen. 😉

Can you post your code (or a meaningful part of it)?

SQL Kiwi (1/3/2012)

---

Michael Valentine Jones (12/29/2011)

---

This code shows a simple way to eliminate those problems using a rowversion column in the table to make sure it has not changed since...

SELECT

SUBSTRING(SerialNumber, PATINDEX('% %', SerialNumber) + 1, PATINDEX('%[^0-9 ]%', SerialNumber) - PATINDEX('% %', SerialNumber) -1) AS SerialNumber,

...

Jeff, you're simply GREAT!

I should print your...

Which operation?

As I said before, it's not something on the backup/restore. You must have messed with the backup.

Try taking another backup and restore it with replace: you will see all the...

I'm sorry, it's unclear to me.

You took a backup, restored with a different name, took another backup, restored with replace and you don't see the records in the first backup...

I think you all should take a deep breath and consider stop posting to this thread.

If you don't have anything nice to say, don't say anything at all.

You're not...

There's nothing wrong with COALESCE, it's the assignment in the SELECT list that makes the code unreliable.

Here's a couple of articles on the subject:

http://www.sqlmag.com/article/tsql3/row-concatenation-solutions-aren-t-all-equal

http://www.simple-talk.com/sql/t-sql-programming/concatenating-row-values-in-transact-sql/