Hello all,
I got a application which is developed using VB6.0 as front end and
MS-Access as backend. Now i would like to change the database from MS-Access
to MS-SQLserver.
How do I change the databse from MS-Access to MS-SQLServer?
Regards
JackAnswered in .newusers
Please keep your posts to one newsgreoup. What you want to do is well
documented in a few thousand different pages all over the internet
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.expertsrt.com - not your average tech Q&A site
"Jack" <Jack@.discussions.microsoft.com> wrote in message
news:427EBA98-380A-42EC-A3C5-47097790D9F9@.microsoft.com...
> Hello all,
> I got a application which is developed using VB6.0 as front end and
> MS-Access as backend. Now i would like to change the database from
> MS-Access
> to MS-SQLserver.
> How do I change the databse from MS-Access to MS-SQLServer?
> Regards
> Jack|||MS Access 2000 Migration Guide
http://www.microsoft.com/technet/pr...
/acssmgde.mspx
After porting over the tables and data, read up on the techniques for
optimizing a SQL Server application:
http://msdn.microsoft.com/library/d...
etHowTo03.asp
http://msdn.microsoft.com/library/d...
ethowto04.asp
http://msdn.microsoft.com/SQL/2000/...rf/default.aspx
"Jack" <Jack@.discussions.microsoft.com> wrote in message
news:427EBA98-380A-42EC-A3C5-47097790D9F9@.microsoft.com...
> Hello all,
> I got a application which is developed using VB6.0 as front end and
> MS-Access as backend. Now i would like to change the database from
> MS-Access
> to MS-SQLserver.
> How do I change the databse from MS-Access to MS-SQLServer?
> Regards
> Jack
Showing posts with label developed. Show all posts
Showing posts with label developed. Show all posts
Thursday, March 22, 2012
Changing the database from MSAccess to MSSQLServer.
Hello all,
I got a application which is developed using VB6.0 as front end and
MS-Access as backend. Now i would like to change the database from MS-Access
to MS-SQLserver.
How do I change the databse from MS-Access to MS-SQLServer?
Regards
Jack
see the response in .newusers
Please only post the same question to one group...
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.expertsrt.com - not your average tech Q&A site
"Jack" <Jack@.discussions.microsoft.com> wrote in message
news:4C0633A4-44A2-402B-8C6B-91A646D8B988@.microsoft.com...
> Hello all,
> I got a application which is developed using VB6.0 as front end and
> MS-Access as backend. Now i would like to change the database from
> MS-Access
> to MS-SQLserver.
> How do I change the databse from MS-Access to MS-SQLServer?
> Regards
> Jack
sql
I got a application which is developed using VB6.0 as front end and
MS-Access as backend. Now i would like to change the database from MS-Access
to MS-SQLserver.
How do I change the databse from MS-Access to MS-SQLServer?
Regards
Jack
see the response in .newusers
Please only post the same question to one group...
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.expertsrt.com - not your average tech Q&A site
"Jack" <Jack@.discussions.microsoft.com> wrote in message
news:4C0633A4-44A2-402B-8C6B-91A646D8B988@.microsoft.com...
> Hello all,
> I got a application which is developed using VB6.0 as front end and
> MS-Access as backend. Now i would like to change the database from
> MS-Access
> to MS-SQLserver.
> How do I change the databse from MS-Access to MS-SQLServer?
> Regards
> Jack
sql
Changing the database from MSAccess to MSSQLServer.
Hello all,
I got a application which is developed using VB6.0 as front end and
MS-Access as backend. Now i would like to change the database from MS-Access
to MS-SQLserver.
How do I change the databse from MS-Access to MS-SQLServer?
Regards
Jack
Hi Jack
You don't say which version of SQL Server you wish to upgrade to?
The guys in the Access newsgroup tend to have their own opinons regarding
the Access upgrade wizard so you may want to ask in there!
The upgrade wizard may provide enough to upgrade your database but then you
should look at tuning and re-writing the code so that it is more compatible
with SQL server, such as choosing more appropriate data types etc.
As an alternative you can do this manually and piecemeal using the Import
Wizard in SQL server (i.e DTS/SSIS).
Before you try anything make sure that you have a recoverable backup. It
will be worthwhile honing the upgrade on a separate system before attempting
anything on the live database.
John
"Jack" wrote:
> Hello all,
> I got a application which is developed using VB6.0 as front end and
> MS-Access as backend. Now i would like to change the database from MS-Access
> to MS-SQLserver.
> How do I change the databse from MS-Access to MS-SQLServer?
> Regards
> Jack
I got a application which is developed using VB6.0 as front end and
MS-Access as backend. Now i would like to change the database from MS-Access
to MS-SQLserver.
How do I change the databse from MS-Access to MS-SQLServer?
Regards
Jack
Hi Jack
You don't say which version of SQL Server you wish to upgrade to?
The guys in the Access newsgroup tend to have their own opinons regarding
the Access upgrade wizard so you may want to ask in there!
The upgrade wizard may provide enough to upgrade your database but then you
should look at tuning and re-writing the code so that it is more compatible
with SQL server, such as choosing more appropriate data types etc.
As an alternative you can do this manually and piecemeal using the Import
Wizard in SQL server (i.e DTS/SSIS).
Before you try anything make sure that you have a recoverable backup. It
will be worthwhile honing the upgrade on a separate system before attempting
anything on the live database.
John
"Jack" wrote:
> Hello all,
> I got a application which is developed using VB6.0 as front end and
> MS-Access as backend. Now i would like to change the database from MS-Access
> to MS-SQLserver.
> How do I change the databse from MS-Access to MS-SQLServer?
> Regards
> Jack
Changing the database from MSAccess to MSSQLServer.
Hello all,
I got a application which is developed using VB6.0 as front end and
MS-Access as backend. Now i would like to change the database from MS-Access
to MS-SQLserver.
How do I change the databse from MS-Access to MS-SQLServer?
Regards
JackHi Jack
You don't say which version of SQL Server you wish to upgrade to?
The guys in the Access newsgroup tend to have their own opinons regarding
the Access upgrade wizard so you may want to ask in there!
The upgrade wizard may provide enough to upgrade your database but then you
should look at tuning and re-writing the code so that it is more compatible
with SQL server, such as choosing more appropriate data types etc.
As an alternative you can do this manually and piecemeal using the Import
Wizard in SQL server (i.e DTS/SSIS).
Before you try anything make sure that you have a recoverable backup. It
will be worthwhile honing the upgrade on a separate system before attempting
anything on the live database.
John
"Jack" wrote:
> Hello all,
> I got a application which is developed using VB6.0 as front end and
> MS-Access as backend. Now i would like to change the database from MS-Acce
ss
> to MS-SQLserver.
> How do I change the databse from MS-Access to MS-SQLServer?
> Regards
> Jack
I got a application which is developed using VB6.0 as front end and
MS-Access as backend. Now i would like to change the database from MS-Access
to MS-SQLserver.
How do I change the databse from MS-Access to MS-SQLServer?
Regards
JackHi Jack
You don't say which version of SQL Server you wish to upgrade to?
The guys in the Access newsgroup tend to have their own opinons regarding
the Access upgrade wizard so you may want to ask in there!
The upgrade wizard may provide enough to upgrade your database but then you
should look at tuning and re-writing the code so that it is more compatible
with SQL server, such as choosing more appropriate data types etc.
As an alternative you can do this manually and piecemeal using the Import
Wizard in SQL server (i.e DTS/SSIS).
Before you try anything make sure that you have a recoverable backup. It
will be worthwhile honing the upgrade on a separate system before attempting
anything on the live database.
John
"Jack" wrote:
> Hello all,
> I got a application which is developed using VB6.0 as front end and
> MS-Access as backend. Now i would like to change the database from MS-Acce
ss
> to MS-SQLserver.
> How do I change the databse from MS-Access to MS-SQLServer?
> Regards
> Jack
Changing the database from MSAccess to MSSQLServer.
Hello all,
I got a application which is developed using VB6.0 as front end and
MS-Access as backend. Now i would like to change the database from MS-Access
to MS-SQLserver.
How do I change the databse from MS-Access to MS-SQLServer?
Regards
JackHi Jack
You don't say which version of SQL Server you wish to upgrade to?
The guys in the Access newsgroup tend to have their own opinons regarding
the Access upgrade wizard so you may want to ask in there!
The upgrade wizard may provide enough to upgrade your database but then you
should look at tuning and re-writing the code so that it is more compatible
with SQL server, such as choosing more appropriate data types etc.
As an alternative you can do this manually and piecemeal using the Import
Wizard in SQL server (i.e DTS/SSIS).
Before you try anything make sure that you have a recoverable backup. It
will be worthwhile honing the upgrade on a separate system before attempting
anything on the live database.
John
"Jack" wrote:
> Hello all,
> I got a application which is developed using VB6.0 as front end and
> MS-Access as backend. Now i would like to change the database from MS-Access
> to MS-SQLserver.
> How do I change the databse from MS-Access to MS-SQLServer?
> Regards
> Jack
I got a application which is developed using VB6.0 as front end and
MS-Access as backend. Now i would like to change the database from MS-Access
to MS-SQLserver.
How do I change the databse from MS-Access to MS-SQLServer?
Regards
JackHi Jack
You don't say which version of SQL Server you wish to upgrade to?
The guys in the Access newsgroup tend to have their own opinons regarding
the Access upgrade wizard so you may want to ask in there!
The upgrade wizard may provide enough to upgrade your database but then you
should look at tuning and re-writing the code so that it is more compatible
with SQL server, such as choosing more appropriate data types etc.
As an alternative you can do this manually and piecemeal using the Import
Wizard in SQL server (i.e DTS/SSIS).
Before you try anything make sure that you have a recoverable backup. It
will be worthwhile honing the upgrade on a separate system before attempting
anything on the live database.
John
"Jack" wrote:
> Hello all,
> I got a application which is developed using VB6.0 as front end and
> MS-Access as backend. Now i would like to change the database from MS-Access
> to MS-SQLserver.
> How do I change the databse from MS-Access to MS-SQLServer?
> Regards
> Jack
Friday, February 10, 2012
changing data source on deploy?
We developed all our reports (a bunch of them) using our development server
named "development" which is not a local server... meaning we cant set our
connection string to localhost when we make them... but then we need to
deploy them to our Live server which then can be localhost as they will only
run on that server... how can we change the connection string's server upon
deployment? also we need to change the traget server to the live one instead
of development... can this be scripted or do we have to change the
connection string manually each and every time we make a change on
development and redeploy to the live server? thanks!The default when deploying is to not overwrite data sources. That means you
only have to change things the first time you deploy to production, after
that you are good to go. No more changes necessary.
As far as target server, in VS you pick the solution configuration, each
solution configuration has its own target server. So you just select the
configuration you want that is appropriate and then deploy to it.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Smokey Grindle" <nospam@.dontspamme.com> wrote in message
news:%23AamjiKRHHA.496@.TK2MSFTNGP06.phx.gbl...
> We developed all our reports (a bunch of them) using our development
> server named "development" which is not a local server... meaning we cant
> set our connection string to localhost when we make them... but then we
> need to deploy them to our Live server which then can be localhost as they
> will only run on that server... how can we change the connection string's
> server upon deployment? also we need to change the traget server to the
> live one instead of development... can this be scripted or do we have to
> change the connection string manually each and every time we make a change
> on development and redeploy to the live server? thanks!
>|||Awesome thanks, but what about for integrated data sources? I found a script
in the same scripts that seems to change the data source its called
PublishSampleReports.rss would this work for changing reports that have
integrated non shared data sources? thanks!
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:eN1imwKRHHA.912@.TK2MSFTNGP06.phx.gbl...
> The default when deploying is to not overwrite data sources. That means
> you only have to change things the first time you deploy to production,
> after that you are good to go. No more changes necessary.
> As far as target server, in VS you pick the solution configuration, each
> solution configuration has its own target server. So you just select the
> configuration you want that is appropriate and then deploy to it.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Smokey Grindle" <nospam@.dontspamme.com> wrote in message
> news:%23AamjiKRHHA.496@.TK2MSFTNGP06.phx.gbl...
>> We developed all our reports (a bunch of them) using our development
>> server named "development" which is not a local server... meaning we cant
>> set our connection string to localhost when we make them... but then we
>> need to deploy them to our Live server which then can be localhost as
>> they will only run on that server... how can we change the connection
>> string's server upon deployment? also we need to change the traget server
>> to the live one instead of development... can this be scripted or do we
>> have to change the connection string manually each and every time we make
>> a change on development and redeploy to the live server? thanks!
>|||I don't know about that. I always used shared data sources.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Smokey Grindle" <nospam@.dontspamme.com> wrote in message
news:uWzPVBLRHHA.3996@.TK2MSFTNGP04.phx.gbl...
> Awesome thanks, but what about for integrated data sources? I found a
> script in the same scripts that seems to change the data source its called
> PublishSampleReports.rss would this work for changing reports that have
> integrated non shared data sources? thanks!
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:eN1imwKRHHA.912@.TK2MSFTNGP06.phx.gbl...
>> The default when deploying is to not overwrite data sources. That means
>> you only have to change things the first time you deploy to production,
>> after that you are good to go. No more changes necessary.
>> As far as target server, in VS you pick the solution configuration, each
>> solution configuration has its own target server. So you just select the
>> configuration you want that is appropriate and then deploy to it.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Smokey Grindle" <nospam@.dontspamme.com> wrote in message
>> news:%23AamjiKRHHA.496@.TK2MSFTNGP06.phx.gbl...
>> We developed all our reports (a bunch of them) using our development
>> server named "development" which is not a local server... meaning we
>> cant set our connection string to localhost when we make them... but
>> then we need to deploy them to our Live server which then can be
>> localhost as they will only run on that server... how can we change the
>> connection string's server upon deployment? also we need to change the
>> traget server to the live one instead of development... can this be
>> scripted or do we have to change the connection string manually each and
>> every time we make a change on development and redeploy to the live
>> server? thanks!
>>
>
named "development" which is not a local server... meaning we cant set our
connection string to localhost when we make them... but then we need to
deploy them to our Live server which then can be localhost as they will only
run on that server... how can we change the connection string's server upon
deployment? also we need to change the traget server to the live one instead
of development... can this be scripted or do we have to change the
connection string manually each and every time we make a change on
development and redeploy to the live server? thanks!The default when deploying is to not overwrite data sources. That means you
only have to change things the first time you deploy to production, after
that you are good to go. No more changes necessary.
As far as target server, in VS you pick the solution configuration, each
solution configuration has its own target server. So you just select the
configuration you want that is appropriate and then deploy to it.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Smokey Grindle" <nospam@.dontspamme.com> wrote in message
news:%23AamjiKRHHA.496@.TK2MSFTNGP06.phx.gbl...
> We developed all our reports (a bunch of them) using our development
> server named "development" which is not a local server... meaning we cant
> set our connection string to localhost when we make them... but then we
> need to deploy them to our Live server which then can be localhost as they
> will only run on that server... how can we change the connection string's
> server upon deployment? also we need to change the traget server to the
> live one instead of development... can this be scripted or do we have to
> change the connection string manually each and every time we make a change
> on development and redeploy to the live server? thanks!
>|||Awesome thanks, but what about for integrated data sources? I found a script
in the same scripts that seems to change the data source its called
PublishSampleReports.rss would this work for changing reports that have
integrated non shared data sources? thanks!
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:eN1imwKRHHA.912@.TK2MSFTNGP06.phx.gbl...
> The default when deploying is to not overwrite data sources. That means
> you only have to change things the first time you deploy to production,
> after that you are good to go. No more changes necessary.
> As far as target server, in VS you pick the solution configuration, each
> solution configuration has its own target server. So you just select the
> configuration you want that is appropriate and then deploy to it.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Smokey Grindle" <nospam@.dontspamme.com> wrote in message
> news:%23AamjiKRHHA.496@.TK2MSFTNGP06.phx.gbl...
>> We developed all our reports (a bunch of them) using our development
>> server named "development" which is not a local server... meaning we cant
>> set our connection string to localhost when we make them... but then we
>> need to deploy them to our Live server which then can be localhost as
>> they will only run on that server... how can we change the connection
>> string's server upon deployment? also we need to change the traget server
>> to the live one instead of development... can this be scripted or do we
>> have to change the connection string manually each and every time we make
>> a change on development and redeploy to the live server? thanks!
>|||I don't know about that. I always used shared data sources.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Smokey Grindle" <nospam@.dontspamme.com> wrote in message
news:uWzPVBLRHHA.3996@.TK2MSFTNGP04.phx.gbl...
> Awesome thanks, but what about for integrated data sources? I found a
> script in the same scripts that seems to change the data source its called
> PublishSampleReports.rss would this work for changing reports that have
> integrated non shared data sources? thanks!
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:eN1imwKRHHA.912@.TK2MSFTNGP06.phx.gbl...
>> The default when deploying is to not overwrite data sources. That means
>> you only have to change things the first time you deploy to production,
>> after that you are good to go. No more changes necessary.
>> As far as target server, in VS you pick the solution configuration, each
>> solution configuration has its own target server. So you just select the
>> configuration you want that is appropriate and then deploy to it.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Smokey Grindle" <nospam@.dontspamme.com> wrote in message
>> news:%23AamjiKRHHA.496@.TK2MSFTNGP06.phx.gbl...
>> We developed all our reports (a bunch of them) using our development
>> server named "development" which is not a local server... meaning we
>> cant set our connection string to localhost when we make them... but
>> then we need to deploy them to our Live server which then can be
>> localhost as they will only run on that server... how can we change the
>> connection string's server upon deployment? also we need to change the
>> traget server to the live one instead of development... can this be
>> scripted or do we have to change the connection string manually each and
>> every time we make a change on development and redeploy to the live
>> server? thanks!
>>
>
Changing Cube source in a EXCEL pivot table
Hi
I have developed a cube on a "test" server - using Excel 2003 as teh front end. All is well with the cube an dI now want to point Excel to the "production" server. I have modified the .oqy file to point to teh new server but Excel does not seem to use this - unless I start over and import data.
is there anyway of pointing to a different server (teh database/cube names are the same - I did an Archive and Restore to move teh database over)
thanks
Steve
By the way - this is SQL Analysis Server 2000 and Excel 2003|||There are 2 techniques I know of to change the data source for an Excel pivot table.
The "low tech" one is to shut down the Analysis Services instance on your test server. Then when you open up the Excel file, Excel will prompt you for a server.
The "hight tech" option is to write some VBA code to change the connection string. The trick to getting at the connection string is that it is stored on the connection property of the PivotCache object. To change a single pivot table on the current sheet you would write something like the following:
thisWorkbook.ActiveSheet.PivotTables(1).PivotCache.Connection = "Provider-MSOLAP.2;Data Source=<Server>;Initial Catalog=<Database>"
|||Another technique, which was mentioned on the public SQL OLAP Newsgroup, is to save the pivot table as an XML file. Then you can find and edit the connection string (search for the server/DB/cube names), and re-open and save the XML back as .XLS.|||Thanks to all.
I checked out the XML and the VBA solutions - at least I have options now.
Changing Cube source in a EXCEL pivot table
Hi
I have developed a cube on a "test" server - using Excel 2003 as teh front end. All is well with the cube an dI now want to point Excel to the "production" server. I have modified the .oqy file to point to teh new server but Excel does not seem to use this - unless I start over and import data.
is there anyway of pointing to a different server (teh database/cube names are the same - I did an Archive and Restore to move teh database over)
thanks
Steve
By the way - this is SQL Analysis Server 2000 and Excel 2003|||There are 2 techniques I know of to change the data source for an Excel pivot table.
The "low tech" one is to shut down the Analysis Services instance on your test server. Then when you open up the Excel file, Excel will prompt you for a server.
The "hight tech" option is to write some VBA code to change the connection string. The trick to getting at the connection string is that it is stored on the connection property of the PivotCache object. To change a single pivot table on the current sheet you would write something like the following:
thisWorkbook.ActiveSheet.PivotTables(1).PivotCache.Connection = "Provider-MSOLAP.2;Data Source=<Server>;Initial Catalog=<Database>"
|||Another technique, which was mentioned on the public SQL OLAP Newsgroup, is to save the pivot table as an XML file. Then you can find and edit the connection string (search for the server/DB/cube names), and re-open and save the XML back as .XLS.|||Thanks to all.
I checked out the XML and the VBA solutions - at least I have options now.
Subscribe to:
Posts (Atom)