Quantcast
Channel: SQL Server Migration forum
Viewing all 1700 articles
Browse latest View live

SQL database upgrade from SQL 2014 to SQL 2017 impact on Team Foundation Server 2017

$
0
0

Hi,

I have a Team Foundation Server 2017 with a 2 Tier setup. My SQL Server is SQL 2014. Now I want to upgrade the SQL server to 2016 with an in place upgrade. My plan is to disconnect the databases with TFSServiceControl [quiesce] command and than upgrade the SQL Server to SQL 2016. When the upgrade process has finished I will use the TFSServiceControl [unquiesce] command.

Is this the right way to do the upgrade? I cannot find a guide which describes an only database upgrade for TFS.

Please help.

Kind regards,

Gerald (Planet X)


Synatax error on view

$
0
0

CREATE VIEW vw_bcpMasterSysobjects
as
   select 
       FIMU_POCTest..SE_Case_Detailes_Tbl.[SE Number], 
FIMU_POCTest..SE_Case_Detailes_Tbl.Country,
FIMU_POCTest..SE_Case_Detailes_Tbl.[SE Name],
FIMU_POCTest..SE_Case_Detailes_Tbl.[SE Setup Date] ,
FIMU_POCTest..SE_Case_Detailes_Tbl.[Acc Status],
FIMU_POCTest..SE_Case_Detailes_Tbl.[Legal Rep Name] ,
FIMU_POCTest..SE_Case_Detailes_Tbl.[Currency],
FIMU_POCTest..SE_Case_Detailes_Tbl.[Payement] ,
FIMU_POCTest..SE_Case_Detailes_Tbl.[Scenario Name] ,
FIMU_POCTest..SE_Case_Detailes_Tbl.[Target Name],
FIMU_POCTest..SE_Case_Detailes_Tbl.[Extension],
FIMU_POCTest..SE_Case_Detailes_Tbl.[FileName]= 'D:\Sajitha_Project\FIMU_POC\FIMU_POCDB\BlobLoc'+'\'+[FileName]  from FIMU_POCTest..SE_Case_Detailes_Tbl 

When I tried to create a view, it shows the error , 

Msg 102, Level 15, State 1, Procedure vw_bcpMasterSysobjects, Line 16
Incorrect syntax near '='.

Could you please correct me


sajitha

What are all the advantage of exporting sql database to csv, than to Excel?

$
0
0

Hi Team,

Could you please give me 

What are all the advantage of exporting sql database to csv, than to Excel?, Which is the best and efficient storage CSV/Excel?


sajitha

Restore database.

$
0
0

Hello All,

Somehow our TFS server database is corrupted, So I copied all database files (.mdf and .ldf) to other SQL server and trying to attach the files but I am getting following error

==============================================================

An inconsistency was detected during an internal operation. Please contact technical support.
Could not open new database ''. CREATE DATABASE is aborted.
File activation failure. The physical file name "C:\Program Files\Microsoft SQL Server\MSSQL13.TFSSQL\MSSQL\DATA\Tfs_TEST_log.ldf" may be incorrect. (Microsoft SQL Server, Error: 5243)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=5243&LinkId=20476

===================================================================

Also I have tried follwing Steps

1. Created a new database with same name 

2. dettach the database and copied currpted databs in datbase folder 

3. going to attach corrupted database its giving me above metioned error.

4. 

EXEC sp_resetstatus 'Tfs_TEST';
ALTER DATABASE Tfs_TEST SET EMERGENCY
DBCC checkdb('Tfs_TEST')
ALTER DATABASE Tfs_TEST SET SINGLE_USER WITH ROLLBACK IMMEDIATE DBCC
CheckDB('Tfs_TEST',REPAIR_ALLOW_DATA_LOSS) ALTER DATABASE Tfs_TEST
SET MULTI_USER

========================================================================

Please guide me how I can restore the database 


Thanks Ravikant Chaturvedi

SQL Server Migration Assistant Error: Error occurred while collecting data

$
0
0
I am using SQL Server Migration Assistant DB2 To SQL Server. 

When I try to connect a DB2 Server: 
Connection to DB2 established successfully.
Connection string: Provider=DB2OLEDB;Network Transport Library=TCPIP;User ID=XXXXXXX;Initial Catalog=XXXXXXXXXX;Package Collection=QGPL;Network Address=XXXXXXXX;Network Port=446;Connection Timeout=0;
Error occurred while collecting data.

SQL SERVER 2016 Compatibility with VS & SSRS 2017

$
0
0

Hi all:

I use SQL 2016 at work via SSMS.  Question:  would I be able to use Visual Studio 2017 and SSRS 2017 with SQL 2016?

Thanks!

Amy

====


A. Wolf

SSMA for Oracle. RAW(16) to uniqueidentifier conversion

$
0
0

We need to migrate data from Oracle tables having RAW(16) columns into SQL Server tables with corresponding uniqueidentifier columns.

SSMA 2008 migration reports an error in this case ("The given value of type Byte[] from the data source cannot be converted to type uniqueidentifier..."). I can change Oracle SELECT statement so that it can convert RAW(16) to something else, i.e. formatted varchar2(36) or anything else. But I still get the similar error (type String ... cannot be converted...). This looks quite strange because normally SqlServer can convert formatted string representation of GUID to uniqueidentifie.

Any way the question is:

Is it possible to cast Oracle type to another type that could be converter to uniqueidentifier?

Is it possible to tune the conversion procedure somehow, i.e. change SqlServer INSERT statement for a particular table or do something like this?

If it's not possible then can I solve the problem in another way?

Permanent changes of the structure of DBs is not an option for us. I would like to keep it as it is (Oracle's RAW16 -> SQlServer's uniqueidentifier) because otherwise I will need to fix this after the autoconversion (currently we have many installations of both database types and these columns are used in FKs and so on...).

restoring database to managed instnace

$
0
0

i am trying to restore bacpac file to sql server MANAGED INSTANCE, HAVING THE SSMS ON MY LOCAL COMPUTER,

AND ITS THROWING THIS ERROR


k


Migrating old SQL Server DB

$
0
0

I am hoping someone can help me.

We have an old SQL Server 2005 DB that is no longer in our production environment.  The database is quite large. The .Bak file is 700+ Gb.  It is a treasure trove of data that we would like use in our research labs.

Unfortunately, I can find no way to migrate this data.  We would like to move it to an open-source database like mySQL since costs are a big issue.  I have read that the newest SQL server product has a migration product that can handle this size.  

How can I use the migration product as a one time use instead of paying for and buying MS SQL server and then never using it again.

Ajay Choudhri, MD

Dept of Radiology

Capital Health - NJ

Login Failed for user ''. Reason Failed to open the explicitly specified database [Client: xxx.xx.x.xx]

$
0
0
I moved a dozen user databases from one 2005 instance on one machine to a 2008 R2 instance on another machine. The databases that I moved is displaying the message in a profiler trace "Cannot open databases "xxxx" request by the login. The login failed. Logon     Error: 18456, Severity : 14, State 38 Date\Time  Logon      Login failed for. Login failed for user "xxxxx\xxxxxxxxxx". Reason Failed to open the explicity specified database [Clientxxx.xx.x.xx]. Iused the backup and restore technique to move the user databases. Only these user databases that I moved is displaying the error. All other user databases seem to not be displaying these messages. On several of the user databases I deleted all the original database users with the exception of the users dbo, guest, INFORMATION_SCHEMA and sys. On one of the databases I even ran the sp_Changedbowner 'sa', true  stored procedure on changing the dbo user login to are sa account. Note the sa account has master as its default database. But that did not work either. I am still getting the messages on all the database that I moved to the 2008 R2 instance.

Migrating Oracle to SQL and indexes are mssing

SSMA convert Schema is success as log, but not seen tables created on SQL Server .Migration failed

Data From SQL Server Linked Server shows binary info

$
0
0

I am using SQL Server 2014 and DB2OLEDB Provider Version 5 to Read data from a DB2/AS400 Linked Server. 

When I run this query,

SELECT * FROM OPENQUERY (LINKED,'SELECT * FROM LINKED.LIBRARY.TABLE') ;

This returns binary data on the "CHAR () FOR BIT DATA feilds". 

I created the linked server with a script. 

EXEC master.dbo.sp_addlinkedserver @server = N'LINKED', @srvproduct=N'DB2', @provider=N'DB2OLEDB', @datasrc=N'QGPL', 
@provstr=N'Initial Catalog=LINKED;Network Transport Library=TCPIP;Host CCSID=37;PC Code Page=1252;Network Address=LINKED;
Network Port=446;Package Collection=QGPL;Default Schema=QGPL;Connect Timeout=15;Units of Work=RUW;DBMS Platform=DB2/AS400;
Use Early Metadata=False;Defer Prepare=True;DateTime As Char=False;Rowset Cache Size=0;Binary CodePage=0;Max Pool Size=100;
Datetime As Date=False;AutoCommit=True;Authentication=Server;Decimal As Numeric=False;Derive Parameters=True;LoadBalancing=False;
Persist Security Info=False;Cache Authentication=False;Mode=Read;Connection Pooling=True;Force Translate=0', @catalog=N'LINKED' ;

Unable to retrieve schemas of tables from sage 100 crm to SQL server

$
0
0

Hi all,

I have an important requirement of transferring data from sage100 crm -> SQL server 2017 -> Dynamics 365 for visualizations. I am able to retrieve the resultset in linked servers but not in the specific database outside of linked server. So far I tried the following and haven't succeeded since last week.

1. Created ODBC driver for sage100 as given in their documentation by the given link:

https://sagecity.na.sage.com/support_communities/sage100_erp/f/sage-100-technical-and-installation-discussions/69119/64-bit-odbc-connection-to-mas-4-5-installation

However I can view tables in linked server objects not their schemas. I tried to use SSIS for mapping but it's not working.

2. I tried to use the import wizard as specified in this link:

https://sagecity.na.sage.com/support_communities/sage100_erp/f/sage-100-technical-and-installation-discussions/84037/how-to-copy-tables-from-sage-2014-to-a-new-database-on-sql-server-2008-r2

I get the same error as specified in this link and realized that the datatype isn't matching with the one in SQL. For example, when I checked out the mapping for Date column name in the import wizard, I found out datatype as '23' which is very weird. 

I am able to query the data through openquery but uanble to get data into an existing DB as usually happens in import/export wizard.

I tried asking the sage community forums too but no one has replied yet.

Can someone help me on this?

Thanks.

Problem migrating large table with SQL Server Migration Assistant for Oracle

$
0
0

Hi

I'm trying to migrate a table with approximately 850 000 rows containing documents stored in a long raw field. The conversion is set to store those as Image-fields in MS SQL. But after 400 000 rows I get a Data migration error:

Could not count rows in the target table after migration. Migration may have succeeded, but row count in not verified.

Error: ExecuteReader requires an open and available Connection. The connection's current state is closed.

ExecuteNonQuery rewuires an open and available Connection. The connection's current state is closed.

I have tried with these changes under Migration in Default Project Settings:

Batch Size: 2000 (also tried 1000)

Data migration timeout: 1440

In my latest test I also tried with Table lock set to No.

Any help would be appreciated.

Regards, Torbjörn


MSSQL Database Migration from Localhost to online server

$
0
0

Hi everyone, I have developed one ERP application on .net Framework and MSSQL database on 2012 3 years ago and hosted the same on local (inhouse) server now I have migrated the ERP application to online VPS.

ERP Application is working fine after migration but issue is that all reports are taking too much time while we extract any report.

It seems the issue is the connection from database having some problem that is why it is not working properly online but working in local host.

Can anyone help me out to get this issue resolve please. 

Correct Compatibility Issues

$
0
0

Hello everyone, 

I am trying to migrate about 150 databases from SQL Server 2008 R2 to SQL 2017. My problems is that when I run Data Migration Assistant to assess databases I get a los of "Unqualified join" issues in stored procedures and views. I would like to know if there is a way to make necesary changes to each stored procedure and view in a fastest way.

Enable "Auto fix" feature Data Migration Assistant (DMA) 4.1

$
0
0

I am trying to migrate several databases with Data Migration Assistant. First I run a assessment to verify compatibility problems and I get many "Unqualified join" issues. Then I run a migration process and acording to the version 3.6 of DMA users can review the suggested code changes but I don't get anything and my databases migrate with the issues.

I there a way to enable "Auto fix" feature? Which tool can I use to solve the issues before migrate?

Thank you.

Snapshot Error

$
0
0

I want to create a snapshot on a database to drive(D). However getting an error said that "Cannot make the file "file_path" a sparse file. Make sure the file system supports sparse files."

Any help greatly appreciated. 

Oracle to SQL Server 2016 migration error on large files

$
0
0

Any parameter to make time out to zero?

Viewing all 1700 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>