Is there a function / SP which gives ONLY the current compatibility setting of a DB.
I know sp_helpdb can do that; but sp_helpdb returns lot more information. I need this to create a script.
------------------------
I think, therefore I am - Rene Descartes
Is it possible to backup databases from a 7.0 box and restore them to as MSSQL 2k box? My question really is this: Does it matter what type of MSSQL server your database resides on or can a dump be created of a database, restored to a different version MSSQL server, and used interchangeably?
View 1 Replies View RelatedCan CE open .mdf files??
View 1 Replies View RelatedHi all,I am under the impression that one can not Log Ship from enterprise edition to standard edition. Anyone have any documentation they can point me to?TIA,SQLPoet
View 3 Replies View RelatedI get the impression that osql (or somewhere in the sql processing) precompiles the entire script before it executes anything. In particular, this is a problem because it means you can't use IF statements to bracket new features in a script designed to be run on both old and new versions of SQL Server. I'm trying to handle an issue whereby I need to use "CREATE LOGIN" on SQL Server 2005 because I need to set CHECK_POLICY = OFF, and you can't do that with sp_addlogin. However, on SQL Server 2000, while I can't use CREATE LOGIN, I don't need to because the default password policy is such that the password being used does not fail without it (as it does in SQL Server 2005, and is why we need to set CHECK_POLICY), so I can simply use sp_addlogin to create the user w/o a CHEC_POLICY setting.
It appears however, due to the way that SQL is processed, it is impossible to create an SQL script of this nature that will work under both SQL Server 2000 and SQL Server 2005. I added code to check the Product Version, and can successfully bracket the code necessary with IF statements, but even though the IF statement would cause the CREATE LOGIN code to not be executed on SQL Server 2000, it errors anyway apparently because it is preparsing the script and of course, SQL Server 2000 doesn't have CREATE LOGIN. Consequently, checking Product Version is useless in this case. It looks like we'll have to do the version check outside of SQL and invoke script A for SQL Server 2000 and script B for SQL Server 2005.
Unless that is, I misunderstand the error I get from SQL Server 2000, or if there's some other way to compatibly do such a conditional. Here's an example script that runs fine under SQL Server 2005:
---------------
declare @ProductVersion as integer
set @ProductVersion = cast(left(cast(serverproperty('productversion')
as varchar(30)),1) as integer)
print 'Product Version = ' + cast(@ProductVersion as char)
IF @ProductVersion < 9 exec sp_addlogin 'testuser', 'fubar', 'master'
IF @ProductVersion > 8
BEGIN
CREATE LOGIN testuser WITH PASSWORD = 'fubar',
CHECK_POLICY = OFF, DEFAULT_DATABASE = [master]
END
----------------
On SQL Server 2000, @ProductVersion gets set to 8, but I get the following error:
Msg 170, Level 15, State 1, Server TESTSVR, Line 10
Line 10: Incorrect syntax near 'LOGIN'.
Any thoughts?
--
Sync
--
Sync
Hi Gurus,
I would like to know if I put the Compatibility Level in a SQL Server 2005 installation to 70 I can make afirmation that I have a full SQL Server 7.0. If the answer is "Yes" where I can find a documentation or a FAQ that explained this topic.
Has anyone changed compatibility level from 80 to 90? Did you have any problems?
View 8 Replies View RelatedI restored the database from SQL server 2000 to 2005.The database was restored with 80 compatibility.Can i change it to 90 and what are the effects? Coz my applications are pulling data from SQL server 2000. Does 80 work for database mirroring?
View 5 Replies View RelatedHi there
We found interesting issue which is basically the app is being tested ok on SQL2005 by software vendor. Then we tested in our environment and we found it's not truly true. There are some compatibility issue on SQL syntax. Anyway ... the plan set the compatibility level back to 80 instead 90. Cause this thing for sure is working.
Now my question is do you know any other impacts that you know of if we are doing this setting (running SQLServer 2005 but the database set as 80)? I know that some inbuilt reporting only run 90 level but I can get around this. Performance or something? Is there any thing that I should to know?
Thanks
Hi,
What are the limitations of using the automated conversion tool and how to deal with compatability issues?
Thanks
Does SQL Server Compact Edition fully support ADO.NET?
Will SQL Server Compact Edition fully support the ADO.NET Entity Framework?
Will SQL Server Compact Edition fully support LINQ?
To your knowledge, is there any performance hit with SQL 2005 when you set a database to a lower compatibility mode. IE from 9.0 to 7.0
View 1 Replies View RelatedHi there,
Correct me please if I'm wrong but one should not get any issues while restoring a database backup from a sql 2005 development edition to an enteprise edition or even from a sql express edition to whatever else?
I was under the impression that a sql 2005 database, no matter what edition, would work on all the other 2005 server editions/versions and hence, the backups from these databases should also work on the others.
Regards
Mike
I was hoping someone could help me or put me on the right path to re-writing the join portion of this sql query in ANSI form for compatibility level 90. Im just not sure how to handle the three join statements and if they should go at the top in the FROM statement (dont know if that would mess up the rows produced). The query exists inside a stored proc.
SELECT
S.TYPE,
S.LOCATION_TYPE,
S.LOCATION_ID,
S.PLANNED_ARRIVAL,
S.PROJECTED_ARRIVAL,
S.ACTUAL_ARRIVAL,
S.PLANNED_DEPARTURE,
S.PROJECTED_DEPARTURE,
S.ACTUAL_DEPARTURE
FROM TAB1 S, TAB2 RL, TAB LS
WHERE
S.LOAD_ID = @V_CURRENTLOADID AND
(RL.REGION_ID = @REGION_ID AND
RL.ROUTE_DATE = @ROUTE_DATE AND
RL.ROUTE_ID = @ROUTE_ID) AND
(S.REGION_ID = RL.REGION_ID AND
S.ROUTE_DATE = RL.ROUTE_DATE AND
S.ROUTE_ID = RL.ROUTE_ID) AND
(S.LOCATION_ID =* LS.LOAD_LOCATION_ID AND
S.LOAD_ID =* LS.LOAD_ID AND
S.LOAD_STOP_ID =* LS.LOAD_STOP_ID)
ORDER BY RL.SEQ_NUM, S.ACTUAL_SEQUENCE_NUM;
Any help would be greatly appreciated
just a question....
my web project is using SQL Express2005 and ASP.NET and C#.
my
web hosting company only have MSsql2000. would there be any conflict
with regards to my database? im sorry if i sound dumb. im a newbie to
this.
thanks a lot!
I have moved a database from SQL 2000 to SQL 2005 Express. I have modified the structure in 2005 Management Studio Express.
Now I cannot attach to the modified dataabse in SQL 2000 Enterprise Manager. I get "Error 602: Could not find row in sysindexes for database ID.... Run DBCC CHECKTABLE on sysindexes".
This occurs despite the fact that I have kept the database at Compatibiluty Level SQL Server 2000, as reported in 2005 Management Studio Express.
Are 2005 and 2000 databases not compatible?
Many thanks.
I find that the "Create Table" script generated by SQL Server 2005 is in format:
CREATE TABLE [dbo].[City](
[CityID] [int] IDENTITY(1,1) NOT NULL,
[Name] [nvarchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
CONSTRAINT [PK_City] PRIMARY KEY CLUSTERED
(
[CityID] ASC
)WITH (IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
Can this appliable in SQL Server 2000 or MSDE? If not, how should I change it to make it work in both SQL 2000 and 2005?
Thanks
we have applications currently talking to a sql 2000 DB via ado.net 1.1. will we have any problems if we upgrade to sql 2005, will the app have to be modified.
View 3 Replies View RelatedHaving moved over to SQL 2k5, from SQL 7.0 we have now realised that the database's need to be set to comp level 9.0 before they are found in the maintence plan wizard, we currently still access the database using an Access 2000 front end, by changing the comp level will this cause us issues writing data, I'm sure it won't but want to make sure, I'm sure that the comp level just sets what options are available to use.
Thanks
I find that the "Create Table" script generated by SQL Server 2005 is in format:
CREATE TABLE [dbo].[City](
[CityID] [int] IDENTITY(1,1) NOT NULL,
[Name] [nvarchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
CONSTRAINT [PK_City] PRIMARY KEY CLUSTERED
(
[CityID] ASC
)WITH (IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
Can this appliable in SQL Server 2000 or MSDE? If not, how should I change it to make it work in both SQL 2000 and 2005?
Thanks
Hi,
i'm using a query to insert a value in a field named 'From' in a table.
i used like
Insert in to myTable ([from]) values('01/01/2005')
The query was working in sql 2000. but in sql 2005, i'm getting a error like
'Syntax error near 'From'.
what could be the reason for this???
I need to know if I will run into problems with sql express on a sql 2000 server. I get the impression that my isp is using 200 server just by lookng at the connection string. Is there a addin I could use if needed I seen a post mentioning the publishing wizard cpt but not much after is it released yet. and then there is the web data admnistrator for msde will that work with sql express.One other question can I reinstall sql and change the authentication process from windows to user name and password.
DKB
We upgraded from SQL 6.5 to 2000 (.384) and just look at this T-SQL and maybe somebody can tell me what's wrong.
sp_dbcmptlevel appetserv1,80
update articleentrepot set usagermodification = 'MANON' where idarticle = 1
Here is the result:
Cannot use the column prefix 'E'. This must match the object in the UPDATE clause 'ArticleEntrepot'.
When I put the compatibility level to 65, it's works. But my problem is that I need to have the compatibility level to 80 because of the DataMirror replication software and if I do that, my house application doesn't work. I really don't know what to do, I'm in a deadlock. Can you help me!
Manon Tremblay
Does anyone know if the enhanced data types (character length up to 8,000 bytes for some types) and the increase in the number of tables used in joins are available when using the 65 backward compatibility mode?
Many thanks in advance...
We have some users who are nervous about our upgrading to SQL Server 7.0 even though we will use 6.5 compatibility mode initially while we work through 7.0 upgrade issues in the applications.
Has anyone had bad experiences with the 6.5 compatibility mode feature? Just how good is it?
Cheers
Matt
Hi!
After upgrading SQL Server from 6.5 to 7.0 my production database compatibility level is "65".
I checked that by executing sp_dbcmptlevel <database_name>.
I can change it to "70" but my question is how it's going to affect the application and do I have to change it?
Thank you
Lena
I have a problem where I have a software application that
needed to be updated to a newer version. In order for the
new version to work I needed to upgrade my SQL Server 7
database to SQL Server 2000. The upgrade went fine for
SQL Server 2000 and also with the application. The only
problem now is that the compatibility level for the
databases stays at 70. Even when I change the
compatibility level to 80 it will automatically go back to
80. What is wrong? Please help.
I installed SQL 7.0 on a test server a few days ago. I want to test an application that currently runs on SQL 6.5. I have run a test database through the upgrade wizard without errors. Is there any way to see the compatibility level that the db is running on. I know I can use the sp_dbcmptlevel procedure to make it run at the 6.5 level. I want to see if it is running at that level currently, or if it is at the 7.0 level.
Any help would be appreciated.
I have table with about 2 million rows. Everyday about 18000 rows are inserted. The table contain events for site security system so archiving is neccessary. I would appreicate any help or ideas. Thanks in advance.
View 2 Replies View RelatedHi,
I am trying to install SQL server 2000 on my laptop which has vista as OS. I am not able to install it , somehow it fails. Can anyone please suggest me how can i accomplish this.
Thanks
Divya
I have a Sql Server 2005 instance that was upgraded from 2000. The compatibility mode of master is still set to 80. Can I change this to 90?
View 2 Replies View RelatedI installed SQL 2K5 (not upgrade from 2K) and just found that Master DB comp. level is 80. All other system DBs are 90.
1. How can I change master's to 90? Does the following work?
EXEC SP_DBCMPTLEVEL Master, 90;
go
2. Changing this, is there any possibility to impact my production?
Canada DBA
Problem: I want to set compatibility_level only when it is greater than 110.
Solution: Select the compatibility level and if it is greater than 110, I alter database set compatibility level=110
ISSUE Irrespective of IF Exist statement the alter database statement is executed all the time.
Here is the sql statement
IF EXISTS (
SELECT * FROM sys.databases where compatibility_level >110 AND name='mydatabase'
)
BEGIN
ALTER DATABASE mydatabase SET COMPATIBILITY_LEVEL = 110
END
What is that I am missing here ?