Viewing 15 posts - 18,091 through 18,105 (of 59,069 total)
bsmith 63193 (3/16/2016)
Thank you for the replies. Would it be recommended to use decimal over numeric because it is a wider held standard?
The really cool part about standards is... there...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 7:35 pm
RV16 (3/16/2016)
So I just used that way:
And now its solved. So I just put answer anyone...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 6:36 pm
Sergiy (3/16/2016)
Do not turn birthday to ages, turn predefined ages into date ranges for birthdays:
Best idea I've heard in a month.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 6:33 pm
mister.magoo (3/16/2016)
Jeff Moden (3/16/2016)
So, what would you prefer to see with the following (using a cte as if a Table Source)...
WITH cteTestData (RowNum,CSV) AS
(
SELECT 1, '1,2,3' UNION ALL
SELECT...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 6:31 pm
bsmith 63193 (3/16/2016)
Is there a preferred recommendation by database administrators of whether to use Decimal or Numeric data types for values that will have decimal values?
It's been my experience that...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 4:56 pm
wendy elizabeth (3/16/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 4:49 pm
sunny.tjk (3/16/2016)
Grant Fritchey (3/15/2016)
CXPacket is only a concern if you also see other CPU waits. The one thing I will say, sight unseen, if your...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 4:45 pm
Solomon Rutzky (3/16/2016)
Jeff Moden (3/15/2016)
jasona.work (3/15/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 3:38 pm
mister.magoo (3/16/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 3:13 pm
lesemv (3/16/2016)
I'm embarrassed to say. I had the same 'Name' value for the data and log file.
Heh... thanks. I'm sure that none of us have ever done that...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 7:26 am
Eric M Russell (3/15/2016)
.. You wish to temporarily disable all foreign key constraints on the table since this is an archive database and you orphaned records are acceptable for this...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2016 at 11:28 pm
You could also change this...
DECLARE @TheDate DATE
... to this ...
DECLARE @TheDate DATETIME
... and continue to do the -1 trick.
Heh... now duck... here come the DATE/TIME police whose hair just burst...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2016 at 11:23 pm
lesemv (3/15/2016)
nevermind
What did you find to make you say "nevermind"?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2016 at 11:17 pm
Jeffery Williams (3/15/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2016 at 11:08 pm
dany.fortier (3/15/2016)
I will try DBCC checkdb if it found error and then i will ran DBCC updateusageWill let you know if this was the solution
The DBCC UPDATEUSAGE will do the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2016 at 11:05 pm
Viewing 15 posts - 18,091 through 18,105 (of 59,069 total)