migrating from crystal report 8.5 to 10.0 using vb .

I am working in migrating my cr application to 10th ver from the existing 8.5 where we have to explicitly make a query in query builder and then attach it. I was using dsn in ms odbc for oracle driver to connect the DB. Now in 10.0 i have removed the query file created using 8.5 query builder and trying to write directly to command editor. the report as stand alone is working fine. but when i try to generate the pdf using my vb application then on .export option it is giving error as "Logon failed.
Details: 01S00:[Microsoft][ODBC driver for Oracle]Invalid connection string attribute". i think the problem might be with cddb_oracle.dll or crdb_oracle.dll file as i am using a evaluation version of crystal report 10. as input to dsn i am providing
1.dsn
2.usid
3.database
4.password
what else is missing . plz help....The next is code I use in VB6 to display in CRViewer10 a CR10 report that read data thru ODBC

Set CRReport = CRApplication.OpenReport("Report.rpt", 1)
For MEnt2 = 1 To CRReport.Database.Tables.Count
Set CRTabla = CRReport.Database.Tables(MEnt2)
Set CRConProp = CRTabla.ConnectionProperties("Provider")
CRConProp.value = "MSDASQL"
Set CRConProp = CRTabla.ConnectionProperties("Data Source")
CRConProp.value = "DSNname"
Set CRConProp = CRTabla.ConnectionProperties("Initial Catalog")
CRConProp.value = "Datapath"
Set CRConProp = CRTabla.ConnectionProperties("User ID")
CRConProp.value = ""
Set CRConProp = CRTabla.ConnectionProperties("Locale Identifier")
CRConProp.value = "2058"
Set CRConProp = CRTabla.ConnectionProperties("OLE DB Services")
CRConProp.value = "-5"
Next MEnt2

frmReport.Show vbModal

Migrating from Access 2000 to SQL Server

Hey All,
Migrating from Access 2000 to SQL Server 6.5 and am experiencing some difficulty...Using the database utilities -> wizard, use existing database, have File DSN created on Server, select it and the login appears. Enter the login and get error message:

"Reserved error (-1038); there is no message for this error"

I cannot locate any info on. If someone knows anything I would really appreciate your input.

Thanks,
soniaI thought I would add some info for you...

Now, normally when you specify the DSN (which is on a network) it prompts you for the user login but when I am in the wizard I didn't get the prompt, I had to actually use windows explorer, go to the correct server and when I selected it there I get the prompt, and I enter the correct user name/password and then the share folders appear. After I did that, the shared folders appear for me when using the wizard.

I located the error meaning in the reserved error refernces: JET_errBufferTooSmall -1038 Buffer is too small. I don't know what this means I should do... If someone knows anything I would really appreciate your input.

Thanks, Desperately hoping someone knows something
Ssql

Migrating Data from SQL Express to SQL Server 2005

Is it possible migrate a database from SQL Express to existing SQL
Server 2005? It is a encrypted DB. We are reaching the 4GB limit on
Express, and would like to move the Data to a existing SQL Server
2005.
Thanks
saqib
http://www.quantumcrypto.de/dante/Saqib,
The SQL Express database is fully a SQL Server 2005 database. You can
restore a backup of the database to your existing SQL Server 2005 server
with no problem.
Regarding the issues with moving an encrypted database, you might find help
on Laurentiu Cristofor's blog.
http://blogs.msdn.com/lcris/
RLF
"Saqib Ali" <docbook.xml@.gmail.com> wrote in message
news:1efb23d4-b637-4114-a64c-2703c297c9a6@.b40g2000prf.googlegroups.com...
> Is it possible migrate a database from SQL Express to existing SQL
> Server 2005? It is a encrypted DB. We are reaching the 4GB limit on
> Express, and would like to move the Data to a existing SQL Server
> 2005.
> Thanks
> saqib
> http://www.quantumcrypto.de/dante/|||The beauty of using SQL Server 2005 Express is that you can move it to a
full-blown SQL Server 2005 instance with ease- attach/detach, backup/restore
or edition upgrade. In your case, an edition upgrade would be necessary as
you need to have your keys available for the encrypted databases
"Saqib Ali" <docbook.xml@.gmail.com> wrote in message
news:1efb23d4-b637-4114-a64c-2703c297c9a6@.b40g2000prf.googlegroups.com...
> Is it possible migrate a database from SQL Express to existing SQL
> Server 2005? It is a encrypted DB. We are reaching the 4GB limit on
> Express, and would like to move the Data to a existing SQL Server
> 2005.
> Thanks
> saqib
> http://www.quantumcrypto.de/dante/|||> In your case, an edition upgrade would be necessary as
> you need to have your keys available for the encrypted databases
Thank y'all for the quick response. Can you tell what a "edition
upgrade" is? And what does it in entail?
thnx
saqib
http://www.quantumcrypto.de/dante/

Migrating Data from SQL Express to SQL Server 2005

Is it possible migrate a database from SQL Express to existing SQL
Server 2005? It is a encrypted DB. We are reaching the 4GB limit on
Express, and would like to move the Data to a existing SQL Server
2005.
Thanks
saqib
http://www.quantumcrypto.de/dante/
Saqib,
The SQL Express database is fully a SQL Server 2005 database. You can
restore a backup of the database to your existing SQL Server 2005 server
with no problem.
Regarding the issues with moving an encrypted database, you might find help
on Laurentiu Cristofor's blog.
http://blogs.msdn.com/lcris/
RLF
"Saqib Ali" <docbook.xml@.gmail.com> wrote in message
news:1efb23d4-b637-4114-a64c-2703c297c9a6@.b40g2000prf.googlegroups.com...
> Is it possible migrate a database from SQL Express to existing SQL
> Server 2005? It is a encrypted DB. We are reaching the 4GB limit on
> Express, and would like to move the Data to a existing SQL Server
> 2005.
> Thanks
> saqib
> http://www.quantumcrypto.de/dante/
|||The beauty of using SQL Server 2005 Express is that you can move it to a
full-blown SQL Server 2005 instance with ease- attach/detach, backup/restore
or edition upgrade. In your case, an edition upgrade would be necessary as
you need to have your keys available for the encrypted databases
"Saqib Ali" <docbook.xml@.gmail.com> wrote in message
news:1efb23d4-b637-4114-a64c-2703c297c9a6@.b40g2000prf.googlegroups.com...
> Is it possible migrate a database from SQL Express to existing SQL
> Server 2005? It is a encrypted DB. We are reaching the 4GB limit on
> Express, and would like to move the Data to a existing SQL Server
> 2005.
> Thanks
> saqib
> http://www.quantumcrypto.de/dante/
|||> In your case, an edition upgrade would be necessary as
> you need to have your keys available for the encrypted databases
Thank y'all for the quick response. Can you tell what a "edition
upgrade" is? And what does it in entail?
thnx
saqib
http://www.quantumcrypto.de/dante/

Migrating Data from SQL Express to SQL Server 2005

Is it possible migrate a database from SQL Express to existing SQL
Server 2005? It is a encrypted DB. We are reaching the 4GB limit on
Express, and would like to move the Data to a existing SQL Server
2005.
Thanks
saqib
http://www.quantumcrypto.de/dante/
Saqib,
The SQL Express database is fully a SQL Server 2005 database. You can
restore a backup of the database to your existing SQL Server 2005 server
with no problem.
Regarding the issues with moving an encrypted database, you might find help
on Laurentiu Cristofor's blog.
http://blogs.msdn.com/lcris/
RLF
"Saqib Ali" <docbook.xml@.gmail.com> wrote in message
news:1efb23d4-b637-4114-a64c-2703c297c9a6@.b40g2000prf.googlegroups.com...
> Is it possible migrate a database from SQL Express to existing SQL
> Server 2005? It is a encrypted DB. We are reaching the 4GB limit on
> Express, and would like to move the Data to a existing SQL Server
> 2005.
> Thanks
> saqib
> http://www.quantumcrypto.de/dante/
|||The beauty of using SQL Server 2005 Express is that you can move it to a
full-blown SQL Server 2005 instance with ease- attach/detach, backup/restore
or edition upgrade. In your case, an edition upgrade would be necessary as
you need to have your keys available for the encrypted databases
"Saqib Ali" <docbook.xml@.gmail.com> wrote in message
news:1efb23d4-b637-4114-a64c-2703c297c9a6@.b40g2000prf.googlegroups.com...
> Is it possible migrate a database from SQL Express to existing SQL
> Server 2005? It is a encrypted DB. We are reaching the 4GB limit on
> Express, and would like to move the Data to a existing SQL Server
> 2005.
> Thanks
> saqib
> http://www.quantumcrypto.de/dante/
|||> In your case, an edition upgrade would be necessary as
> you need to have your keys available for the encrypted databases
Thank y'all for the quick response. Can you tell what a "edition
upgrade" is? And what does it in entail?
thnx
saqib
http://www.quantumcrypto.de/dante/

migrate users

How can I script out existing SQL users from a user database on Production s
erver to the same user databse migrated to Test server ? (Both srv are on w2
k, sql2000)
When I migrate the user database to Test server, I accidentally deleted all
the SQL users for that database on the Test server.
I hve looked at these KB, but not sure if the "logins transfer" will removed
the existing logins or any impact on the Production server,
http://support.microsoft.com/default.aspx?kbid=298897
http://support.microsoft.com/default.aspx?kbid=246133
http://support.microsoft.com/default.aspx?kbid=240872
pls helpHi,
You can script the users and associated roles for that user using the SQL
Server ENterprise manager "Generate SQL script"
1. Open Enterprise manager and connect to the SQL server where your actual
database resides.
2. Expand the datbases and select the database.
3. Right click above the database and choose All tasks and select "Generate
SQL Scripts"
4. Go to Options tab in the new window displayed
5. Check the option "Script database users and database roles"
6. Go back to "General Tab"
7. CLick Preview.. This will display you the database users and roles
assigned
8. copy the script and paste in to a notepad
9. Login to TEST SQL servers Query analyzer using 'SA'
10. Go to the database you have dropped the users
11. copy the notepad contents and paste it in Query analyzer
12. Execute the script... Ensure that you are in correct database.
This will create all the users back with correct previlages.
FYI, I have never tested this steps before.
Thanks
Hari
MCDBA
"pk" <pk@.discussions.microsoft.com> wrote in message
news:AB82B609-55E7-4D10-9344-4ACC87721FA6@.microsoft.com...
> How can I script out existing SQL users from a user database on Production
server to the same user databse migrated to Test server ? (Both srv are on
w2k, sql2000)
> When I migrate the user database to Test server, I accidentally deleted
all the SQL users for that database on the Test server.
> I hve looked at these KB, but not sure if the "logins transfer" will
removed the existing logins or any impact on the Production server,
> http://support.microsoft.com/default.aspx?kbid=298897
> http://support.microsoft.com/default.aspx?kbid=246133
> http://support.microsoft.com/default.aspx?kbid=240872
>
> pls help

migrate users

How can I script out existing SQL users from a user database on Production server to the same user databse migrated to Test server ? (Both srv are on w2k, sql2000)
When I migrate the user database to Test server, I accidentally deleted all the SQL users for that database on the Test server.
I hve looked at these KB, but not sure if the "logins transfer" will removed the existing logins or any impact on the Production server,
http://support.microsoft.com/default.aspx?kbid=298897
http://support.microsoft.com/default.aspx?kbid=246133
http://support.microsoft.com/default.aspx?kbid=240872
pls help
Hi,
You can script the users and associated roles for that user using the SQL
Server ENterprise manager "Generate SQL script"
1. Open Enterprise manager and connect to the SQL server where your actual
database resides.
2. Expand the datbases and select the database.
3. Right click above the database and choose All tasks and select "Generate
SQL Scripts"
4. Go to Options tab in the new window displayed
5. Check the option "Script database users and database roles"
6. Go back to "General Tab"
7. CLick Preview.. This will display you the database users and roles
assigned
8. copy the script and paste in to a notepad
9. Login to TEST SQL servers Query analyzer using 'SA'
10. Go to the database you have dropped the users
11. copy the notepad contents and paste it in Query analyzer
12. Execute the script... Ensure that you are in correct database.
This will create all the users back with correct previlages.
FYI, I have never tested this steps before.
Thanks
Hari
MCDBA
"pk" <pk@.discussions.microsoft.com> wrote in message
news:AB82B609-55E7-4D10-9344-4ACC87721FA6@.microsoft.com...
> How can I script out existing SQL users from a user database on Production
server to the same user databse migrated to Test server ? (Both srv are on
w2k, sql2000)
> When I migrate the user database to Test server, I accidentally deleted
all the SQL users for that database on the Test server.
> I hve looked at these KB, but not sure if the "logins transfer" will
removed the existing logins or any impact on the Production server,
> http://support.microsoft.com/default.aspx?kbid=298897
> http://support.microsoft.com/default.aspx?kbid=246133
> http://support.microsoft.com/default.aspx?kbid=240872
>
> pls help
sql

migrate users

How can I script out existing SQL users from a user database on Production server to the same user databse migrated to Test server ? (Both srv are on w2k, sql2000)
When I migrate the user database to Test server, I accidentally deleted all the SQL users for that database on the Test server.
I hve looked at these KB, but not sure if the "logins transfer" will removed the existing logins or any impact on the Production server,
http://support.microsoft.com/default.aspx?kbid=298897
http://support.microsoft.com/default.aspx?kbid=246133
http://support.microsoft.com/default.aspx?kbid=240872
pls helpHi,
You can script the users and associated roles for that user using the SQL
Server ENterprise manager "Generate SQL script"
1. Open Enterprise manager and connect to the SQL server where your actual
database resides.
2. Expand the datbases and select the database.
3. Right click above the database and choose All tasks and select "Generate
SQL Scripts"
4. Go to Options tab in the new window displayed
5. Check the option "Script database users and database roles"
6. Go back to "General Tab"
7. CLick Preview.. This will display you the database users and roles
assigned
8. copy the script and paste in to a notepad
9. Login to TEST SQL servers Query analyzer using 'SA'
10. Go to the database you have dropped the users
11. copy the notepad contents and paste it in Query analyzer
12. Execute the script... Ensure that you are in correct database.
This will create all the users back with correct previlages.
FYI, I have never tested this steps before.
--
Thanks
Hari
MCDBA
"pk" <pk@.discussions.microsoft.com> wrote in message
news:AB82B609-55E7-4D10-9344-4ACC87721FA6@.microsoft.com...
> How can I script out existing SQL users from a user database on Production
server to the same user databse migrated to Test server ? (Both srv are on
w2k, sql2000)
> When I migrate the user database to Test server, I accidentally deleted
all the SQL users for that database on the Test server.
> I hve looked at these KB, but not sure if the "logins transfer" will
removed the existing logins or any impact on the Production server,
> http://support.microsoft.com/default.aspx?kbid=298897
> http://support.microsoft.com/default.aspx?kbid=246133
> http://support.microsoft.com/default.aspx?kbid=240872
>
> pls help

Migrate to New Domain

I migrated my SQL 7 server running on Win 2K Server from
the existing domain to a new domain using the Active
Directory Migration tool but now SQL won't start and I
cannot get it to start whether I log on to the old or new
domains. Does anyone have an insight?Wht error do yo get? I guess SQL Server service can't logo to Windows
domain. Check te username and password SQL Server service is using.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Kevin" <anonymous@.discussions.microsoft.com> wrote in message
news:54af01c42cdd$7a56a5f0$a101280a@.phx.gbl...
> I migrated my SQL 7 server running on Win 2K Server from
> the existing domain to a new domain using the Active
> Directory Migration tool but now SQL won't start and I
> cannot get it to start whether I log on to the old or new
> domains. Does anyone have an insight?

Migrate to New Domain

I migrated my SQL 7 server running on Win 2K Server from
the existing domain to a new domain using the Active
Directory Migration tool but now SQL won't start and I
cannot get it to start whether I log on to the old or new
domains. Does anyone have an insight?
Wht error do yo get? I guess SQL Server service can't logo to Windows
domain. Check te username and password SQL Server service is using.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Kevin" <anonymous@.discussions.microsoft.com> wrote in message
news:54af01c42cdd$7a56a5f0$a101280a@.phx.gbl...
> I migrated my SQL 7 server running on Win 2K Server from
> the existing domain to a new domain using the Active
> Directory Migration tool but now SQL won't start and I
> cannot get it to start whether I log on to the old or new
> domains. Does anyone have an insight?
sql

Migrate to New Domain

I migrated my SQL 7 server running on Win 2K Server from
the existing domain to a new domain using the Active
Directory Migration tool but now SQL won't start and I
cannot get it to start whether I log on to the old or new
domains. Does anyone have an insight?Wht error do yo get? I guess SQL Server service can't logo to Windows
domain. Check te username and password SQL Server service is using.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Kevin" <anonymous@.discussions.microsoft.com> wrote in message
news:54af01c42cdd$7a56a5f0$a101280a@.phx.gbl...
> I migrated my SQL 7 server running on Win 2K Server from
> the existing domain to a new domain using the Active
> Directory Migration tool but now SQL won't start and I
> cannot get it to start whether I log on to the old or new
> domains. Does anyone have an insight?

Migrate Roles

Hi,
I need to migrate all databases from one server to another
existing database server, at this time i know how to
migrate all users logins avoiding orphaned users but i
dont know how to migrate all existing roles and how to
assign logins to existing Server Roles on the destination
with the minimum effort.
Best regardsHi,
As soon as you transfer the syslogins table the server wide fixed roles also
will be transferred.
Have a look into the below link , This script will provide a easy method to
quickly generate a script that will move all logins along with same id and
password from one server to other.
http://www.databasejournal.com/features/mssql/article.php/2228611
--
Thanks
Hari
MCDBA
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:22d9501c45dd8$18b37630$a401280a@.phx.gbl...
> Hi,
> I need to migrate all databases from one server to another
> existing database server, at this time i know how to
> migrate all users logins avoiding orphaned users but i
> dont know how to migrate all existing roles and how to
> assign logins to existing Server Roles on the destination
> with the minimum effort.
> Best regards|||Hi Hari,
I tried and the server roles were migrated to the new
server but the roles appear with no members. The users
that belong to any existing server roles do not belong to
the destination server roles too.
I think that i must use the sp_addrolemember to assign the
users migrated to the corresponding database roles
Best regards
>--Original Message--
>Hi,
>As soon as you transfer the syslogins table the server
wide fixed roles also
>will be transferred.
>Have a look into the below link , This script will
provide a easy method to
>quickly generate a script that will move all logins along
with same id and
>password from one server to other.
>
>http://www.databasejournal.com/features/mssql/article.php/
2228611
>--
>Thanks
>Hari
>MCDBA
>"CC&JM" <anonymous@.discussions.microsoft.com> wrote in
message
>news:22d9501c45dd8$18b37630$a401280a@.phx.gbl...
>> Hi,
>> I need to migrate all databases from one server to
another
>> existing database server, at this time i know how to
>> migrate all users logins avoiding orphaned users but i
>> dont know how to migrate all existing roles and how to
>> assign logins to existing Server Roles on the
destination
>> with the minimum effort.
>> Best regards
>
>.
>|||HI,
After migration, Can you execute the below command:-
select * from syslogins
and see the below column values:-
sysadmin int 1, if login is a member of the sysadmin server role.
securityadmin int 1, if login is a member of the securityadmin server
role.
serveradmin int 1, if login is a member of the serveradmin fixed
server role.
setupadmin int 1, if login is a member of the setupadmin fixed server
role.
processadmin int 1, if login is a member of the processadmin fixed
server role.
diskadmin int 1, if login is a member of the diskadmin fixed server
role.
dbcreator int 1, if login is a member of the dbcreator fixed server
role.
If you have the value 1 for the column then the role is transfered from
source server to destination.
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:2269701c45de4$91a25c80$a601280a@.phx.gbl...
> Hi Hari,
> I tried and the server roles were migrated to the new
> server but the roles appear with no members. The users
> that belong to any existing server roles do not belong to
> the destination server roles too.
> I think that i must use the sp_addrolemember to assign the
> users migrated to the corresponding database roles
> Best regards
> >--Original Message--
> >Hi,
> >
> >As soon as you transfer the syslogins table the server
> wide fixed roles also
> >will be transferred.
> >
> >Have a look into the below link , This script will
> provide a easy method to
> >quickly generate a script that will move all logins along
> with same id and
> >password from one server to other.
> >
> >
> >http://www.databasejournal.com/features/mssql/article.php/
> 2228611
> >
> >--
> >Thanks
> >Hari
> >MCDBA
> >
> >"CC&JM" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:22d9501c45dd8$18b37630$a401280a@.phx.gbl...
> >> Hi,
> >>
> >> I need to migrate all databases from one server to
> another
> >> existing database server, at this time i know how to
> >> migrate all users logins avoiding orphaned users but i
> >> dont know how to migrate all existing roles and how to
> >> assign logins to existing Server Roles on the
> destination
> >> with the minimum effort.
> >>
> >> Best regards
> >
> >
> >.
> >

Migrate Jobs, DTS and Alerts

Hello,
I need to migrate all my databases to another database
server, can you tell me how can i migrate all the existing
Jobs, DTS's and Alerts sucefully from one server to
another with the minimum effort?
The scheduled DTS's will function on the destination
server?
Thanks,
Best regardsI just went through this. I migrated all my packages using SQL_DMO. I
wrote some code that processed through each DTS package using the DTS
Package Object. The processing I did was to change connection strings, or
any references to server specific stuff, and then saved them onto the new
servers. Did a similar things with the SQL Agent Jobs, and Alerts.
--
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:2478201c45f79$57739290$a501280a@.phx.gbl...
> Hello,
> I need to migrate all my databases to another database
> server, can you tell me how can i migrate all the existing
> Jobs, DTS's and Alerts sucefully from one server to
> another with the minimum effort?
> The scheduled DTS's will function on the destination
> server?
> Thanks,
> Best regards
>sql

Migrate form stand alone to clustered server

Here is the scenario:
We have an existing production non clustered SQL 2000 server instance that we need to migrate to a new clustered SQL 2000 server instance. We need to accomplish this without affecting the FQDN that applications use to call this server. I found this article on a solution to rename the server after an xcopy of the entire db structure. Here is the link http://vyaskn.tripod.com/moving_sql_server.htm. The other issue that we are trying to resolve is the time it takes for the snapshots of replication to run (in our case almost a full day). That is why this approach looked like it may be a good solution for us.

Here is the question:
Is it possible to move our existing database to a new clustered environment without having to change the FQDN that other applications use to access this database and without having to reinitialize replication?GrantAsh,

The link you posted could work. But, the problem is in the drive letters and the folders.

The problem is that for a clustered server the data drives need to be shared in the cluster. The concern that I would have is the drive letters that you used for your current SQL server would not match the Clustered SQL server drives.

But, if you can match the drive letters then copying the data is not a problem.

But I can't stress this enough, using the method described on that web page to change the SQL server name will not work for a Clustered SQL Server.

I would suggest reading the following:
http://support.microsoft.com/kb/244980/
http://www.sql-server-performance.com/clustering_2000.asp

bEH

Migrate existing standalone to cluster

While away on vacation my company had some software installed that required a
new instance of SQL Server 2K to be created on our existing active/passive
cluster.
Because the techs doing the install did not know the password for our domain
cluster user account they created the standalone instance on the db server.
What I need to know is how do I go about migrating it to a clustered instance
instead of a standalone so as to take advantage of the failover capabilities?
i.e. I already have a clustered server with one clustered instance. They
installed a standalone instance alongside and now I need to migrate the new
instance to another named clustered instance.
Is it possible to go with the existing clustered instance and simply move
the DB's to the cluster? What's driving the need for two instances?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Cary" <Cary@.discussions.microsoft.com> wrote in message
news:F9743B37-FC4D-4909-A4CA-608078BB5A3E@.microsoft.com...
While away on vacation my company had some software installed that required
a
new instance of SQL Server 2K to be created on our existing active/passive
cluster.
Because the techs doing the install did not know the password for our domain
cluster user account they created the standalone instance on the db server.
What I need to know is how do I go about migrating it to a clustered
instance
instead of a standalone so as to take advantage of the failover
capabilities?
i.e. I already have a clustered server with one clustered instance. They
installed a standalone instance alongside and now I need to migrate the new
instance to another named clustered instance.
|||Oh you'll love this...
The software we purchased for our new document management system *cough*
Documentum *cough*, is designed so as to require a case-sensitive database.
I know...D-U-M Dum...And because all of our other databases are NOT
case-sensitive (and there's no way in h*ll I would change that) we had to
create a new instance that was.
"Tom Moreau" wrote:

> Is it possible to go with the existing clustered instance and simply move
> the DB's to the cluster? What's driving the need for two instances?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Cary" <Cary@.discussions.microsoft.com> wrote in message
> news:F9743B37-FC4D-4909-A4CA-608078BB5A3E@.microsoft.com...
> While away on vacation my company had some software installed that required
> a
> new instance of SQL Server 2K to be created on our existing active/passive
> cluster.
> Because the techs doing the install did not know the password for our domain
> cluster user account they created the standalone instance on the db server.
> What I need to know is how do I go about migrating it to a clustered
> instance
> instead of a standalone so as to take advantage of the failover
> capabilities?
> i.e. I already have a clustered server with one clustered instance. They
> installed a standalone instance alongside and now I need to migrate the new
> instance to another named clustered instance.
>
|||That's not justification enough. You can create a case-sensitive database
within an instance that is not case sensitive.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Cary" <Cary@.discussions.microsoft.com> wrote in message
news:A8F1525E-3D96-4842-AFBD-87160EC34CB8@.microsoft.com...
Oh you'll love this...
The software we purchased for our new document management system *cough*
Documentum *cough*, is designed so as to require a case-sensitive database.
I know...D-U-M Dum...And because all of our other databases are NOT
case-sensitive (and there's no way in h*ll I would change that) we had to
create a new instance that was.
"Tom Moreau" wrote:

> Is it possible to go with the existing clustered instance and simply move
> the DB's to the cluster? What's driving the need for two instances?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Cary" <Cary@.discussions.microsoft.com> wrote in message
> news:F9743B37-FC4D-4909-A4CA-608078BB5A3E@.microsoft.com...
> While away on vacation my company had some software installed that
> required
> a
> new instance of SQL Server 2K to be created on our existing active/passive
> cluster.
> Because the techs doing the install did not know the password for our
> domain
> cluster user account they created the standalone instance on the db
> server.
> What I need to know is how do I go about migrating it to a clustered
> instance
> instead of a standalone so as to take advantage of the failover
> capabilities?
> i.e. I already have a clustered server with one clustered instance. They
> installed a standalone instance alongside and now I need to migrate the
> new
> instance to another named clustered instance.
>
|||Not that it will matter much anyway, since it is already installed, but how
do you go about making a case-sensitive db inside of an insensitive instance?
And I still need to know how to change the standalone to a clustered...
"Tom Moreau" wrote:

> That's not justification enough. You can create a case-sensitive database
> within an instance that is not case sensitive.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Cary" <Cary@.discussions.microsoft.com> wrote in message
> news:A8F1525E-3D96-4842-AFBD-87160EC34CB8@.microsoft.com...
> Oh you'll love this...
> The software we purchased for our new document management system *cough*
> Documentum *cough*, is designed so as to require a case-sensitive database.
> I know...D-U-M Dum...And because all of our other databases are NOT
> case-sensitive (and there's no way in h*ll I would change that) we had to
> create a new instance that was.
> "Tom Moreau" wrote:
>
>
|||To create a database with a case-sensitive collation, just use the COLLATE
option:
create database MyDB
collate Latin1_General_CS_AI
As for the other bit, you'll have to create the new virtual server (and
named instance) in the same manner as you created the other virtual server
and instance. However, you can specify the collation for the new instance
at that time. Once that's done, then backup and restore the DB's from the
standalone to the new instance. Finally, remove the standalone.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Cary" <Cary@.discussions.microsoft.com> wrote in message
news:FBFC5A77-4A41-4B6E-B076-370E9111321B@.microsoft.com...
Not that it will matter much anyway, since it is already installed, but how
do you go about making a case-sensitive db inside of an insensitive
instance?
And I still need to know how to change the standalone to a clustered...
"Tom Moreau" wrote:

> That's not justification enough. You can create a case-sensitive database
> within an instance that is not case sensitive.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Cary" <Cary@.discussions.microsoft.com> wrote in message
> news:A8F1525E-3D96-4842-AFBD-87160EC34CB8@.microsoft.com...
> Oh you'll love this...
> The software we purchased for our new document management system *cough*
> Documentum *cough*, is designed so as to require a case-sensitive
> database.
> I know...D-U-M Dum...And because all of our other databases are NOT
> case-sensitive (and there's no way in h*ll I would change that) we had to
> create a new instance that was.
> "Tom Moreau" wrote:
>
>
|||Creating a database in an instance with a collation that is differnt than
the default server collation, as Tom suggested, is certainly one approach
you can explore. If everything is under your control, you can make this
work. A vendor package like Ducumentum, however, may crap out becasue of the
likely collation conflict with the tempdb database. So test it out!
Linchi
"Cary" <Cary@.discussions.microsoft.com> wrote in message
news:FBFC5A77-4A41-4B6E-B076-370E9111321B@.microsoft.com...[vbcol=seagreen]
> Not that it will matter much anyway, since it is already installed, but
> how
> do you go about making a case-sensitive db inside of an insensitive
> instance?
> And I still need to know how to change the standalone to a clustered...
>
> "Tom Moreau" wrote:
|||Question regarding what Linchi wrote about the temp DB being an issue. We
are currently in the same situation with a mulitnode cluster that will house
a peoplesoft instance (different collation than the other instances) but have
concerns on how failover will happen with this different collation instance
vs the collation instances that are indentical. Will failover happen just as
if all the collations were the same or do we have to take special precautions?
"Linchi Shea" wrote:

> Creating a database in an instance with a collation that is differnt than
> the default server collation, as Tom suggested, is certainly one approach
> you can explore. If everything is under your control, you can make this
> work. A vendor package like Ducumentum, however, may crap out becasue of the
> likely collation conflict with the tempdb database. So test it out!
> Linchi
> "Cary" <Cary@.discussions.microsoft.com> wrote in message
> news:FBFC5A77-4A41-4B6E-B076-370E9111321B@.microsoft.com...
>
>
|||Multiple collations are no different on a cluster than on a stand-alone box.
Failover will work exactly the same regardless of the system or anyuser
database collation. Collations have been separated from the system code
page since SQL 7.0
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Todd" <Todd@.discussions.microsoft.com> wrote in message
news:32F54FD8-2882-4125-8202-D6CE442C83E5@.microsoft.com...[vbcol=seagreen]
> Question regarding what Linchi wrote about the temp DB being an issue. We
> are currently in the same situation with a mulitnode cluster that will
> house
> a peoplesoft instance (different collation than the other instances) but
> have
> concerns on how failover will happen with this different collation
> instance
> vs the collation instances that are indentical. Will failover happen just
> as
> if all the collations were the same or do we have to take special
> precautions?
> "Linchi Shea" wrote:

migrate existing sql database to cluster

We are in the process of putting together a Windows 2000
distributed failover cluster. We have numerous SQL 2000
servers functioning as DB servers for a few different
departments. What we would like to do is eventually
migrate theses databases off of the stand alone servers to
the clustered servers.
Few questions:
Are there any major things to look out for when migrating
the databases? Or is it basically using the migration
wizard thats built into SQL server and dumping the
databases to one of the new installs of SQL on the cluster?
What about transaction and data files? Do these need to
be migrated as well?
Anything major I should be on the lookout for?
Any documentation about this on MS site? I couldnt find
any.
TIA!
Jeff BaileyYou should read on "moving databases between servers".
One Issue that often comes is security (logins/users).
"JBailey" <abc@.123.com> wrote in message
news:096701c34afd$255562c0$a001280a@.phx.gbl...
> We are in the process of putting together a Windows 2000
> distributed failover cluster. We have numerous SQL 2000
> servers functioning as DB servers for a few different
> departments. What we would like to do is eventually
> migrate theses databases off of the stand alone servers to
> the clustered servers.
> Few questions:
> Are there any major things to look out for when migrating
> the databases? Or is it basically using the migration
> wizard thats built into SQL server and dumping the
> databases to one of the new installs of SQL on the cluster?
> What about transaction and data files? Do these need to
> be migrated as well?
> Anything major I should be on the lookout for?
> Any documentation about this on MS site? I couldnt find
> any.
> TIA!
> Jeff Bailey
>|||Easiest way is probably to restore a backup to the other server
or detach/attach
INF: Moving SQL Server Databases to a New Location with Detach/Attach
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q224071
or use the Copy database wizard
INF: Understanding and Troubleshooting the Copy Database Wizard in SQL
Server 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q274463
Also check out
INF: How To Transfer Logins and Passwords Between SQL Servers
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q246133
PRB: User Logon and/or Permission Errors After Restoring Dump
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q168001
INF: How to Resolve Permission Issues When a Database is Moved Between SQL
Servers
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q240872
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is Incomplete
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q274188
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"JBailey" <abc@.123.com> wrote in message
news:096701c34afd$255562c0$a001280a@.phx.gbl...
We are in the process of putting together a Windows 2000
distributed failover cluster. We have numerous SQL 2000
servers functioning as DB servers for a few different
departments. What we would like to do is eventually
migrate theses databases off of the stand alone servers to
the clustered servers.
Few questions:
Are there any major things to look out for when migrating
the databases? Or is it basically using the migration
wizard thats built into SQL server and dumping the
databases to one of the new installs of SQL on the cluster?
What about transaction and data files? Do these need to
be migrated as well?
Anything major I should be on the lookout for?
Any documentation about this on MS site? I couldnt find
any.
TIA!
Jeff Bailey

Migrate DTC

Hi guys,
I have an existing sql 2k enterprise server and we're going to configure it
for server clustering. We have custom made DTC package and most of the
application use it very often.
My concern is how do we migrate this custom made DTC package to the new
environment(sql cluster)?
Appreaciate ur guys help.
Hidayat
Message posted via http://www.droptable.com
I maybe missing something; due my true lack of understanding MSDTC, but I
don't think you have anything to migrate. MSDTC as far as I know, is just a
log file, and a new install will use a new log file. This should be a walk
in the park.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
"Hidayat via droptable.com" <forum@.nospam.droptable.com> wrote in message
news:4FE03924D8C20@.droptable.com...
> Hi guys,
> I have an existing sql 2k enterprise server and we're going to configure
> it
> for server clustering. We have custom made DTC package and most of the
> application use it very often.
> My concern is how do we migrate this custom made DTC package to the new
> environment(sql cluster)?
> Appreaciate ur guys help.
> Hidayat
> --
> Message posted via http://www.droptable.com
|||tks for your prompt reply.
Another question i would like to ask is do we need different virtual ip for
MSDTC & SQL cluster? Can we use the existing virtual ip that we configure for
MSCS?
Tks
Message posted via http://www.droptable.com
|||If MSDTC has heavy usage then give it its own Group - with an Virtual IP,
Virtual Name, Physical Disk, and the MSDTC resource. If it is not a heavy
hitter, then don't worry about it.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
"Hidayat via droptable.com" <forum@.droptable.com> wrote in message
news:4FE4339FB56C0@.droptable.com...
> tks for your prompt reply.
> Another question i would like to ask is do we need different virtual ip
> for
> MSDTC & SQL cluster? Can we use the existing virtual ip that we configure
> for
> MSCS?
> Tks
> --
> Message posted via http://www.droptable.com
|||Can the physical disk for MSDTC be the same(sharing) for the SQL cluster
physical disk?
In SQL cluster environment, how is the procedure of restoring the database?
Is it the same as normal SQL restore using it's own utility. As i know the
data will centrally reside in the SAN(EMC) storage.
Tks
Message posted via http://www.droptable.com
|||You can share the space. But if it is heavily used that maybe a bad idea.
Everything about a database is the same, restore, attach, etc. The Books
Online are wonderful and full of great information.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
"Hidayat via droptable.com" <forum@.droptable.com> wrote in message
news:4FE89EBC9A9E0@.droptable.com...
> Can the physical disk for MSDTC be the same(sharing) for the SQL cluster
> physical disk?
> In SQL cluster environment, how is the procedure of restoring the
> database?
> Is it the same as normal SQL restore using it's own utility. As i know the
> data will centrally reside in the SAN(EMC) storage.
> Tks
> --
> Message posted via http://www.droptable.com
|||Clustered SQL servers look and act just like normal SQL servers for amost
every purpose, including backup and restore. There are some extra steps for
things like restoring master, adding disks, and adding/dropping cluster
nodes but these are well documented. From the client's point of view, they
look and act exactly like any other SQL server.
Geoff N. Hiten
Microsoft SQL Server MVP
"Hidayat via droptable.com" <forum@.droptable.com> wrote in message
news:4FE89EBC9A9E0@.droptable.com...
> Can the physical disk for MSDTC be the same(sharing) for the SQL cluster
> physical disk?
> In SQL cluster environment, how is the procedure of restoring the
> database?
> Is it the same as normal SQL restore using it's own utility. As i know the
> data will centrally reside in the SAN(EMC) storage.
> Tks
> --
> Message posted via http://www.droptable.com
|||Tks for the explaination. Just to confirm with u guys. Let's say that i have
2 node(A & B). I install and configure SQL cluster on Node A. Must i install
the SQL cluster on Node B?
Message posted via http://www.droptable.com
|||Tks a million guys. Let's say that i have 5GB each on 2 servers. Should i
enabled /3GB or /PAE or AWE? What is u guys best recommendation. I'm going to
configure clustering this Saturday and will be in production.
This clustering is new to me so tks for your patient in answering my question.
U guys have been very helpful.
Tks.
Message posted via http://www.droptable.com
|||Great question. You need to 1) talk to you hardware vendor and find out if
/PAE or /AWE are even supported. 2) test the /3GB with whatever the vendor
supports, you may not see any difference or worse, things could get slower,
3) I am guessing you will only need /PAE to see the 5 GB of memory, but this
is a guess - testing will tell all.
Lastly, you are on a very aggressive schedule. It sounds like you need more
testing time to me BEFORE you go live. This being your first cluster, can
you restore it or a node in the case of a failure? Do you fully understand
how to handle service packs, etc. I am not trying to beat you up, you have a
learning curve ahead. After you in production is really not the way to
manage and maintain your Highly Available SQL Failover Cluster.
Just my two cents...
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
"Hidayat via droptable.com" <forum@.droptable.com> wrote in message
news:4FF0A99441520@.droptable.com...
> Tks a million guys. Let's say that i have 5GB each on 2 servers. Should i
> enabled /3GB or /PAE or AWE? What is u guys best recommendation. I'm going
> to
> configure clustering this Saturday and will be in production.
> This clustering is new to me so tks for your patient in answering my
> question.
>
> U guys have been very helpful.
> Tks.
> --
> Message posted via http://www.droptable.com

Migrate AS2005 Cube to New Version of Source DB

Is it possible -- and how straightforward is it -- to migrate an existing AS2005 Cube (and/or at least it's dimensions) to an updated version of my source DB (SQL 2005)? I had little choice but to establish a "dev-and-test" version of the source DB during enhancements that coincided with production analysis and reporting. Now that I've approved the "dev-and-test" version, I want to make it our production master for OLAP.

As a note, I don't believe that any of the fields used in the cube have been modified. We've just added some new calculated fields (and sp's).

I have little idea of whether this will be simple, hard or impossible. I'm planning to try, but wanted expert feedback first.

There is a feature in BI Dev Studio specifically designed for the scenario you describe.

Open up your DSV and right click on the empty space anywhere. Select a "Refresh" option.

At this moment BI Dev Studio connects to the relational database and verifies if all the tables and all the coluns you build your Analysis Services objects upon are there. If it detects any changes in the relational database it will give you the list of the objects and will ask you if you would like that BI Dev studio will fix them for you automatically.
If the case is simple, just go ahead. If you see lots of changes, you save the list and try to takle every problem separately.

Hope that helps.

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

|||

Yes, the DSV refresh will help. However, just to clarify my situation...

I need to disconnect an existing cube away from it's source DB and connect it to a new database, (which is a modified, renamed copy of the original), not just refresh the DSV connection after some mods.

Two questions:

(1) In light of my situation,then prior to following your guidance above, would it work for me to (1st b/u everything, then) restore the new database into/overwriting the old database?

(2) Is there a better way involving DB file renaming, etc.? (Specifically, I'm looking for alternatives to re-building my cube and/or dimensions.)

I think I'm half way to resolving this problem. Thank you, Edward!

|||

Again, DSV refresh not only going to synchronize your DSV with relational database, it also checks and changes properties of attributes and measures. You should try it to see what it does for you and if it works.

Make a copy of your database and try your experiments on the copy.

You can also make backup of your database and then resore it with different name.

You can script your database Create script and modify the script to change the database name and ID.

You have quite a few options here. I suggest you just try and few and see what works.

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

|||

Thanks Edward. Your replies are illuminating and helpful.

In light of a new SSIS package connected to the new "dev-and-test" db, I'd like to inquire about simply changing the data source for an existing AS2005 cube, but will start a new thread on that subject.