network profile
|
Mar 14 |
answered | What alternatives exist when a table requires too many foreign keys? |
|
Mar 14 |
revised |
Index use and column type bunch of code tags |
|
Mar 14 |
suggested | suggested edit on Index use and column type |
|
Mar 14 |
comment |
Index use and column type To put it more bluntly: specifying a width for int at a database level is asinine and asking for trouble. |
|
Mar 7 |
comment |
How can I calculate time spent at work in a single column? UserID, SignIn, SignOut |
|
Mar 7 |
comment |
How can I calculate time spent at work in a single column? These answers do not correspond to the data in the question, correct? |
|
Feb 27 |
revised |
Pull Access schema into a SQL Server table typos, caps. etc |
|
Feb 27 |
comment |
managing a growing database in the long run (10 years from now) In a few years MySQL will have changed, your web host will have different pricing, HDD prices will have changed and CPUs will have changed. It is impossible to predict what will be best at that point. |
|
Feb 27 |
suggested | suggested edit on Pull Access schema into a SQL Server table |
|
Feb 27 |
comment |
How might a corrupt partition in TempDB result in DBCC CHECKDB reporting no issue? There's also this, but you'd think it would have been fixed by 2012: sqlservercentral.com/Forums/Topic770808-149-1.aspx |
|
Feb 27 |
comment |
How might a corrupt partition in TempDB result in DBCC CHECKDB reporting no issue? Are you sure the service was not restarted in the meantime? |
|
Feb 26 |
awarded | Editor |
|
Feb 26 |
revised |
SQL Server Analysis Studio naive Bayes attribute has too many states typos, caps. etc |
|
Feb 26 |
comment |
Why would I NOT use the SQL Server option “optimize for ad hoc workloads”? Again, fair enough. I am a developer as much as I am a DBA, and am in favor of change as long as it is positive. I work both sides of the fence here. The one hard and fast rule that has never let me down is that ANY change, no matter how minute, WILL break someone, somewhere. But as Paul pointed out, things should be in place for that not to be a hair-on-fire issue. I'll try to change my fear-mongering to infusing healthy dollops of skepticism and caution from here on out. |
|
Feb 26 |
comment |
Why would I NOT use the SQL Server option “optimize for ad hoc workloads”? @Aaron: of course. But your servers are not my servers. I'm probably a little cranky from just spending two days tracing down an issue with our application that ONLY happens when en-US SQL Server is installed on a Turkish version of Windows. If you have enough users, there is no such thing as a corner case; if you have enough users, you will turn every corner. I just have a strong reaction to anyone, anywhere suggesting there's no risk of breakage. And again, I apologize for that strong reaction. |
|
Feb 26 |
awarded | Commentator |
|
Feb 26 |
comment |
Why would I NOT use the SQL Server option “optimize for ad hoc workloads”? @Aaron: It was an example of a "this always helps" feature. It was about changes to parameter sniffing, not ad-hoc querying. There was no setting. The issue did not show on the test server because the environment was a little different. It only served to illustrate my original point: there is no such thing as a feature without risk. There is no such thing as sufficient testing to say that a feature will not break something. There is a reason new features are now introduced this way. |
|
Feb 26 |
comment |
Why would I NOT use the SQL Server option “optimize for ad hoc workloads”? @Paul: Don't get me started on that company's views on "production", "test", "staging", or "reality" for that matter :-) |
|
Feb 26 |
comment |
Why would I NOT use the SQL Server option “optimize for ad hoc workloads”? Fair enough. I should have phrased that better. Aaron, I apologize. In the end, I think we are agreeing in a very unusual way. |
|
Feb 26 |
comment |
Does disabling index exists in a table? Why can't you open up the table in SSMS and just look? |
