SQL Server Management Studio: sql2005

Showing posts with label sql2005. Show all posts

Friday, March 30, 2012

Migrating DTS packages from SQL2000 to SQL2005

Hi,
My initial tests show that this feature will only see DTS Local Packages.
How can we migrate the DTS Meta Data Services Packages?
Thanks
ChrisThe requirements for migrating DTS packages saved to the
repository are explained in Books Online help topic:
Using the Package Migration Wizard
http://msdn2.microsoft.com/en-us/library/ms143496.aspx
-Sue
On Tue, 19 Sep 2006 08:04:56 -0600, "Chris Wood"
<anonymous@.discussions.microsoft.com> wrote:
>Hi,
>My initial tests show that this feature will only see DTS Local Packages.
>How can we migrate the DTS Meta Data Services Packages?
>Thanks
>Chris
>|||Sue,
This mentions Repository packages only if SQL2000, SQL2000 tools or the
Repository files are present on the local computer, the server that the
Migration Wizard is being run on I assume? As we have msdb as our Repository
we would have to migrate the SQL2000 msdb to the SQL2005 to find the Meta
Data Services packages?
Thanks
Chris
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:7a20h2pq7uggrgp7iuvggghvdpu343mms8@.4ax.com...
> The requirements for migrating DTS packages saved to the
> repository are explained in Books Online help topic:
> Using the Package Migration Wizard
> http://msdn2.microsoft.com/en-us/library/ms143496.aspx
> -Sue
> On Tue, 19 Sep 2006 08:04:56 -0600, "Chris Wood"
> <anonymous@.discussions.microsoft.com> wrote:
>>Hi,
>>My initial tests show that this feature will only see DTS Local Packages.
>>How can we migrate the DTS Meta Data Services Packages?
>>Thanks
>>Chris
>|||Yes...on the server where the migration wizard is being run.
The wizard needs the repository files to read the packages.
You just need the repository redistributable files on that
server.
-Sue
On Tue, 19 Sep 2006 10:07:43 -0600, "Chris Wood"
<anonymous@.discussions.microsoft.com> wrote:
>Sue,
>This mentions Repository packages only if SQL2000, SQL2000 tools or the
>Repository files are present on the local computer, the server that the
>Migration Wizard is being run on I assume? As we have msdb as our Repository
>we would have to migrate the SQL2000 msdb to the SQL2005 to find the Meta
>Data Services packages?
>Thanks
>Chris
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:7a20h2pq7uggrgp7iuvggghvdpu343mms8@.4ax.com...
>> The requirements for migrating DTS packages saved to the
>> repository are explained in Books Online help topic:
>> Using the Package Migration Wizard
>> http://msdn2.microsoft.com/en-us/library/ms143496.aspx
>> -Sue
>> On Tue, 19 Sep 2006 08:04:56 -0600, "Chris Wood"
>> <anonymous@.discussions.microsoft.com> wrote:
>>Hi,
>>My initial tests show that this feature will only see DTS Local Packages.
>>How can we migrate the DTS Meta Data Services Packages?
>>Thanks
>>Chris
>>
>|||Thanks Sue.
The analysts changed the packages to Local packages so we could use the
Migration Wizard.
Now we have migrated them we had to install the SQL2000 DTS Designer
Components, from the Feature Pack, but we still cannot see the migrated
packages. I remember an article by Brian Moran in SQL Mag on how to fix this
problem but I don't have the article on hand.
Can someone tell me the fix please? I think it had to do with the registry.
Thanks
Chris
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:2t81h2trkbmjlfsve86v8egsgs9lc01cci@.4ax.com...
> Yes...on the server where the migration wizard is being run.
> The wizard needs the repository files to read the packages.
> You just need the repository redistributable files on that
> server.
> -Sue
> On Tue, 19 Sep 2006 10:07:43 -0600, "Chris Wood"
> <anonymous@.discussions.microsoft.com> wrote:
>>Sue,
>>This mentions Repository packages only if SQL2000, SQL2000 tools or the
>>Repository files are present on the local computer, the server that the
>>Migration Wizard is being run on I assume? As we have msdb as our
>>Repository
>>we would have to migrate the SQL2000 msdb to the SQL2005 to find the Meta
>>Data Services packages?
>>Thanks
>>Chris
>>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>>news:7a20h2pq7uggrgp7iuvggghvdpu343mms8@.4ax.com...
>> The requirements for migrating DTS packages saved to the
>> repository are explained in Books Online help topic:
>> Using the Package Migration Wizard
>> http://msdn2.microsoft.com/en-us/library/ms143496.aspx
>> -Sue
>> On Tue, 19 Sep 2006 08:04:56 -0600, "Chris Wood"
>> <anonymous@.discussions.microsoft.com> wrote:
>>Hi,
>>My initial tests show that this feature will only see DTS Local
>>Packages.
>>How can we migrate the DTS Meta Data Services Packages?
>>Thanks
>>Chris
>>
>

Migrating DTS packages from SQL2000 to SQL2005

Wednesday, March 28, 2012

Migrating db's from 2000 to 2005 results in truncated columns?

Hi all,

Today I stumbled across something very strange. A couple weeks ago we migrated 2 servers from sql2000 to sql2005, and changed the default colation at the same time. The way I did it was I backed up all the user databases to *.bak files, uninstalled sql2000, installed sql2005 using the new default colation, and restored the databases. Today we discovered any columns that used to be char(xxx) were truncated to char(255), and the leftover went into a new column (i.e. a char(300) column became 2 columns, column1 char(255) and column2 char(45)).

Does this remotely make sense to anyone? I tested this out creating a dummy database and going from a 2k to 2k5 instance with the same colations would not split the columns, however from 2k to 2k5 with a different colation does. And so far it only appears to have affected the char datatype.

(note this is from sql2k sp3a to sql2k5 without sp1)

Is this a bug or am I just whacked?

Thanks

Anyone?|||

I'm moving this thread to the database engine forum, where you're more likely to get help.

Paul

Migrating database table data from 2005 to 2000

I'm trying to get a database from SQL2005 to SQL2000. I already recreated the database in SQL2005 and I'm just trying to get some data from just a few tables.

It doesn't appear the DTS or any export functionality is available in my version of SQL Express 2005...so how do I do this. I've tried installing everything I can find.

I've also tried BCP but I keep getting these errors:

SQLState = 08001, NativeError = 53
Error = [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [53].
SQLState = HYT00, NativeError = 0
Error = [Microsoft][SQL Native Client]Login timeout expired
SQLState = 08001, NativeError = 53
Error = [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

This is a LOCAL database and I have tried -T for trusted, I have also tried a username and password combination. The database is set to Allow Remote connections. Nothing is working.

I'm typing this

bcp somedb..countries out countries.csv -c -t , -S machine/SQLdatabase -T -U myusername

|||Moving to the SQL Server Express forum.|||

Your options are to (a) script out the tables, run those scripts in the SQL 2005 Express sever, and then use the Import/Export Wizard in SQL 2005 Express to move the data, (b) Check out some of the excellent third party tools.

Comparison Tools
Object Comparison:
AdeptSQL Diff
AlfaAlfa Software - SQL Server Comparison Tool
ApexSQL – SQL Diff
Best SoftTool – SQL DBCompare
e-Dule - DB SynchroComp
PrimeLogics - DataVision 2007
Quest – SchemaCompare
RAC4SQL's QALite (Free)
Red Gate – SQL Compare
SQL Effects Clarity
TASC - SQL Delta
Teratrax Database Compare
TulsaSoft - SQL Examiner
Voltex Data Systems - SQLDBcontrol
XpressApps - sqlXpress Diff
xSQL Software - xSQL Object
Data Comparison
ApexSQL – SQL Diff
Best SoftTool – SQL DBCompare
Quest - DataCompare
Red Gate – Data Compare
TASC - SQL Delta
TulsaSoft - SQL Data Examiner
xSQL Software - xSQL DataCompare
DTS Comparison
Red Gate – DTS Package Compare
Server Comparison
Quest - ServerCompare
Free Tools
RAC4SQL's QALite (Free)
SQL Effects Clarity CE Edition

|||

That would just get me to the same place I'm already at.

I don't have your step 3 this-->

Import/Export Wizard in SQL 2005 Express

These options do not appear in my SQL Server Management Studio Express. In fact, if they did, I'd be done.

|||

In Object Explorer, right click on your database, select [Tasks], then [Import].

Oops, forget the above, my mind was running on empty.

Try the DTSWizard:

{install drive}:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTSWizard.exe

|||

Arnie: I don't got it. I have done a search for DTS* and there is no such file on my computer. I don't have import/export under task. I installed some of the extra tools but apparently not all and you can't rerun the installation program...its too stupid. You can only rerun it from add/remove SQL in the CP, and then its looking for a .msi file but Microsoft distributes the tools as an .EXE. Around and around you go....whoever wrote the installation for SQL Express/2005 should be fired...but only have he/she is beaten profusely about the head out back.

I have Express and apparently there is no SSIS available and no DTS avilable. I've been around this a 100 different ways. I only have 3 tables here....I just want to get bcp running and move on back to SQL 2000. It looks like Microsoft is now charging for the developer tools for SQL 2005 I guess..

I don't have a firewall running. Why does BCP error out? I'm at a loss.

|||

First, verify that [Allow Remote Connections] is checked in SQL Server Configuration Manager.

Second, the DTSWizard is available in the 'toolkit' for download here: http://go.microsoft.com/fwlink/?LinkId=65111

sql

Migrating Data from MySQL

Hello

I am looking for a way to migrate my data from a MySQL database to a SQL2005 Express data base. All of my MySQL Schemas only have 1 or 2 tables in them so I would imagine that it isn't that hard to do. I treid just exporting it to a CSV file with the intention of just using import/export in MSSQL but in the express edition, it ain't there. Like I stated all of my schemas are only 1 or two tables none are linked in any way they are independant table and the most records any one of the tables contain is around 250. Any suggestions?

hi,

as you already found, SQLExpress does not provide import/export tools, but you can rely on the underlying fundametals of the engine it self to perform such a kind of operation..

you can, for instance, perform a bulk insert as indicated in http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=723808&SiteID=1, or directly using BCP

additional "modes" are indicated in http://blogs.msdn.com/euanga/archive/2006/07/20/672272.aspx

regards

|||I don't mean to sound like a total dummy but I sort of understand what is being said and there is some really good round about information but, it just isn't getting me there. I have a table right now for example that I exported in CSV format from MySQL that has 6 columns and 203 rows. If I create this same table in SQL2005 Express, how do I bring that data into my SQL 2005 database. Admittedly my experience level with SQL and Scripting is not quite beginner but I wouldn't consider myself intermediate either. Could you dumb it down for me a little?|||Hi,

I was in the process of trying to load data into a SQL Express DB with bcp see
Unable to open BCP host data-file
when I ran across this post. I read the above linked articles. The DTSwizard seems to only want to add a new table where bcp will load data into an existing table using a format file.
I have used bcp to load data in SQL Server 2000 but am having trouble with SQL Server 2005 Express. We are planning to purchase the standard version of SQL Server 2005, but I was wanting to get some feel for 2005 it until the $$$ actually come through. Isn't that what Express version is for?

Any help?|||hi

a way to migrate is you import into Access and afzer them you build in SQL-Express the Table structure and import via ODBC the dates into the new table.

I have this do somtimes from MySQL to acces and then to SQLExpress 2005 and vice versa

sincerly
Helmi|||hi

a way to migrate is you import into Access and afzer them you build in

SQL-Express the Table structure and import via ODBC the dates into the

new table.

I have this do somtimes from MySQL to acces and then to SQLExpress 2005 and vice versa

sincerly

Helmi|||This sounds like it would be a good option. I was exploring the possibility of doing that, I even went so far as to import my tables in to Access however, I don't see a way to bring the data over into SQL express. Someone had mentioned using the DTS wizard but unless I am missing something, it isn't included in SQL 2005 express.|||The links above reference a utility
"C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTSWizard.exe"

It doesn't work for me because it seems to create the table definitions from the data file and I already have that part done.|||Nevermind I figure out how the Access option works. That was the ticket. Thank you.

Monday, March 26, 2012

Migrating AS2000 to AS2005 on two seperate machines

Hi champs!

I have two seperates machines, one SQL2000 with some Cubes, and one with sql2005 and AS 2005.

I've tried the migrate wizard, but the sql2005 machines cannot connect to the sql2000 machine through OLAP connection.

The two machines ar in the same workgroup, but not in a domain.

Do I have to make a linked server connection? and if so how exactly is the syntax for connecting to a 2000 OLAP cubes?

I've tried to install AS2000 on my sql2005 machine, but that will not work.

I cannot restore AS2000 cubes on the AS2005 either.

/Many thanks

For one, to be able to install AS2000 on AS2005 machine you need to make sure you are running Analysis Server as named instance.

You can ether reinstall AS2005 and choose it to be named instance or use ASInstanceRename utility to rename defult instance. After that you should be able to install AS2000.

As for not being able to migrate from remote machine, if you choose to go that way. Try first installing AS2000 tools- Analysis Manager and use and work out through process of being able to use that to remotely access AS2000 server. http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/anservog.mspx

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Migrating AS2000 to AS2005 on two seperate machines

Hi champs!

I have two seperates machines, one SQL2000 with some Cubes, and one with sql2005 and AS 2005.

I've tried the migrate wizard, but the sql2005 machines cannot connect to the sql2000 machine through OLAP connection.

The two machines ar in the same workgroup, but not in a domain.

Do I have to make a linked server connection? and if so how exactly is the syntax for connecting to a 2000 OLAP cubes?

I've tried to install AS2000 on my sql2005 machine, but that will not work.

I cannot restore AS2000 cubes on the AS2005 either.

/Many thanks

For one, to be able to install AS2000 on AS2005 machine you need to make sure you are running Analysis Server as named instance.

You can ether reinstall AS2005 and choose it to be named instance or use ASInstanceRename utility to rename defult instance. After that you should be able to install AS2000.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

sql

Friday, March 23, 2012

Migrate SQL2005 from Standard to Enterprise edition

Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise editio
n ?
I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
prompted the following message after a few step.
"To change existing instance of SQL2005 to a different edition of SQL2005,
you must run SQL2005 Setup from the command prompt and include the
SKUUPGRADE=1 parameter".
Followed the instruction to run setup with the parameter, upgraded
successfully but it got error when I started SSMS.
"could not load file or assembly Microsoft.Sqlserver.Management.Reports,
Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one o
f
its dependencies. The system could not find the file specified."
End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
Looking forward to your advices.Hi
"Johnny" wrote:

> Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edit
ion ?
> I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
> prompted the following message after a few step.
> "To change existing instance of SQL2005 to a different edition of SQL2005,
> you must run SQL2005 Setup from the command prompt and include the
> SKUUPGRADE=1 parameter".
> Followed the instruction to run setup with the parameter, upgraded
> successfully but it got error when I started SSMS.
> "could not load file or assembly Microsoft.Sqlserver.Management.Reports,
> Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one
of
> its dependencies. The system could not find the file specified."
> End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
> Looking forward to your advices.
You don't say what options you used on the command prompt, at a guess you
didn't specify UPGRADE=SQL_Engine as shown in the example on
http://msdn2.microsoft.com/en-us/li...aspx#skuupgrade and have
also upgraded the tools as well, which for some reason didn't work?
You could have re-installed the tools on their own using the reinstallmode
parameter
http://msdn2.microsoft.com/en-us/li...x#reinstallmode and the
ADDLOCAL parameter set to the Client_components
You will now need to re-apply service pack 2 and subsequent hotfixes.
John|||Hi John,
I wish to clarify that upgrading the edition has to specify
UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
the client tools is no need for the edition upgrade (only sql_engine is
required.)
Johnny
"John Bell" wrote:

> Hi
> "Johnny" wrote:
>
> You don't say what options you used on the command prompt, at a guess you
> didn't specify UPGRADE=SQL_Engine as shown in the example on
> http://msdn2.microsoft.com/en-us/li...aspx#skuupgrade and have
> also upgraded the tools as well, which for some reason didn't work?
> You could have re-installed the tools on their own using the reinstallmode
> parameter
> http://msdn2.microsoft.com/en-us/li...x#reinstallmode and t
he
> ADDLOCAL parameter set to the Client_components
> You will now need to re-apply service pack 2 and subsequent hotfixes.
> John|||Hi
"Johnny" wrote:

> Hi John,
> I wish to clarify that upgrading the edition has to specify
> UPGRADE=SQL_ENGINE as well which I did not specify before. That means tha
t
> the client tools is no need for the edition upgrade (only sql_engine is
> required.)
> Johnny
> "John Bell" wrote:
Had you service packed the original installation, and were they re-applied
after the upgrade?
John|||Applied the service pack 2 before and after the edition upgrade.
Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
well for edition upgrade, isn't it ?
Ta.
"John Bell" wrote:

> Hi
> "Johnny" wrote:
>
> Had you service packed the original installation, and were they re-applied
> after the upgrade?
> John
>|||Hi
"Johnny" wrote:

> Applied the service pack 2 before and after the edition upgrade.
> Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
> well for edition upgrade, isn't it ?
> Ta.
>
I believe so, but I have not found anywhere to confirm this.
John

Migrate SQL2005 from Standard to Enterprise edition

Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edition ?
I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
prompted the following message after a few step.
"To change existing instance of SQL2005 to a different edition of SQL2005,
you must run SQL2005 Setup from the command prompt and include the
SKUUPGRADE=1 parameter".
Followed the instruction to run setup with the parameter, upgraded
successfully but it got error when I started SSMS.
"could not load file or assembly Microsoft.Sqlserver.Management.Reports,
Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one of
its dependencies. The system could not find the file specified."
End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
Looking forward to your advices.
Hi
"Johnny" wrote:

> Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edition ?
> I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
> prompted the following message after a few step.
> "To change existing instance of SQL2005 to a different edition of SQL2005,
> you must run SQL2005 Setup from the command prompt and include the
> SKUUPGRADE=1 parameter".
> Followed the instruction to run setup with the parameter, upgraded
> successfully but it got error when I started SSMS.
> "could not load file or assembly Microsoft.Sqlserver.Management.Reports,
> Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one of
> its dependencies. The system could not find the file specified."
> End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
> Looking forward to your advices.
You don't say what options you used on the command prompt, at a guess you
didn't specify UPGRADE=SQL_Engine as shown in the example on
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgrade and have
also upgraded the tools as well, which for some reason didn't work?
You could have re-installed the tools on their own using the reinstallmode
parameter
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode and the
ADDLOCAL parameter set to the Client_components
You will now need to re-apply service pack 2 and subsequent hotfixes.
John
|||Hi John,
I wish to clarify that upgrading the edition has to specify
UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
the client tools is no need for the edition upgrade (only sql_engine is
required.)
Johnny
"John Bell" wrote:

> Hi
> "Johnny" wrote:
>
> You don't say what options you used on the command prompt, at a guess you
> didn't specify UPGRADE=SQL_Engine as shown in the example on
> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgrade and have
> also upgraded the tools as well, which for some reason didn't work?
> You could have re-installed the tools on their own using the reinstallmode
> parameter
> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode and the
> ADDLOCAL parameter set to the Client_components
> You will now need to re-apply service pack 2 and subsequent hotfixes.
> John
|||Hi
"Johnny" wrote:

> Hi John,
> I wish to clarify that upgrading the edition has to specify
> UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
> the client tools is no need for the edition upgrade (only sql_engine is
> required.)
> Johnny
> "John Bell" wrote:
Had you service packed the original installation, and were they re-applied
after the upgrade?
John
|||Applied the service pack 2 before and after the edition upgrade.
Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
well for edition upgrade, isn't it ?
Ta.
"John Bell" wrote:

> Hi
> "Johnny" wrote:
>
> Had you service packed the original installation, and were they re-applied
> after the upgrade?
> John
>
|||Hi
"Johnny" wrote:

> Applied the service pack 2 before and after the edition upgrade.
> Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
> well for edition upgrade, isn't it ?
> Ta.
>
I believe so, but I have not found anywhere to confirm this.
John

Migrate SQL2005 from Standard to Enterprise edition

Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edition ?
I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
prompted the following message after a few step.
"To change existing instance of SQL2005 to a different edition of SQL2005,
you must run SQL2005 Setup from the command prompt and include the
SKUUPGRADE=1 parameter".
Followed the instruction to run setup with the parameter, upgraded
successfully but it got error when I started SSMS.
"could not load file or assembly Microsoft.Sqlserver.Management.Reports,
Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one of
its dependencies. The system could not find the file specified."
End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
Looking forward to your advices.Hi
"Johnny" wrote:
> Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edition ?
> I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
> prompted the following message after a few step.
> "To change existing instance of SQL2005 to a different edition of SQL2005,
> you must run SQL2005 Setup from the command prompt and include the
> SKUUPGRADE=1 parameter".
> Followed the instruction to run setup with the parameter, upgraded
> successfully but it got error when I started SSMS.
> "could not load file or assembly Microsoft.Sqlserver.Management.Reports,
> Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one of
> its dependencies. The system could not find the file specified."
> End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
> Looking forward to your advices.
You don't say what options you used on the command prompt, at a guess you
didn't specify UPGRADE=SQL_Engine as shown in the example on
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgrade and have
also upgraded the tools as well, which for some reason didn't work?
You could have re-installed the tools on their own using the reinstallmode
parameter
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode and the
ADDLOCAL parameter set to the Client_components
You will now need to re-apply service pack 2 and subsequent hotfixes.
John|||Hi John,
I wish to clarify that upgrading the edition has to specify
UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
the client tools is no need for the edition upgrade (only sql_engine is
required.)
Johnny
"John Bell" wrote:
> Hi
> "Johnny" wrote:
> > Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edition ?
> >
> > I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
> > prompted the following message after a few step.
> >
> > "To change existing instance of SQL2005 to a different edition of SQL2005,
> > you must run SQL2005 Setup from the command prompt and include the
> > SKUUPGRADE=1 parameter".
> >
> > Followed the instruction to run setup with the parameter, upgraded
> > successfully but it got error when I started SSMS.
> >
> > "could not load file or assembly Microsoft.Sqlserver.Management.Reports,
> > Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one of
> > its dependencies. The system could not find the file specified."
> >
> > End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
> > Looking forward to your advices.
> You don't say what options you used on the command prompt, at a guess you
> didn't specify UPGRADE=SQL_Engine as shown in the example on
> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgrade and have
> also upgraded the tools as well, which for some reason didn't work?
> You could have re-installed the tools on their own using the reinstallmode
> parameter
> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode and the
> ADDLOCAL parameter set to the Client_components
> You will now need to re-apply service pack 2 and subsequent hotfixes.
> John|||Hi
"Johnny" wrote:
> Hi John,
> I wish to clarify that upgrading the edition has to specify
> UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
> the client tools is no need for the edition upgrade (only sql_engine is
> required.)
> Johnny
> "John Bell" wrote:
Had you service packed the original installation, and were they re-applied
after the upgrade?
John|||Applied the service pack 2 before and after the edition upgrade.
Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
well for edition upgrade, isn't it ?
Ta.
"John Bell" wrote:
> Hi
> "Johnny" wrote:
> > Hi John,
> >
> > I wish to clarify that upgrading the edition has to specify
> > UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
> > the client tools is no need for the edition upgrade (only sql_engine is
> > required.)
> >
> > Johnny
> > "John Bell" wrote:
> Had you service packed the original installation, and were they re-applied
> after the upgrade?
> John
>|||Hi
"Johnny" wrote:
> Applied the service pack 2 before and after the edition upgrade.
> Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
> well for edition upgrade, isn't it ?
> Ta.
>
I believe so, but I have not found anywhere to confirm this.
Johnsql

Wednesday, March 21, 2012

migrate objects between SQL2005

I got 2 development servers, I m triyng to move some data from 2 tables to other tables from other database located in other server.

I was using Sql Server 2005 Business Intelligence Development Studio to acommplish this, but when i debug it is shows me error.

someone can tell me the right steps to do this?

If you are using a windows authenticated account to access both servers, just right-click the table in the source database, go to Script Table as --> CREATE to --> New query editor window.

Once the script is generated, right-click in your script and go to Connection -->Change Connection, and connect to the other SQL Server. Once connected, select the appropriate database, and run the create script to add the table.

Then you can run a simple insert statement to post records from the source table to the new table using fully qulified naming. For example:

Insert into TargetTableName
Select * from SourceServerName.SourceDatabase.dbo.SourceTableName

sql

Migrate MSExcel worksheet sources to SQL2005

Hi,

Is there anyway I could do to migrate my data on my excel workbook to SQL Server 2005 per worksheet? Meaning, I have to create table for all my excel worksheet then transfer all the data to a new table through SSIS package.

How will I possibly do this? Please help.

Thanks in advance.

Have you tried the import wizard? That can import from Excel Data Sources.

-Jamie

|||Hi,

I just want to elaborate what I am about to do here to clarify things up.

In my case, I have 50 worksheet in my Excel workbook and I would like these worksheets be transferred in our SQL Server 2005 database, one table per worksheet. Now, I am planning to use SSIS "Foreach" control block so that SSIS recusively gets data on every worksheet, then SSIS package will transfer the data gathered on one table to another.

Is this task possible in SSIS? If not, kindly advise me of a more suitable solution for this. Or, is there any available custom script/coding for this in VS2005?

Please help. Thanks in advance.
|||

As Jamie said the Import Wizard should be able to help you.

In the SQL Server Management Studio right click on your destination database and choose Tasks->Import Data. Select Excel as your source and go from there.

Thanks.

Monday, March 12, 2012

Migrate database from SQL2005 to SQL 2000 (or MSDE)

Hi,
Is it possible to do? (how to do it)
I've tied to do backup and thet to restore it but it hasn't work.
Regards
KrisHi
No, the backup and data files are not compatible when going from 2005 to 200
0.
You have to script the schema and data out and run it against 2000.
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Kris" wrote:

> Hi,
> Is it possible to do? (how to do it)
> I've tied to do backup and thet to restore it but it hasn't work.
> Regards
> Kris

Migrate database from SQL2005 to SQL 2000 (or MSDE)

Hi,
Is it possible to do? (how to do it)
I've tied to do backup and thet to restore it but it hasn't work.
Regards
KrisHi
No, the backup and data files are not compatible when going from 2005 to 2000.
You have to script the schema and data out and run it against 2000.
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Kris" wrote:
> Hi,
> Is it possible to do? (how to do it)
> I've tied to do backup and thet to restore it but it hasn't work.
> Regards
> Kris

Migrate database from SQL2005 to SQL 2000 (or MSDE)

Hi,
Is it possible to do? (how to do it)
I've tied to do backup and thet to restore it but it hasn't work.
Regards
Kris
Hi
No, the backup and data files are not compatible when going from 2005 to 2000.
You have to script the schema and data out and run it against 2000.
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Kris" wrote:

> Hi,
> Is it possible to do? (how to do it)
> I've tied to do backup and thet to restore it but it hasn't work.
> Regards
> Kris

Migrate data from Oracle to SQL2005 64-bit

Hi,
I'm trying to migrate data from Oracle 10g to SQL2005 64-bit but I've
ran into some problems. First I tried using SSMA vith 32-bit Oracle
client got connection with both databases. I was able to create
objects (tables,index etc..) but when I tried to migrate data SSMA
stopped at 2%. I tried the same against SQL2005 32-bit everything
worked fine.
I then changed Oracle client from 32-bit to 64-bit so I was able to
create a linked server but moving data with insert into..Select * from
linked server did take some time, about 1 million rows/30-min this is
too slow!
SSMA doesnt seem to be working with 64-bit Oracle client? Can't get
connected to the Oracle database.
So what to do, doesn't SSMA work with SQL2005 64-bit? What Oracle
client should I use? Is SSIS a way out of the problem. Could I speed
up moving data via linked server?
Thanks in advance
Regards /Patrik
Patrik,
Have you tried the import wizard from SQL Server 2005 Management Studio?
Right-click on the database that you want to import to, choose Tasks /
Import Data ... and go through the dialogs. One of the data sources is
"Microsoft OLE DB Provider for Oracle". Choose that, specify where you want
the data to come from, then where it will go on your server, etc.
(Disclaimer: I have never personally tried an import from Oracle.) This
import wizard will actually make an SSIS package to do the imports for you.
SSIS can use the Bulk Insert facilities so it can be about as fast as
possible, provided the mappings are simple.
RLF
<pama@.unitema.se> wrote in message
news:3d51377a-3f73-49c1-a7aa-9970106b79ad@.8g2000hse.googlegroups.com...
> Hi,
> I'm trying to migrate data from Oracle 10g to SQL2005 64-bit but I've
> ran into some problems. First I tried using SSMA vith 32-bit Oracle
> client got connection with both databases. I was able to create
> objects (tables,index etc..) but when I tried to migrate data SSMA
> stopped at 2%. I tried the same against SQL2005 32-bit everything
> worked fine.
> I then changed Oracle client from 32-bit to 64-bit so I was able to
> create a linked server but moving data with insert into..Select * from
> linked server did take some time, about 1 million rows/30-min this is
> too slow!
> SSMA doesnt seem to be working with 64-bit Oracle client? Can't get
> connected to the Oracle database.
> So what to do, doesn't SSMA work with SQL2005 64-bit? What Oracle
> client should I use? Is SSIS a way out of the problem. Could I speed
> up moving data via linked server?
> Thanks in advance
> Regards /Patrik
|||Hi,
I also have seen many problems connecting to Oracle from SQL Server 2005
64-bit. This version of the client and this patch worked fine for me:
Oracle Client 10.2.0.1.0
Oracle Database 10g Release 2 Patch Set 2 10.2.0.3.0
Hope this helps,
Ben Nevarez
"pama@.unitema.se" wrote:

> Hi,
> I'm trying to migrate data from Oracle 10g to SQL2005 64-bit but I've
> ran into some problems. First I tried using SSMA vith 32-bit Oracle
> client got connection with both databases. I was able to create
> objects (tables,index etc..) but when I tried to migrate data SSMA
> stopped at 2%. I tried the same against SQL2005 32-bit everything
> worked fine.
> I then changed Oracle client from 32-bit to 64-bit so I was able to
> create a linked server but moving data with insert into..Select * from
> linked server did take some time, about 1 million rows/30-min this is
> too slow!
> SSMA doesnt seem to be working with 64-bit Oracle client? Can't get
> connected to the Oracle database.
> So what to do, doesn't SSMA work with SQL2005 64-bit? What Oracle
> client should I use? Is SSIS a way out of the problem. Could I speed
> up moving data via linked server?
> Thanks in advance
> Regards /Patrik
>
|||BTW, it is the 32-bit client.
Ben Nevarez
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hi,
> I also have seen many problems connecting to Oracle from SQL Server 2005
> 64-bit. This version of the client and this patch worked fine for me:
> Oracle Client 10.2.0.1.0
> Oracle Database 10g Release 2 Patch Set 2 10.2.0.3.0
> Hope this helps,
> Ben Nevarez
>
>
> "pama@.unitema.se" wrote:

Migrate data from Oracle to SQL2005 64-bit

Hi,
I'm trying to migrate data from Oracle 10g to SQL2005 64-bit but I've
ran into some problems. First I tried using SSMA vith 32-bit Oracle
client got connection with both databases. I was able to create
objects (tables,index etc..) but when I tried to migrate data SSMA
stopped at 2%. I tried the same against SQL2005 32-bit everything
worked fine.
I then changed Oracle client from 32-bit to 64-bit so I was able to
create a linked server but moving data with insert into..Select * from
linked server did take some time, about 1 million rows/30-min this is
too slow!
SSMA doesnt seem to be working with 64-bit Oracle client' Can't get
connected to the Oracle database.
So what to do, doesn't SSMA work with SQL2005 64-bit? What Oracle
client should I use? Is SSIS a way out of the problem. Could I speed
up moving data via linked server?
Thanks in advance
Regards /PatrikPatrik,
Have you tried the import wizard from SQL Server 2005 Management Studio?
Right-click on the database that you want to import to, choose Tasks /
Import Data ... and go through the dialogs. One of the data sources is
"Microsoft OLE DB Provider for Oracle". Choose that, specify where you want
the data to come from, then where it will go on your server, etc.
(Disclaimer: I have never personally tried an import from Oracle.) This
import wizard will actually make an SSIS package to do the imports for you.
SSIS can use the Bulk Insert facilities so it can be about as fast as
possible, provided the mappings are simple.
RLF
<pama@.unitema.se> wrote in message
news:3d51377a-3f73-49c1-a7aa-9970106b79ad@.8g2000hse.googlegroups.com...
> Hi,
> I'm trying to migrate data from Oracle 10g to SQL2005 64-bit but I've
> ran into some problems. First I tried using SSMA vith 32-bit Oracle
> client got connection with both databases. I was able to create
> objects (tables,index etc..) but when I tried to migrate data SSMA
> stopped at 2%. I tried the same against SQL2005 32-bit everything
> worked fine.
> I then changed Oracle client from 32-bit to 64-bit so I was able to
> create a linked server but moving data with insert into..Select * from
> linked server did take some time, about 1 million rows/30-min this is
> too slow!
> SSMA doesnt seem to be working with 64-bit Oracle client' Can't get
> connected to the Oracle database.
> So what to do, doesn't SSMA work with SQL2005 64-bit? What Oracle
> client should I use? Is SSIS a way out of the problem. Could I speed
> up moving data via linked server?
> Thanks in advance
> Regards /Patrik|||Hi,
I also have seen many problems connecting to Oracle from SQL Server 2005
64-bit. This version of the client and this patch worked fine for me:
Oracle Client 10.2.0.1.0
Oracle Database 10g Release 2 Patch Set 2 10.2.0.3.0
Hope this helps,
Ben Nevarez
"pama@.unitema.se" wrote:
> Hi,
> I'm trying to migrate data from Oracle 10g to SQL2005 64-bit but I've
> ran into some problems. First I tried using SSMA vith 32-bit Oracle
> client got connection with both databases. I was able to create
> objects (tables,index etc..) but when I tried to migrate data SSMA
> stopped at 2%. I tried the same against SQL2005 32-bit everything
> worked fine.
> I then changed Oracle client from 32-bit to 64-bit so I was able to
> create a linked server but moving data with insert into..Select * from
> linked server did take some time, about 1 million rows/30-min this is
> too slow!
> SSMA doesnt seem to be working with 64-bit Oracle client' Can't get
> connected to the Oracle database.
> So what to do, doesn't SSMA work with SQL2005 64-bit? What Oracle
> client should I use? Is SSIS a way out of the problem. Could I speed
> up moving data via linked server?
> Thanks in advance
> Regards /Patrik
>|||BTW, it is the 32-bit client.
Ben Nevarez
"Ben Nevarez" wrote:
> Hi,
> I also have seen many problems connecting to Oracle from SQL Server 2005
> 64-bit. This version of the client and this patch worked fine for me:
> Oracle Client 10.2.0.1.0
> Oracle Database 10g Release 2 Patch Set 2 10.2.0.3.0
> Hope this helps,
> Ben Nevarez
>
>
> "pama@.unitema.se" wrote:
> > Hi,
> >
> > I'm trying to migrate data from Oracle 10g to SQL2005 64-bit but I've
> > ran into some problems. First I tried using SSMA vith 32-bit Oracle
> > client got connection with both databases. I was able to create
> > objects (tables,index etc..) but when I tried to migrate data SSMA
> > stopped at 2%. I tried the same against SQL2005 32-bit everything
> > worked fine.
> >
> > I then changed Oracle client from 32-bit to 64-bit so I was able to
> > create a linked server but moving data with insert into..Select * from
> > linked server did take some time, about 1 million rows/30-min this is
> > too slow!
> >
> > SSMA doesnt seem to be working with 64-bit Oracle client' Can't get
> > connected to the Oracle database.
> >
> > So what to do, doesn't SSMA work with SQL2005 64-bit? What Oracle
> > client should I use? Is SSIS a way out of the problem. Could I speed
> > up moving data via linked server?
> >
> > Thanks in advance
> >
> > Regards /Patrik
> >

Wednesday, March 7, 2012

Microsoft.Jet.OLEDB.4.0 has not been registered. ?

Hi folks,
We've got SQL2005 April CTP i64 running on Win2003 with SP1 appied (Itenium Proc). Last week, one of developer sent me an email with error msg,

: Msg 7403, Level 16, State 1, Line 1

The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.

I ran Component Checker against that box and it found that MDAC2.8 with SP2 installed. I also found from MS site that Jet 4.0 SP8 i64 version available but the installation aborted due to newer version installed on the box. I am stucked. Any advice would be appreciated.

Sunny

Sunny,

It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.

I hope this information proves helpful.

David Sceppa
ADO.NET Program Manager
Microsoft|||

Does MS have some kind of plans for x64 based 64-bit .net apps to connect to Access 2007 or this a permanent solution?

|||

David Sceppa - Microsoft wrote:
Sunny,
It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.
I hope this information proves helpful.
David Sceppa
ADO.NET Program Manager
Microsoft

Would this also be revelant for OPENROWSET queries that use the driver? For example, the following select runs fine on my dev box (32bit SQL 2005), yet fails on our live box ((SQL 2005 64 bit)) .(it is part of a greater process that *should* bein in SSIS, but is being pushed in as a 'quick fix')

select [User Name],[Password], [Store Number] ,getdate(),''2008-12-31 00:00:00.000'',''1980-01-01 00:00:00.000''

from OPENROWSET(''Microsoft.Jet.OLEDB.4.0'',''Excel 8.0;Database=c:\Username and passwords v1.1.xls'',''SELECT * FROM [staff login details$]'')

version info from live:

7 FileDescription SQL Server Windows NT - 64 Bit
8 FileVersion 2005.090.2153.00

Microsoft.Jet.OLEDB.4.0 has not been registered. ?

Hi folks,
We've got SQL2005 April CTP i64 running on Win2003 with SP1 appied (Itenium Proc). Last week, one of developer sent me an email with error msg,

: Msg 7403, Level 16, State 1, Line 1

The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.

Sunny

Sunny,

I hope this information proves helpful.

David Sceppa
ADO.NET Program Manager
Microsoft|||

Does MS have some kind of plans for x64 based 64-bit .net apps to connect to Access 2007 or this a permanent solution?

|||

David Sceppa - Microsoft wrote:
Sunny,
It sounds like the developer is executing code in a 64-bit application, and is looking for the Jet OLE DB Provider. There is no 64-bit OLE DB Provider for Jet databases. Your developer would need to use a 32-bit application.
I hope this information proves helpful.
David Sceppa
ADO.NET Program Manager
Microsoft

select [User Name],[Password], [Store Number] ,getdate(),''2008-12-31 00:00:00.000'',''1980-01-01 00:00:00.000''

from OPENROWSET(''Microsoft.Jet.OLEDB.4.0'',''Excel 8.0;Database=c:\Username and passwords v1.1.xls'',''SELECT * FROM [staff login details$]'')

version info from live:

7 FileDescription SQL Server Windows NT - 64 Bit
8 FileVersion 2005.090.2153.00

Friday, March 30, 2012

Migrating DTS packages from SQL2000 to SQL2005

Migrating DTS packages from SQL2000 to SQL2005

Migrating DTS packages from SQL2000 to SQL2005

Wednesday, March 28, 2012

Migrating db's from 2000 to 2005 results in truncated columns?

Migrating database table data from 2005 to 2000

Migrating Data from MySQL

Monday, March 26, 2012

Migrating AS2000 to AS2005 on two seperate machines

Migrating AS2000 to AS2005 on two seperate machines

Friday, March 23, 2012

Migrate SQL2005 from Standard to Enterprise edition

Migrate SQL2005 from Standard to Enterprise edition

Migrate SQL2005 from Standard to Enterprise edition

Wednesday, March 21, 2012

migrate objects between SQL2005

Migrate MSExcel worksheet sources to SQL2005

Monday, March 12, 2012

Migrate database from SQL2005 to SQL 2000 (or MSDE)

Migrate database from SQL2005 to SQL 2000 (or MSDE)

Migrate database from SQL2005 to SQL 2000 (or MSDE)

Migrate data from Oracle to SQL2005 64-bit

Migrate data from Oracle to SQL2005 64-bit

Wednesday, March 7, 2012

Microsoft.Jet.OLEDB.4.0 has not been registered. ?

Microsoft.Jet.OLEDB.4.0 has not been registered. ?

SQL Server Management Studio

Blog Archive

About Me