Viewing 15 posts - 18,076 through 18,090 (of 59,069 total)
Luis Cazares (3/16/2016)
Here's an untested...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 9:41 pm
Kazmerelda (3/16/2016)
Thank you am going to have a good read of that article, put it in Dev first (because I am not crazy) and test it fully.
Really appreciated, learn...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 9:39 pm
georgheretis (3/16/2016)
is it posiible to use 5 different steps for each db and inside each step to use ( SQL Server 2012)
BACKUP DATABASE [CONNECT] TO DISK = N'C:\Program Files\Microsoft SQL\...\MSSQL\Backup\CONNECT.bak'
I...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 9:35 pm
My "more elegant" method is to remove all but PUBLIC and CONNECT privs from the users/applications and force them to call stored procedures (which they've been given execute privs on)...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 9:22 pm
Sergiy (3/16/2016)
Jeff Moden (3/16/2016)
Lynn Pettis (8/6/2012)
An empty string is not null, it is a known value (empty).
I strongly agree. NULL is not NOTHING. NOTHING is a...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 9:10 pm
lkennedy76 (3/16/2016)
Thank everyone for all your replies. I am truly grateful for...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 9:04 pm
Jason-299789 (3/15/2016)
I appreciate that but you write a query in one instance to do specific job then someone comes up with a bright idea of expanding the grain, so you...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 9:01 pm
The drawing in the article is what I've seen a whole lot of automated testing do. People don't know how to write the testing any more than how to...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 8:50 pm
SQL!$@w$0ME (3/10/2016)
Did you already try the approach with column-level permissions? Have you considered the (IMO much better) alternative to have a separate audit table?
Not able to...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 8:44 pm
Eirikur Eiriksson (3/9/2016)
SQL!$@w$0ME (3/9/2016)
Users are still able to insert an invalid date/user in the Audit columns with default constraints. What is the best way to avoid this.Thanks!
Trigger
😎
Second that... trigger....
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 8:34 pm
ramana3327 (3/16/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 8:30 pm
smithhead (3/16/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 8:23 pm
Luis Cazares (3/16/2016)
The new data types don't allow these operations to allow better functionality.
That's a serious matter of opinion. I think they flubbed it in two ways...
1. They...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 8:05 pm
Luis Cazares (8/7/2012)
JasonRowland (8/7/2012)
Luis Cazares (8/7/2012)
http://msdn.microsoft.com/en-us/library/ms190309.aspx
So you won't have to wait for Celko to "do some digging". Here are the exact rules for implicit conversion...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 7:45 pm
Lynn Pettis (8/6/2012)
JasonRowland (8/6/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2016 at 7:40 pm
Viewing 15 posts - 18,076 through 18,090 (of 59,069 total)