March 22, 2010 at 6:09 pm
Yes I’m aware of the risk… but since SQL 2000 to 2005 only work it out for the best. Must be a way to do the same in SQL 2008, and that is my only question here in this forum.
When you said that was by design in 2008, MS said the same in SQL 2005... I believe.
Thanks again.
March 22, 2010 at 6:11 pm
amandix (3/22/2010)
Yes I’m aware of the risk… but since SQL 2000 to 2005 only work it out for the best. Must be a way to do the same in SQL 2008, and that is my only question here in this blog.When you said that was by design in 2008, MS said the same in SQL 2005... I believe.
Thanks again.
I don't know that MS actually ever stated that was the case in 2005. I had a MS employee show me directly how to do that in 2005.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 22, 2010 at 6:13 pm
If the changes have truly made it perform that much better, I recommend you make those suggestions directly to Microsoft on their Connect site. If they deem the changes appropriate, they may well incorporate the changes in a future release.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 22, 2010 at 6:30 pm
I did that once for improving SQL Queue Reader Agent on sp_replsqlqgetrows, and they did incorporate changes on SP3 for SQL 2000, but do really know how much time it took… long enough to loose replication projects, and so on. That’s why workarounds can save us time and money.
Are you saying there no chance for me? The end?!
Please if you have any documentation about this matter let me know.
March 23, 2010 at 1:57 am
Are you saying the only way you can successfully complete a replication project is to hack your client's SQL Servers? Are they aware that by doing so you'd have lost them support from Microsoft?
What on earth are you doing in replication that requires you to hack system objects?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 23, 2010 at 10:37 pm
amandix (3/22/2010)
OK, now i have to explain why...I usually install on SQL Server systems Transactional Replication on databases. This is not for hack SQL Server!
Sample: there is a system stored stored procedure in mssqlsystemresource db that is called when gererating code for triggers and sps for the publisher side, named [sys].[sp_execresultset].
Altering this sp, i can modify the standard code that is generated by default.
Could you help finding a way to do this in SQL Server 2008?
I am curious why you are claiming that this is to "modify the standard code that is generated" for Replication SPs and Triggers when this capability has been built in as a supported feature of MS Replication since SQL Server 2000?!?
It seems very likely that this is just a cover for hacking SQL Server, and I cannot imagine any reason why we should help you with this.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply