Viewing 15 posts - 8,926 through 8,940 (of 59,091 total)
I might be missing something but that looks an awful lot like JSON. Is it?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2019 at 5:27 pm
Thanks for your input. I've done some thinking about this and might be able to work something out querying the sys.syslogins. Since a trigger will catch every login it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2019 at 11:54 am
Jeff, I agree that on busy systems these 5 files (20 MB each) of default trace will be overwritten soon, but look at at from the following angle:
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2019 at 11:49 am
What I'm really getting at is that a lot of Developers that I've worked with at other companies think that they don't need to test their own code as...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2019 at 11:46 am
Not to mention that the default trace file has a pretty small row limit before it "rolls over", it only stores (IIRC) 6 total files, and a busy system can...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2019 at 12:44 am
Can you think of anything that could cause the problem?
Call the vendor that provided the "application". If the "application" was written by you good folks, you can't "call the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2019 at 10:13 pm
Agreed. Be nice if MS added the option to the CREATE TABLE statement, so that SQL would "know" that the variable length bytes are not needed at all for...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2019 at 8:19 pm
Heh... but ONLY if the reason for the change wasn't in the form of a requirements change. Otherwise, the existing unit test is totally useless and actually may cause...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2019 at 8:15 pm
Then again, with properly normalized tables, I can't imagine ever needing more than 10 (if that many?) max-length columns in one row.
I cannot give that comment enough good points! ...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2019 at 5:10 pm
I created a table with 433 columns: that's where I got the number from. I was hoping that 500 might be possible but the variable-length byte overhead still being required...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2019 at 4:08 pm
Ah... I think I found it... it looks like it's at the following link now...
http://improve.dk/what-is-the-size-of-the-lob-pointer-for-max-types-like-varchar-varbinary-etc/
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2019 at 3:27 pm
No prob! I took the liberty of elaborating a bit more on my blog since you're not the only one unable to find the behavior cleanly documented on the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2019 at 3:23 pm
p.s. We both may be right. According to Paul Randal, "It Depends" and can be 16 or 24 depending on the datatype. Please see the following.
https://www.sqlservercentral.com/forums/topic/lob-pointers-am-i-stupid/#post-1354312
To add to that,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2019 at 3:17 pm
Forced-off-row types require only a 16-byte pointer. The 2-byte variable-length overhead per pointer, though, causes even fewer than 500 columns to be possible [I thought SQL would be able...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2019 at 2:44 pm
Here is my code:
CREATE SCHEMA Costpoint AUTHORIZATION iDrago;
GO
CREATE TABLE Costpoint.ProjectCodes
(
isActivetinyintNOT NULL,
projectCodevarchar(28)NOT NULL,
projectNamevarchar(25)NULL,
leveltinyintNOT NULL,
projectMgrIDchar(6)NULL,
projectMgrNamevarchar(22)NULL,
projectClassvarchar(14)NULL,
projectTypevarchar(11)NOT NULL,
isBillabletinyintNOT NULL,
allowChargingtinyintNOT NULL,
exportProjectClassvarchar(23)NOT NULL,
accountGroupchar(3)NOT NULL,
owningOrgchar(10)NOT NULL,
customerIDvarchar(12)NOT NULL,
customerNamevarchar(20)NOT NULL,
startDatedateNULL,
endDatedateNULL,
primeContractNochar(20)NULL,
taskOrderNochar (20)NULL,
CONSTRAINT CK_isActiveCHECK (isActive = 0...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2019 at 1:07 pm
Viewing 15 posts - 8,926 through 8,940 (of 59,091 total)