|
|
|
Mr or Mrs. 500
      
Group: Administrators
Last Login: Wednesday, May 08, 2013 10:31 AM
Points: 511,
Visits: 945
|
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Wednesday, March 27, 2013 3:22 PM
Points: 1,276,
Visits: 1,112
|
|
Hi Tony,
Funny you mentioned extended properties :) I'm working on a little set of apps right now that will greatly simplify working with them. Of course the Intellisense won't be modified to incorporate them, but adding, deleting, updating and retrieving them on objects will be greatly simplified. To me it only makes sense to let the server manage your metadata, but as you mentioned it can be painful to use the SPs.
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Friday, November 16, 2012 9:00 AM
Points: 3,
Visits: 42
|
|
| Another useful feature would be change in versioning so it accepts the same plugins that Visual Studio uses. For now versioning doesn't work for most people around.
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Sunday, May 19, 2013 4:00 AM
Points: 533,
Visits: 2,285
|
|
I realize that this is not a major issue, but I always find it irritating that the system stored procedures haven't been updated with the new data types. ---for years and years and years.....
Try this...
DECLARE @Output VARCHAR(8000) EXECUTE xp_sprintf @output out, 'Go hang yourself, you old M.D,! You shall not sneer at me. Pick up your hat and stethoscope, Go wash your mouth with laundry soap; I contemplate a joy exquisite In not paying you for your visit. I did not call you to be told My malady is a common cold.
By pounding brow and swollen lip; By fever''s hot and scaly grip; By those two red redundant eyes That weep like woeful %s skies; By racking snuffle, snort, and sniff; By handkerchief after handkerchief; This cold you wave away as naught Is the damnedest cold man ever caught!', 'April' SELECT LEN(@Output)
--253
Yup, the documentation proudly says that it takes a string. ...Er... only 256 characters. Look here, this isn't even lined up for deprecation so how long would it take to fix to make it use MAX??
Best wishes,
Phil Factor Simple Talk
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Wednesday, January 23, 2013 9:10 PM
Points: 105,
Visits: 481
|
|
| While table partitioning has been available since 2005, it's almost easier to continue to manually manage it with regular tables, since tables have to be swapped in and out, and partition functions changed with a lot of verbose code - i.e. equivalent to the same code you would change when you added partitioning tables into a view and changed the trigger which makes the view updatable.
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Wednesday, January 23, 2013 9:10 PM
Points: 105,
Visits: 481
|
|
| If they were to fix extended properties, they should fix it so that they are not lost when altering a multi-step table value function whenever I remove schemabinding and re-add schemabinding.
|
|
|
|
|
SSC-Dedicated
           
Group: Administrators
Last Login: Today @ 3:30 PM
Points: 31,436,
Visits: 13,751
|
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Friday, March 29, 2013 11:17 AM
Points: 3,432,
Visits: 14,332
|
|
In most software development projects there is a bug I call the sycophant who tells the boss he or she can do the job and most bosses usually find out after the person with the implementation detail have left without leaving the implementation detail. I can tell you the people who created those nice features have moved on to other companies Microsoft is left without implementation detail, Microsoft is also in a better position than other companies because their employees must leave blogs as is. If the employee did not blog about it the feature is usually lost forever even with a blog I think Microsoft sometimes hire 5 to 10 new people who still cannot complete the nice feature. I know one such work in .NET I help their customers only as needed because the person who created it left with the implementation detail. I was surprised to find the person’s blog number one when I searched Google for it using the feature as key word because I did not remember his name , who knows if he now works for Google.


Kind regards, Gift Peddie
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 4:51 PM
Points: 32,923,
Visits: 26,811
|
|
Gift Peddie's good post brings up a real sore spot with me... why does everyone think that the Agile Manifesto says "No Documentation" whatsoever? Why does everyone think that if you document code (especially embedded documentation) that you're a sissy of some sort? Why does everyone think that having a simple implementation plan in black and white is somehow against the ability to move quickly?
IT managers of the world... wake up. Insist on proper embedded documentation so it never gets separated from the code and then give people time to do it right. Then insist on code reviews and make them part of everyone's job using pay reviews as enforcement. If you lose a couple of programmers because of it, good... they needed to be replaced anyway.
And remember... "If you want it real bad, you'll probably get it that way."
--Jeff Moden "RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."
For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Friday, March 29, 2013 11:17 AM
Points: 3,432,
Visits: 14,332
|
|
IT managers of the world... wake up. Insist on proper embedded documentation so it never gets separated from the code and then give people time to do it right. Then insist on code reviews and make them part of everyone's job using pay reviews as enforcement. If you lose a couple of programmers because of it, good... they needed to be replaced anyway.
And remember... "If you want it real bad, you'll probably get it that way."
This is more about intellectual property transfer than documentation because I can give you ten pages of documentation without the three lines needed to implement what I am working on. It takes very little to keep a developer happy but companies sometimes have paid team members doing nothing, writing useless compiled code, working on manager's pet project reinventing the wheel. I find most large projects are useless without a few people in the team and if these people are marginalized so they move on the project is dead.
Kind regards, Gift Peddie
|
|
|
|