Viewing 15 posts - 556 through 570 (of 6,041 total)
With 30 feet of printed manuals, I'm guessing a moderate sized IT department had something like a technical reference librarian who could research stuff and keep it organized.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
April 16, 2019 at 3:00 pm
At least in my observable universe, most limitations that developers struggle with daily are at the logical level of SQL coding or at the physical modeling level, rather than being...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
April 16, 2019 at 1:35 pm
No doubt widespread traffic congestion would occur on highways and inner city streets globally if a technical glitch (or hack attack) disrupted smartphone GPS capability. Imagine it's 4:00pm mid week...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
April 11, 2019 at 2:33 pm
On those occasions the query produces a skewed execution plan, see if you can correlate the point in time with your index and statistics maintenance window. I know that maintenance...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
April 10, 2019 at 5:57 pm
It's unclear if you're asking a modeling question or a security question. For example, are you asking how grant DW users access only to financial data but not HR ?
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
April 10, 2019 at 5:50 pm
Maybe add the proxy account to one of the other server roles.
For example:
"dbcreator: Members of the dbcreator fixed server role can create, alter, drop, and restore any database."
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
April 10, 2019 at 5:47 pm
Rather than dropping the table, I'd reccomend denying select permission, and then wait at least 45 days before dropping it.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
April 10, 2019 at 4:37 pm
As a DBA and developer, I personally don't need an AI to help me write my code. However, I could really use an AI to monitor my servers, maybe even...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
April 10, 2019 at 1:32 pm
Do we really need AI driven application development?
Just like AI driven cars, it's an interesting concept, and I'm sure it's in our future, but at least here an now, there...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
April 10, 2019 at 1:28 pm
Yes, an index recommendation should be treated like a pharmaceutical add: always consult your DBA, and stop using the index when database bloating and slowness of data movement occurs.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
April 9, 2019 at 5:33 pm
null
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
April 9, 2019 at 5:33 pm
I don't know about AI (ie: speech to code) driven application development, but meta-data driven application development certainly is a thing. T-SQL is adept at generating code. The example below...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
April 9, 2019 at 1:51 pm
"..The longer I’m in this business, the more I think that many people with 5 years working with SQL Server usually don’t have 1 year of experience 5 times. I’m...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
April 8, 2019 at 1:42 pm
Storage Explorer, Data Explorer, Data Studio, Visual Studio, Visual Studio Express, Visual Studio Code, Data Tools:
Which of these are in the process of being deprecated?
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
April 5, 2019 at 1:17 pm
If a stored procedure isn't an option, then another safe guard would be to grant the mssql account used by the Contact page to have only insert permission on this...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
April 2, 2019 at 8:25 pm
Viewing 15 posts - 556 through 570 (of 6,041 total)