November 20, 2006 at 8:00 am
Hi,
mssql 2000/sp4 on win2003
I have a vendor asking me the following:
"Are we in SQL 2000 native mode? Or are we still using backward compatibility for SQL 7.0?"
I've never heard it called "native mode" ... re: db compatibility level. I've only heard the term "native mode" in copying data. What is this?
Many thanks. Jeff
November 20, 2006 at 8:12 am
I found refferences of native mode for BCP... but nothing for the server itself. I'm with you on this one. I think he's talking about compatibility of the database, or that he doesn't know what he is talking about .
November 20, 2006 at 8:41 am
on a slight tangent, in sql 2005 i know there is a SQL Native Client, which is the provider that replaces SQLOLEDB to connect to a SQL instance...maybe he's trying to sound important by inventing phrases you never heard of so he sounds like he has a clue.
Lowell
November 20, 2006 at 1:33 pm
As a comparison of mixed mode, a native mode should be SQL Server authentication.
November 21, 2006 at 3:11 am
Though, authentication modes aren't different between SS2k an 7 (ie has nothing to do with compatibility) so my guess is also that it's the compat level that is referred to...
/Kenneth
November 21, 2006 at 5:39 am
I'd suppose they are just trying to impress by finding out a new slang-word.
I guess what they are trying to find out is if you are using a lower than the current sqlserverversion db-level setting. (db compatibility level)
e.g. you have a sqlserver 2000, so all db should be using 80
chec BOL :
The compatibility level is specified for each database using the sp_dbcmptlevel system stored procedure. The database compatibility level can be set to 60 (version 6.0 compatibility), 65 (version 6.5 compatibility), 70 (version 7.0 compatibility), and the default 80 (SQL Server 2000 compatibility). The effects of the compatibility level settings are generally limited to the behaviors of a small number of Transact-SQL statements that also existed in earlier versions of SQL Server. Even when the database compatibility level is set to 60 or 65, applications gain almost all of the benefits of the new performance enhancements of SQL Server 2000. Applications still benefit from features such as the improved query processor. For more information, see the discussion of specific behaviors controlled by the different settings in sp_dbcmptlevel.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
November 21, 2006 at 7:58 am
I've seen the Sql Native Client referred to when using the Business Intelligence Developement Studio's Import SSIS Import/Export Wizard. Here what the help file says:
SQL Native Client is a data access technology that is new to Microsoft SQL Server 2005, and it is a stand-alone data access application programming interface (API) that is used for both OLE DB and ODBC. It combines the SQL OLE DB provider and the SQL ODBC driver into one native dynamic-link library (DLL) while also providing new functionality above and beyond that supplied by the Microsoft Data Access Components (MDAC). SQL Native Client can be used to create new applications or enhance existing applications that need to take advantage of new SQL Server 2005 features such as multiple active result sets (MARS), user-defined data types (UDT), query notifications, snapshot isolation, and XML data type support...
I assume this is the mode they're referring to, there more in the online help.
November 21, 2006 at 12:13 pm
Native mode refers tot he way that SQL Server interacts with external databases. SQL Server Native mode means that it is using a language that only SQL Server understands. For example, if SQL Server tried to talk to an Oracle database using SQL Server Native Mode, it would be like when you answer the phone and a fax machine is on the other end. You'd have no idea what it was trying to tell you.
SQL Native mode is faster because it doesn't have to convert it to a universally understood language. Sort of like it is easier and fater to talk to someone that shares the same native language as you than it is to talk to someone who's secondary language is the same as your secondary language.
I do believe that the vendor was referring to compatibility mode. I do not recall if SQL 7 supported the SQL Server Native mode or not.
Viewing 8 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy