Hello, I'm developing a site with variations of language in sp2010 and in the documentation saids that the object VariationsLabelEcbMenu is deprecated .
What is to be used?
View Complete Post
I read an article about deprecated features and sysindexes is marked as not supported under list "Features Not Supported in a Future Version of SQL Server" (system tables).
However I am surprised to see that sp_udpatestats procedure still uses sysindexes table for picking up rowmodctr column for verifying the indexes that got modified after last stats calculation, and this procedure is not using the new DMV's introduced in
SQL 2005 like physical index stats, stats calculated date, last_user_modified_date etc.
Also sp_updatestats is not marked for deprecation. When applications depending on SQL server are modifying the code/re-writting to move to the new catalog views/DMV's, I would expect SQL Server system stored procedures also get modified accordingly.
It's just a thought and never know if MS can consider this request...
Hi, I am pretty sure the code below compiled on ms sql 2000 and it doesn't compile on ms sql 2005. I know the code below won't compile (create a proc if code below is in the proc) in ms sql 2005. Is there any replacement short of exec (@sql1).
I hate execs.
WHEN 'T' THEN f.oid
WHEN 'F' THEN fromoid
WHEN 'L' THEN c.acct
WHEN 'I' THEN e.item
I have a web application that has been using the System.Data.OracleClient.dll for the past 3 years. Recently we've been having some performance issues on the database server and it appears that this app is now causing problems when connecting to our Oracle database.
I've found an updated client at the Oracle website: http://www.oracle.com/technetwork/topics/dotnet/index-085163.html
My question is: Is it necessary for me to update to this new client?
We are running Oracle 11g on 64-bit servers in a cluster.
The app is running on a Windows Server 2008 R2 64-bit machine using ASP.NET 4.0. The app was built using Visual Studio 2005 Team Suite on a 32-bit machine. It was re-compiled on a 64-bit machine and imported into Visual Studio 2010 Professional in order to switch the target framework to .NET 4.0. Then it was deployed to the server. This basically updated the Web.config file for us, the rest of the site remains the same as before.
All suggestions and thoughts are welcome.
According to books online, Logical Record Relationships are deprecated (http://msdn.microsoft.com/en-us/library/ms146865(v=SQL.100).aspx).
Is there anything going to replace this feature?