i need the exact version of tds (Tabular Data Stream) used in SQL2008 .
I know that in SQL 2000 is TDSv7 but i don't know which is in SQL2008.
Thanks in advance.
View Complete Post
If someone has a suggestion of how to handle .NET dll assembly versions in a SQL Server 2008 database I would be very happy if you could explain how to do it.
First some background though so you'll understand the situation I'm in.
I've created a SQLCLR stored procedure in .NET with some code doning calculations in the database. Now I need to update the code according to some new business rules. Unfortunately we don't have a test environment where I can upload the code and test it
until it works. Therefore I would like make the changes necessary in the code and somehow change the version number of the dll and deploy that to the database while the old dll is still used in production.
I've heard of the workaround with strong/weak assembly names but I'm wondering if there's a real versioning method around yet.
And yes I know the "easiest" way would be to create a testenvironment and ahve the normal setup with test/production servers but I still would like to know if my original idea is possible in any way.
I am using SQL Server 2008 on Windows Server 2008 R2 and one of our servers running as a windows service (on Windows Server 2008 R2) contacts the SQL Server 2008 in a timely fashion to get some information. During one of these runs, we encountered the following
error logs in the service logs and thereby we took a hit in serving client requests. The jdbc jar that is used for database connectivity is of version 3.0 (sqljdbc.jar).
I can provide more details on this issue. Can someone please let us know why this can be occurring ? Just so you know, the set of errors repeats itself after sometime although on a different JDBC Connection (with different ConnectionID). We have a reconnection
algorithm running in case the JDBC Connection is lost for some reason (but I would be surprised if this issue relates to the re-connect algorithm).
INFO | jvm 1 | 2011/02/28 22:26:54 | Feb 28, 2011 10:26:54 PM com.microsoft.sqlserver.jdbc.TDSParser throwUnexpectedTokenException
INFO | jvm 1 | 2011/02/28 22:26:54 | SEVERE: TDSReader@4686d ( ConnectionID:25 TransactionID:0x0000000000000000): FetchBufferTokenHandler: Encountered unexpected TDS_RET_STAT (0x79)
INFO | jvm 1 | 2011/02/28 22:26:54 | Feb 28, 2011 10:26:54 PM com.microsoft.sqlserver.jdbc.TDSReade
how to create a mobile version of a website?Is there any server support needed?How does the browser detect whether the url is accessed via mobile device or a PC?
See how you can build Rich Internet Applications that take advantage of the OData protocol to creatively interact with Silverlight, PowerPivot, SQL Server, SharePoint, the Windows Azure platform, "Dallas" and more.
MSDN Magazine June 2010
We take a look at planned support for parallel programming for both managed and native code in the next version of Visual Studio.
Stephen Toub and Hazim Shafi
MSDN Magazine October 2008
In this new column, Brian Randell begins his long look at how to extend and enhance Visual Studio Team System.
Brian A. Randell
MSDN Magazine January 2007
Now that Windows Server 2003 is widely deployed, Keith Brown addresses questions from readers who are trying to use protocol transition to build secure gateways into their intranets.
This month: CWebVersion revisited using HTTP instead of FTP, and adding sounds to an MFC-based app.
MSDN Magazine May 2006
The next version of Microsoft SQL Server, code-named "Yukon," represents quite a few steps forward in the evolution of XML integration. Yukon supports native storage of XML data using the XML data type, which makes it possible to run native queries on XML data using the emerging industry standard XQuery language. Data integrity of the XML data type can be enforced through schema validation and XML-based check constraints, and special indexes can be defined that help speed up queries. In addition, Yukon has the built-in ability to expose its data through Web services. This article discusses these and other XML features of Yukon.
MSDN Magazine February 2004
MSDN Magazine October 2002
Windows CE .NET, the newest member of the .NET family, includes a number of improvements over previous versions of Windows CE. For example, there are quite a few new APIs and enhancements to security and connectivity, the user interface, the kernel, and the emulator. In addition, DirectX support has been added and C++ in Windows CE .NET now supports C++ exceptions, STL, and runtime type information. In this article the author takes a tour of Windows CE .NET, starting with the New Platform Wizard that allows you to code for your choice of devices. A sample application is included that locates features on portable devices so the reader knows what's available before writing code.
MSDN Magazine July 2002
In this article the author modifies an industry standard middle-tier application server benchmark called Nile. The goal was to get it to build and run correctly on the 64-bit edition of the Microsoft .NET Advanced Server running on computers with Intel Itanium processors and still build as a 32-bit version to run on Pentium class x86 processors. While modifying Nile, the author discovered some of the tips he presents here. As the article explains, when modifying code for 64-bit Windows, data types are the key to success. The article discusses which types to use and when, along with new data types and the importance of memory alignment.
MSDN Magazine November 2001
Handheld device users need to be able to synchronize with a main data store when it's convenient and, preferably, when the back-end database server isn't busy. SQL Server 2000 Windows CE Edition allows you to build a traveling data store that can be displayed and run on a variety of devices. SQL Server CE supports a subset of the full SQL Server package, and can be used as a standalone server or in tandem with SWL Server and IIS. The architecture of SQL Server CE, along with data manipulation, synchronization, and connectivity issues, are discussed in this article. Topics such as making your data public, choosing the right type of replication, and handling errors are also covered.
Paul Yao and David Durant
MSDN Magazine June 2001
MSDN Magazine June 2000