Sql server 2005 in server 2012 domain

Hello,
I am running sql server 2005, in a 2003 domain. I plan to possibly upgrade domain/servers to 2012, but am thinking it may create issues with sql 2005?
1. Can sql server version 2005 (32-bit) run ok in a 2012 server domain?
2. If not, will it run ok, if I leave 2003 servers (running mixed mode) until sql 2005 is upgraded?
Thank you
Robert

1. Can sql server version 2005 (32-bit) run ok in a 2012 server domain?
No & May be.
No if you are trying to have multiple version of SQL Server on server ,as per this
article
SQL Server 2005 (the release version and service packs) and earlier versions of SQL Server are not supported on Windows
Server 2012 R2, Windows Server 2012, Windows 8.1, or Windows 8. You will receive a warning in the Action Center if Windows 8.1 or Windows 8 detects an instance of SQL Server 2005.
May be, if you just want to have single instance of SQL Server 2005 on server 2012. Check this:
How to install SQL Server 2005 on Windows 8
2. If not, will it run ok, if I leave 2003 servers (running mixed mode) until sql 2005 is upgraded?
To be able to answer this question in a better way, may I know your SQL Server 2005 version and to which version you want to upgrade? Check for the
supported version and editor upgrade
before going for upgrade along with there hardware and software requirements.
Glad to help! Please remember to accept the answer if you found it helpful. It will be useful for future readers having same issue.

Similar Messages

SQL Server 2005 Analysis Services across domains

Hi,
With SQL Server 2000, the Enterprise Edition was required to access
Analysis Services across domains.
Is this also the case in SQL Server 2005, that the Enterprise Edition
is needed?
Thanks, S

Silver,
Do you still need help with this?
Thank you!
Ed Price, Power BI & SQL Server Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Are there any known issues with a 2003 server authenticating to a 2012 domain controller

I am trying to get off of these 2003 domain controllers. But I still have a couple of 2003 servers that will be decommissioned by early next year. If I change my environment and get rid of the two 2003 dc's, and promote two 2012 dc's. Will I have any issues
with the 2003 servers authenticating? I have a very small maintenance window, and do not have time to test on my own. I was hoping someone else has tried this before, and knows the results.

Hi,
I am not aware of any issues with 2012 as domain controller role. There was an issue with 2012 R2 as domain controller role related to the AES encryption for computer password, but MS issued a hotfix and a rollup (covers many other issues along).
https://support.microsoft.com/kb/910205?wa=wsignin1.0
Once you upgrade your schema to support 2012 domain controllers you can start promoting those and eliminate 2003 ones.
I have been running this in our environment and I see no issues. In fact i am using 2012 R2 DC which were problematic.
Here is another good link to upgrade from 2003 to 2012 or 2012 R2.
http://blogs.msmvps.com/mweber/2012/07/30/upgrading-an-active-directory-domain-from-windows-server-2003-or-windows-server-2003-r2-to-windows-server-2012/
Hope it helps.
Regards,
Calin

OraOledb for 64-bit, Linked Servers and SQL Server 2005 issues

Our environment is : SQL Server 2005, Windows Server 2003, 64-bit and 32-bit operating systems.
Problem on 64-bit operating system box: (32-bit works fine).
I am trying to access Oracle 10g database using linked server from our SQL Server 2005. In case of number fileds i got the following error:
Invalid data for type "numeric".
After going through one of the posting in this forumn i was able to resolve the problem by converting those column values to char while querying and then converting them back to numeric type on SQL server side.
But today i ran into another problem. There is a VARCHAR2 column. I was able to retrieve the data yesterday for that column but today i am getting a blank recordset. If i exclude the colum from the query then i am getting all the rows.
I am querying against a view and it has got a number of columns whose data type is VARCHAR2.
Again the problem is on 64-bit operating system only. We have a 32-bit operating system on which i am able to retrieve the data including this column. I looked at the data and everything looks OK. No funny characters etc.
I tried workarounds like using cast, to_char, checking for nulls etc., Nothing works.
Any help is greately appreciated. Thanks.

Did you find a resolution for this? We have similar problem. Set up a linked server in SQL 2006 to Oracle (running on Windows 64-bit) Linked server works and views I had set up were working but they added some new data in the Oracle test database I am using and now I get errors on one of the views.
Error I am getting on the view is "Cannot initialize the data source object of OLE DB Provider "OraOLDEDB.ORacle" for the linked server"
If I fine tune my queries to find the specific table or view that is at issue, then I get the error "inconsistent metadata for a column"

I can't link to an I series (IBM AS400) server from my sql server 2014 server (64 bit) -- but yes can link on sql server 2005 (32 bit)

I have an I series (IBM AS400) server linked "OK" to a sql 2005 sql server (32 big). I copied the link script (but changed credentials) from the sql server 2005 link and attempted to run it in the sql server 2014 server (on win 7 64
bit). There are no complaints from SSMS when I run the script, but when I try to query a table I get this error message:
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[IBM][System i Access ODBC Driver]Key value in connection string too long.".
Msg 7303, Level 16, State 1, Line 11
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "CWMPDTA".
Here is the script (from the sql server 2005 (32 bit)) I ran on the sql server 2014 SSMS -- is there anything I need to change? How can I get this I series server to link to my sql server 2014 server?
USE [master]
GO
/****** Object: LinkedServer [CWMPDTA] Script Date: 9/25/2014 10:39:12 AM ******/
EXEC master.dbo.sp_addlinkedserver @server = N'CWMPDTA', @srvproduct=N'cwmpdta', @provider=N'MSDASQL', @datasrc=N'iseries2', @provstr=N'Provider=IBMDA400.DataSource.1;Password=myPwrd;Persist Security Info=True;User ID=myID;Data Source=10.0.0.51;Initial Catalog=T9S', @catalog=N'T9S'
/* For security reasons the linked server remote logins password is changed with ######## */
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'CWMPDTA',@useself=N'False',@locallogin=NULL,@rmtuser=N'myID',@rmtpassword='myPwrd'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'collation compatible', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'data access', @optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'dist', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'pub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'rpc', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'rpc out', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'sub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'connect timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'collation name', @optvalue=null
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'lazy schema validation', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'query timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'use remote collation', @optvalue=N'true'
GO
Rich P

Thank you for this reply. I went to the link and selected the option for DB2s and ran the install. Then I started up SSMS. I copied the same script as above, and it executed successfully. But when I try to run a query against
a table in a database on this linked sever -- I get this error message:
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[IBM][System i Access ODBC Driver]Key value in connection string too long.".
Msg 7303, Level 16, State 1, Line 8
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "CWMPDTA".
Do I need to change the line containing -- @provider=N'MSDASQL', maybe?
this is the query I'm running:
select TOP 10 * from CWMPDTA.T9S.CWMPDTA.INSKU
The same exact query runs fine on the sql server 2005 linked server. Is there something I need to configure?
Rich P

MS sql server 2005 and encryption

I've got a Microsoft SQL Server 2005 database server set up
with encryption forced on. I managed to get the MS 1.1 jdbc driver
from Microsoft, I then tried to configure it into Coldfusion v
7.0.2 as an Other data source. The problem I've got now is that I
get the error
"com.microsoft.sqlserver.jdbc.SQLServerException: The SQL
Server login requires an SSL connection."
I previously tried to use the SQL Server data source type but
that didn't work either.
So how do I get past this hurdle?

There is currently no SSL support for JDBC connections.
Microsoft addresses it regarding SQL Server 2005 on this mdsn
forum thread:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1071465&SiteID=1

SQL Server 2005 performance decreases with DB size while SQL Server 2012 is fine

Hi,
We have a C# windows service running that polls some files and inserts/updates some fields in database.
The service was tested on a local dev machine with SQL Server 2012 running and performance was quite decent with any number of records. Later on the service was moved to a test stage environment where SQL Server 2005 is installed. At that point database
was still empty and service was running just fine but later on, after some 500k records were written, performance problems came to light. After some more tests we've founds out that, basically, database operation performance in SQL Server 2005 decreases with
a direct correlation with the database size. Here are some testing results:
Run#
1
2
3
4
5
DB size (records)
520k
620k
720k
820k
920k
SQL Server 2005
TotalRunTime
25:25.1
32:25.4
38:27.3
42:50.5
43:51.8
Get1
00:18.3
00:18.9
00:20.1
00:20.1
00:19.3
Get2
01:13.4
01:17.9
01:21.0
01:21.2
01:17.5
Get3
01:19.5
01:24.6
01:28.4
01:29.3
01:24.8
Count1
00:19.9
00:18.7
00:17.9
00:18.7
00:19.1
Count2
00:44.5
00:45.7
00:45.9
00:47.0
00:46.0
Count3
00:21.7
00:21.7
00:21.7
00:22.3
00:22.3
Count4
00:23.6
00:23.9
00:23.9
00:24.9
00:24.5
Process1
03:10.6
03:15.4
03:14.7
03:21.5
03:19.6
Process2
17:08.7
23:35.7
28:53.8
32:58.3
34:46.9
Count5
00:02.3
00:02.3
00:02.3
00:02.3
00:02.1
Count6
00:01.6
00:01.6
00:01.6
00:01.7
00:01.7
Count7
00:01.9
00:01.9
00:01.7
00:02.0
00:02.0
Process3
00:02.0
00:01.8
00:01.8
00:01.8
00:01.8
SQL Server 2012
TotalRunTime
12:51.6
13:38.7
13:20.4
13:38.0
12:38.8
Get1
00:21.6
00:21.7
00:20.7
00:22.7
00:21.4
Get2
01:38.3
01:37.2
01:31.6
01:39.2
01:37.3
Get3
01:41.7
01:42.1
01:35.9
01:44.5
01:41.7
Count1
00:20.3
00:19.9
00:19.9
00:21.5
00:17.3
Count2
01:04.5
01:04.8
01:05.3
01:10.0
01:01.0
Count3
00:24.5
00:24.1
00:23.7
00:26.0
00:21.7
Count4
00:26.3
00:24.6
00:25.1
00:27.5
00:23.7
Process1
03:52.3
03:57.7
03:59.4
04:21.2
03:41.4
Process2
03:05.4
03:06.2
02:53.2
03:10.3
03:06.5
Count5
00:02.8
00:02.7
00:02.6
00:02.8
00:02.7
Count6
00:02.3
00:03.0
00:02.8
00:03.4
00:02.4
Count7
00:02.5
00:02.9
00:02.8
00:03.4
00:02.5
Process3
00:21.7
00:21.0
00:20.4
00:22.8
00:21.5
One more thing is that it's not Process2 table that constantly grows in size but is Process1 table, that gets almost 100k records each run.
After that SQL Server 2005 has also been installed on a dev machine just to test things and we got exactly the same results. Both SQL Server 2005 and 2012 instances are installed using default settings with no changes at all. The same goes for databases
created for the service.
So the question is - why are there such huge differences between performance of SQL Server 2005 and 2012? Maybe there are some settings that are set by default in SQL Server 2012 database that need to be set manually in 2005?
What else can I try to test? The main problem is that production SQL Server will be updated god-knows-when and we can't just wait for that.
Any suggestions/advices are more than welcome.

...One more thing is that it's not Process2 table that constantly grows in size but is
Process1 table, that gets almost 100k records each run....
Hi,
It is not clear to me what is that you are doing, but now we have a better understanding on ONE of your tables an it is obviously you will get worse result as the data become bigger. Actually your table look like a automatic build table by ORM like Entity
Framework, and it's DDL probably do not much your needs. For example if your select query is using a filter on the other column that [setID] then you have no index and the server probably have to scan the entire table in order to find the records that you
need.
Forum is a suitable place to seek advice about a specific system (as I mentioned before we are not familiar with your system), and it is more suitable for general questions. For example the fact that you have no index except the index on the column [setID]
can indicate a problem. Ultimately to optimize the system will need to investigate it more thoroughly (as it is no longer appropriate forum ... but we're not there yet). Another point is that now we can see that you are using [timestamp] column, an this
implies that your are using this column as a filter for selecting the data. If so, then maybe a better DDL will be to use clustered index on this column and if needed a nonclustered index on the [setID] if it is needed at all...
what is obviously is that next is to check if this DDL fit
your specific needs (as i mentioned before).
Next step is to understand what action do you do with this table. (1) what is your query which become slowly in a bigger data set. (2) Are you using ORM (object relational mapping, like Entity Framework
code first), and if so then which one.
[Personal Site] [Blog] [Facebook]

Migrate biztalk 2006R2/SQL server 2005 projects to Biztalk 2013/SQL server 2012

We have Biztalk application projects deployed on Biztalk 2006R2/SQL server 2005 environment on a single server
Now we have installed and configured Biztalk 2013/SQL server 2012 in a multicomputer environment where Biztalk server is on one computer while SQL server is on the other.
Now it's time to migrate the projects 2006R2 to 2013.. Is it a smooth process? I found a lot of posts about migration from 2006R2 to Biztalk 2010... Just wondering if it is similar or more complex?? Appreciate any help/suggestions.. thanks!!

Hi Annee,
Following article should answer your question:
BizTalk Application Migration Guide
Also have a look at following forum post:
http://social.msdn.microsoft.com/Forums/en-US/f9ac6b6c-3dbe-487b-85c5-448d257d62f4/migration-from-biztalk-server-2006-to-2013?forum=biztalkgeneral
Maheshkumar S. Tiwari|http://tech-findings.blogspot.in/

Linked Server error: Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON' between sql server 2005 32 bit and sql server 2012 64 bit

Hi All,
Here the linked server is created between sql server 2012 64 bit and sql server 2005 32 bit. I am getting the below error when i try to access linked server from third server. I have created linked from Instance 1 to Instance 2. When i access it from
instance 3 i am getting the below error. SPN setting has been done between these 2 servers. Also the option 'Trust the delegate' is enabled for the both the service account.
'Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
Appreciate your quick response.
Vikas.M.S

Hello,
Please read the following resources:
http://www.databasejournal.com/features/mssql/article.php/3696506/Setting-Up-Delegation-for-Linked-Servers.htm
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/ea26de43-4c6b-4991-86d7-e1578f107c92/linked-server-login-failed-for-user-nt-authorityanonymous-logon?forum=sqldataaccess
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Can i open an SQL express 2005 database in SQL server express 2012?

Hi,
i have a database and it's in SQL express 2005 but because my windows 8 is not compatible with the installer, i have to install the latest 2012 installer. my problem now is that i cannot open it in the 2012 edition..what do i have to do?

Hi white_roses,
Could you let us know how do you restore the database to SQL Server 2012 Express edition? Please help to collect the detail error information of this issue, it will benefit for us to do further investigation.
As Sandesh and ED suggested above, we can directly detach our databases from SQL Server 2005 and then attach them to SQL Server 2012. For detail steps, please refer to the following article:
http://msdn.microsoft.com/en-us/library/ms187858.aspx
After we move a database from the instance of SQL Server on server A to the instance of SQL Server on server B, users may be unable to log in to the database on server B. If need the logins information on Server B, please refer to the following article:
http://support.microsoft.com/kb/918992
If you have any question, please feel free to let me know.
Thanks,
Jerry Li

MS-SQL Server 2005 SP1 vs MS-SQL Native Client 2008 or 2012

Hello,
I woud like to know if it's possible to use on a computer Windows Seven, the MS-SQL Native Client 2008 or 2012, and connect it on a MS-SQL Server 2005 (under Windows 2003 enterprise).
Regards,

Hello,
Yes, the SQL Server Native client is backward compatible, means you can use Client 2008 or higher to connect to a SQL Server 2005.
With some limitations the client is also forward compatible, means you can use a client 2005 to connect to SQL Server 2008 and higher; but the client isn't aware of new server features.
Olaf Helper
[ Blog] [ Xing] [ MVP]

DataBase Migration from SQL server 2005 to SQL server 2012

What are the challenges and steps to be taken care for proper migration of the Database.
Applications are using the Visual Studio 2012.
saikalyan

Few things that I can think of -
Verify all logins and users are migrated correctly.
Some of the SQL Server 2005 features/code could be deprecated in SQL Server 2012. Changes could be required before or after migration.
Some of the queries could have different performance (better or worse) on 2012 due to changes in query optimizer.
The applications/SSIS/DTS config files are updated to use the new server/instance name.
DNS alias names from the old servers (if used) are moved to the new server to have minimal impact on connection strings.
Plan for downtime of applications and batch processes.
Notify developers about the migration and the new server name(s)
- Aalam | (Blog)

Issue in rebuilding index after restoring database from sql server 2005 to 2012

Hi All,
We have recently restored a database named DBA_admin from our sql server 2005 instance to sql server 2012 and we have added the database to out weekly maintenance plan. After adding the database to maintenance plan the job is failing every weekend due to
below error message.
Error message from maintenance plan history:
Executing the query "ALTER INDEX [PK_lsttype] ON [dbo].[lstAssign..." failed with the following error: "Invalid object name 'admin.dbo.databaselog'.
ALTER_INDEX - dbo.PK_lsttype". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Below is the code within the maintenance plan which the rebuild index task is using for database dba_admin:
USE [dba_admin]
GO
ALTER INDEX [PK_lstType] ON [dbo].[lstType] REBUILD PARTITION = ALL WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 98, DATA_COMPRESSION = PAGE)
Please let me know if any one knows how to fix this issue.
Thanks in Advance.

Sorry for the confusion.
Here is what is happening.
The query is failing while trying to rebuild index [Pk_lsttype] on table [lstAssign], both these objects belong to database
admin.
I have verified the old instance there is table databaselog within the database
dba_admin, but in new SQL instance within the database dba_admin the table is not present.
Even I'm not sure of what this table databaselog has to do with rebuilding indexes on table
lstAssign within the admin database.
I have manually tried to execute the alter index command within the database
admin and it is failing with the below error.
ALTER_TABLE - dbo.Query_pnb_sms
Msg 208, Level 16, State 1, Procedure ddlDatabaseTriggerLog, Line 39
Invalid object name 'dba_admin.dbo.databaselog'.

Steps SSIS and SSAS Migration from sql server 2005 to 2012?

steps SSIS,SSRS and SSAS Migration from sql server 2005 to 2012? any precautions to take while migration.
any documentation or any specified steps.

Hi Vijay,
According to your description, you want to migrate SQL Server Integration Services and SQL Server Analysis Services from SQL Server 2005 to SQL Server 2012.
For how to migrate SQL Server Integration Services, please refer to the article:
http://www.bidn.com/blogs/DevinKnight/ssis/2718/upgrading-packages-to-ssis-2012.
In addition, since the issue regards SQL Server Integration Services. I suggest you post the question in the SQL Server Integration Services forums at
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlintegrationservices.
For how to migrate SQL Server Analysis Services, please refer to this article:
http://www.codeproject.com/Articles/435703/Migration-from-SQL-server-to.
In addition, since the issue regards SQL Server Analysis Services. I suggest you post the question in the SQL Server Analysis Services forums at
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlanalysisservices. It is appropriate and more experts will assist you.
Regards,
Michelle Li

SQL Server 2005 upgrade & migrate to 2012 method

Hi,
The situation is like this:
Currently I have SQL Server 2005 on an old Windows Server 2003. The target is to let SQL Server 2012 on Windows Server 2012 with the databases migrated over. The new server with Windows Server 2012 was prepared.
Originally my plan is to install SQL Server 2005 on the new Windows Sever 2012 first, migrate the database from old server to here, then upgrade SQL Server to 2012. Then found out this method cannot be used due to SQL Server 2005 is not compatible with Windows
Server 2012.
Alternative suggestions are appreciated.

SQL Server 2012 supports upgrade from the following versions of SQL Server:
SQL Server 2005 SP4 or later
SQL Server 2008 SP2 or later
SQL Server 2008 R2 SP1 or late
So please make sure that your existing sql server 2005 is upgraded to SP4 or later.
Then best way is use side by side.
Windows Sever 2012 on you new machine and sql server 2012.
Then use side by side method to migrate your old sql 2005 to new version 2012, ( moving backups and restore, logins, jobs, packages, configurations, maintenance plans,
linked server details and more. )
If you use in-place the in case of any issues we cant do anything to bring back the server to old version or fixing the issue may take lot of time. side by side its matter of navigating the connection and changing the connection setting for application and
putting databases for use ( online from single user or may be from online to online )
Raju Rasagounder MSSQL DBA

Sql server 2005 in server 2012 domain

Similar Messages

Maybe you are looking for