Viewing 15 posts - 20,866 through 20,880 (of 22,202 total)
Evidently, geeks with weapons!
:w00t:
March 12, 2008 at 9:18 am
The good news is, it's working. I just finished the install and I'm looking at the February CTP, finally.
March 12, 2008 at 9:02 am
Get rid of the TOP 1 sub select in the SELECT clause, that's effectively a cursor in your code.
Try using a LEFT JOIN?
March 12, 2008 at 8:56 am
The axe is such a clumsy weapon. How about a katana? Unless the interviewers are wearing armor, then I'm going for a good broadsword.
No pork chops!
How about just coming as...
March 12, 2008 at 8:30 am
Oh, and it happened to one other guy at my company too. He was able to get his uninstalled. Mine wasn't. I'm probably going to be rebuilding my lap top....
March 12, 2008 at 7:30 am
I ran into a problem. It didn't prevent 2005 from working, but it did cause parts of the GUI in SSMS to stop working. I would be very cautious about...
March 12, 2008 at 7:29 am
Because you're grouping on everything, you'll get the max date for a distict select. You might want to look at something like:
SELECT c.consultantid
...
March 12, 2008 at 7:12 am
Do I have to setup a stored procedure, or just write a select satement?
Yes.
Oh, a little more? Fine.
You can do either. The preferred approach when building applications is to create...
March 12, 2008 at 6:10 am
Another question far too dense to answer in a forum like this.
However, a few pointers (and, as with everything in SQL Server, there are exceptions to every one of these...
March 12, 2008 at 6:00 am
Another variation on what everyone else has done would be this:
SELECT a.OH_DOC_TYPE,
a.OH_DOC_NUM,
a.OH_PO_NUM,
...
March 12, 2008 at 5:53 am
I doubt it's going to help, but you can call this in a cross database query. I used the example from BOL:
SELECT 'Index Name' = i.name, 'Statistics Date' = STATS_DATE(i.object_id,...
March 12, 2008 at 5:48 am
Nope. Not through anything available in the system for your basic queries. There is a way to output status on restores & backups & such.
March 11, 2008 at 12:12 pm
You can do this:
INSERT INTO MyTable1
DEFAULT VALUES
Then, with that, you can capture the values you inserted like this:
CREATE TABLE #Id ( id INT )
INSERT INTO onecolumn
OUTPUT inserted.id
...
March 11, 2008 at 12:09 pm
It means your joins are probably returning more than one row from one of the tables. That's a pretty normal occurrence when using left joins. I'd first investigate the data...
March 11, 2008 at 8:45 am
Viewing 15 posts - 20,866 through 20,880 (of 22,202 total)