Viewing 15 posts - 6,976 through 6,990 (of 14,953 total)
The function uses the DBCC command, if I'm not mistaken.
March 1, 2010 at 3:39 pm
You'd need to build a CLR assembly for that.
March 1, 2010 at 12:45 pm
There's an undocumented DBCC command that can read the log file. The data it provides may or may not do what you need.
It's "DBCC Log()". The parameters that...
March 1, 2010 at 9:36 am
jcrawf02 (2/26/2010)
Steve, saw you were re-learning Pythagorean theorem, can't help but poison your mind with a joke:
An Indian chief had three wives...
February 26, 2010 at 9:48 am
I'm not entirely clear on what you mean.
Do you mean you want to restrict the location of the files (mdf and ldf and ndf)? Or the server(s) they can...
February 26, 2010 at 8:34 am
Is it possible the process you killed is still rolling back? That's what it sounds like to me.
February 26, 2010 at 8:30 am
I just performed this test:
SET NOCOUNT ON;
CREATE TABLE #T (
ID INT IDENTITY PRIMARY KEY,
Section INT NOT NULL,
DT DATE);
INSERT INTO #T (Section, DT)
SELECT N1.Number, DATEADD(day, CHECKSUM(NEWID())%36525, '1/1/2000')
FROM Common.dbo.Numbers N1
CROSS JOIN Common.dbo.Numbers...
February 26, 2010 at 8:17 am
There are a number of ways to achieve that, but the simplest is to join the two tables together in your query. Are you familiar with how to do...
February 26, 2010 at 7:57 am
This kind of design can be done efficiently if you have the front end generate a GUID, instead of using a database-generated integer ID. The GUID can then be...
February 26, 2010 at 7:55 am
Asha.Richardson-1129890 (2/25/2010)
I am not sure about what you said.... The table I am updating has many more rows than the tables I am not updating..
It's not a question of which...
February 26, 2010 at 7:21 am
In that case, with file formats changing every few years, I'd be inclined towards setting up XML definition files and using OpenRowset Bulk to import the data.
I've used that method...
February 26, 2010 at 7:06 am
The table(s) you aren't updating have more rows than the table you are updating. That's what causes that.
Try this, you'll see what I'm talking about:
CREATE TABLE #T1 (
ID INT...
February 25, 2010 at 3:11 pm
On another note, you shouldn't be subtracting 3 milliseconds from a date to define the end of a datetime range. The right way to do it is to use:
date>=@StartDate...
February 25, 2010 at 3:05 pm
The reason the version you were using before worked is because SQL was doing a string-to-datetime conversion implicitly behind the scenes. It can't do that if the string can't...
February 25, 2010 at 2:59 pm
Viewing 15 posts - 6,976 through 6,990 (of 14,953 total)