Why doesn't Microsoft Update catch SQLDMO.DLL ( version 2000.85.2004.0 ) ??

Question

Which has some outdated joins in it that become apparent if you invoke the SQL DMO (sqldmo.dll version 2000.85.2004.0) method

.Databases.Users.Add

Upgrading SQLDMO.DLL to 2000.85.2309.0 appears to fix...

Just wondering why Microsoft Update doesn't catch the need for upgrade of that SQLDMO.DLL/backward compatibility pack?

Answer 1

You can submit a feedback to MS at this link https://connect.microsoft.com/SQLServer/Feedback. This connect site will serve as a connecting point between you and Microsoft, and ultimately the large community for you and Microsoft to interact with. Your feedback enables Microsoft to offer the best software and deliver superior services, meanwhile you can learn more about and contribute to the exciting projects on Microsoft Connect.
Or provide a feature request at https://connect.microsoft.com/SQLServer

Answer 2

SQL DMO is deprecated. please use SMO - http://msdn.microsoft.com/en-us/library/ms162169(v=sql.105).aspx

If your goal is to add a user to database, you can achieve this using SMO

SMO Samples:

http://blogs.msdn.com/b/sqlagent/archive/2012/05/11/create-sql-agent-job-using-c-and-smo.aspx

Thanks

Sethu  Srinivasan [MSFT]

SQL Server

Answer 3

SQL DMO is deprecated. please use SMO - http://msdn.microsoft.com/en-us/library/ms162169(v=sql.105).aspx

Sethu  Srinivasan [MSFT]

SQL Server

Kind of blows the various and sundry guarantees that VB programs "will just work" in Win7/Win8 into teeny tiny fragments, doesn't it? Or is http://msdn.microsoft.com/nb-no/vbrun/ms788708%28en-us%29.aspx supposed to read "...but only for trivial code."

That is, the Microsoft statement "The Visual Basic team’s goal is that Visual Basic 6.0 applications that run on Windows XP will also run on Windows Vista, Windows Server 2008, Windows 7, and Windows 8. " is a great big lie?

Answer 4

Hello,

SQL Server 2000 is disappearing ( it is no more supported since 2008 ) but DMO was created to manage SQL server 2000.The 1st annoucement of the depreciation of DMO appeared with the release of SQL Server 2005 ( a long time ago... ).Why the SQL Server Team would maintain a product which is depreciated and no longer provided in the last SQL Server 2012 feature pack.

It seems that the last way to use DMO is to manage Access databases since Access 2010. I don't understand why the Office and VB Teams are always needing a product which will not be supported by the SQL Server Team. I see only one reason : VBscript is similar to VB ( if it is true, i am deceived by these teams ... ).

For VB 6.0, the problem is that the .Net Frameworks began to be stable in 2003 and Microsoft warned at this time to switch towards .Net Framework ( with the necessity to rewrite the applications ). 10 years later, i am always seeing people crying about the possible disappearance of VBA,VB 6.0 or VBScript : if they hope a longer support from Microsoft, i am fearing that they will have to change their habits. And from a long experience of developer  ( i have written my 1st  program in Basic in October of 1967 ), the people who are the most difficult ones to push them to change their coding habits are those programming in COBOL and Basic/VB as i am not sure they really want to face the challenge of migration from VB 6.0 thru VB 2010 or 2012. I have always used the language the most adapted to the situation. Learn something new is not a problem for me but ,the main problem with VB 6.0 is that everything will have to be recoded , nothing will be saved and it is not sure that the people who are able to understand VB 6.0 application are numerous.Bye-Bye VB 6.0, you was a good one and i will never forget it ( i have used VB 3.0 upto 6.0 with pleasure especially because C++ was not a great success as not evident to use). I am regreating it but it is time to use newer , easier  and surer languages...Don't forget that VB 6.0 was launched at the time of Windows 95 and 97  . How long time ago ?

Have a nice day

---

Mark Post as helpful if it provides any help.Otherwise,leave it as it is.