My team keeps emphasizing the importance of community participation and value all the feedback posted in the groups, forums and all possible channels to communicate with you all, the customers; and loop the feedback provided to improve the quality of product. I personally felt the importance after being part of the community during our SP1 release cycle, it really helped to address most of the customer impact defects in our Service Pack1; however, not all could be addressed in the first service pack and we would like to give importance to them and start gathering the impact of those defects. We will evaluate and try to address most of the commonly reported customer bugs in our next Service pack, SP2.
This can be done effectively by your active participation in providing feedback. Though there are several ways to do it, the best way to track and evaluate the impact on unaddressed issues across customers, is through reporting them through MSDN product feedback center which is incorporated in SQL Server Management Studio. You can access MSDN Product Feedback Center from Management Studio by selecting “Send Feedback” menu item under “Community” Menu or by going directly to the link
http://lab.msdn.microsoft.com/productfeedback/
By using this channel, you could log bugs directly or browse over the existing bugs that correspond to the issue you are running into and vote the importance of the fix for that bug. Our team constantly watches the incoming bugs and goes over the importance of the bug to be addressed based on number of voters and the rating of how important the fix is needed.
We are starting to plan and work on our next service pack and your input is the key factor for success of SP2!
Thanks,
Gops Dwarak, SQL Server Tools Team, MSFT
SP2 - Need Your Feedback!
AEC-JD
Hello Clifton,
I have confirmed that this is indeed a bug in our SQL2005 code base, and as far as I can tell, the bug has been there since 2002 so I am a bit confused by your comment that SQL2005 DMO has been working fine for you for two years. It would be great if you can clarify whether you really meant SQL2000 instead of SQL2005 in that comment. At the moment, we are going through a debate internally as to which delivery vehicle (QFE or SP2) we should use for the fix and I will post again to inform you of our decision. If you want to track the progress of this issue more closely, I would encourage you to log it @ https://login.live.com/ppsecure/secure.srf lc=1033&id=64416&ru=https://connect.microsoft.com/default.aspx&tw=3600&fs=1&kv=4&ct=1150303879&ems=1&seclog=10&ver=2.1.6000.1&rn=CYWDyHyE&tpf=504beca26541936cfbb9d9e716bf9902
Or, you can let me if you want me to log an internal bug on your behalf.
Thank you for reporting the issue and sorry for the inconvenience.
-Raymond
cramer-creek
What are the target release date(s) for MS SQL 2005 Service Pack 2
Mkid
Hey
The feedback site is a bit confusing.
I can't seem to find the "Submit Feedback" link.
Any ideas
Thanks
Timothy R James
Hi Clifton,
The Connect site is rather new to me too so I needed to fumble a bit to navigate to the feedback form. The following is roughly what I did after the registration page:
1) Click on the "Available Connections" link on the left pane
2) Click on the "SQL Server" link
3) Click on the "Feedback" link on the left pane
4) Click on the "Submit Feedback" link
5) The next page will force you to search the existing bug database, so just type in a few keywords and hit the Search button
6) Since there will probably nott be existing issue corresponding to yours, you can hit the "Submit Feedback" button
7) Now you have the of using either the Bug form or the Suggestion form
I know this is a bit of a hassle, but your QFE request will more likely be accepted if you go through the Microsoft product support organization (call them up) rather than logging it at the Connect site which pipes directly to the product development folks like me.
Hope that helps,
-Raymond
kclarico
Using DMO to look up the distribution publisher, the publishing db and the publication name appear to be working. This is accomplished with the TransPublication dmo object.
We receive some information from the TransSubscription object, but not the DistributionJobID.
We get the correct subscriber count, article count, publiser name, subscriber server and subscriber databasename.
The DistributionJobID is all zeros, (00000000000000000000000000000000).
SQL2005 9.00.2047 with or without the backward compatible objects installed.
The objects and code has been working with SQL2000 for two years.
It is failing during our certification of SQL2005 for our distributed application.
We cannot proceed with certification and recommending SQL2005 to our 300+ customers without resolution.
Robert Simpson
Thank you for the update. My notes are incorrect in one place. We are currently on SQL 2000 in production distribution of our product. The code has been working on SQL2000 for two years.
I would like to have a hotfix /qfe if possible.
jhoop2002
What is the target SQL 2005 SP2 release dates
zdeer1
Hello Clifton,
We have decided to deliver the fix in SQL2005 SP2, if you need the fix sooner, I would encourage you to go through the product support channels to get a QFE request in.
-Raymond
ukhobson
I am logged in to connect. I get to the feedback page, https://connect.microsoft.com/SQLServer/Feedback, but do not see a method of submitting feedback. All I have are search options. Do I need an invitation ID in order to connect/participate in the SQL server program
????? ????????