Moving to client/server

Hi
I have an access mdb frontend/backend app. To use sql server as backend, is
it better to keep the mdb frontend or should I switch to adp instead?
Thanks
Regards
Hi,
That does not matter. All depends up on your requirement.
Thanks
Hari
SQL Server MVP
"John" <John@.nospam.infovis.co.uk> wrote in message
news:e0AGovclFHA.2484@.TK2MSFTNGP15.phx.gbl...
> Hi
> I have an access mdb frontend/backend app. To use sql server as backend,
> is it better to keep the mdb frontend or should I switch to adp instead?
> Thanks
> Regards
>
|||What is the criteria to choose one over the other?
Regards
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23$GQX$dlFHA.3316@.TK2MSFTNGP14.phx.gbl...
> Hi,
> That does not matter. All depends up on your requirement.
> Thanks
> Hari
> SQL Server MVP
> "John" <John@.nospam.infovis.co.uk> wrote in message
> news:e0AGovclFHA.2484@.TK2MSFTNGP15.phx.gbl...
>
|||Per John:
>What is the criteria to choose one over the other?
If you've got an Access UI that works, I can't think of any reason to migrate to
another platform unless performance goes down the tubes when the DB is migrated
and somehow the other platform can remedy that. OTOH, keeping the same UI and
feeding with with stored procedures would probably accomplish anything that
another tool could.
PeteCresswell
|||On Sun, 31 Jul 2005 13:23:35 -0700, "(PeteCresswell)" <x@.y.z.invalid> wrote:

>Per John:
>If you've got an Access UI that works, I can't think of any reason to migrate to
>another platform unless performance goes down the tubes when the DB is migrated
>and somehow the other platform can remedy that. OTOH, keeping the same UI and
>feeding with with stored procedures would probably accomplish anything that
>another tool could.
Even switching to stored procedures is a huge job that means re-engineering
all the editable bound forms, and it's usually not necessary.
Converting queries to views and/or stored procedured is a good idea when...
1. A particular Access query can't be convinced to optimize well using linked
tables.
2. There will be multiple front-ends and you want to move much of the business
logic to the server, so it can be managed in one place without changing
multiple applications. Note that if you have SQL Server 2000 or newer, you
can often do this with Views and Instead Of triggers rather than stored
procedures, which is a much more Access-friendly way of doing it.
|||You can keep access itself as frontend
"John" wrote:

> Hi
> I have an access mdb frontend/backend app. To use sql server as backend, is
> it better to keep the mdb frontend or should I switch to adp instead?
> Thanks
> Regards
>
>

Moving SQL Express data to SQL Server 2005 Dev?

Hi gang,
Sorry for the bloody obviousness of this quetion, but I'm a unix/mysql
guy who's been tasked with moving an web app developed with SQL
Express (specifically RedDot CMS) to SQL Server 2005 Developer, and,
having literally NO working experience with the Microsoft products, am
wondering how one would migrate data from SQL Express to SQL Server
proper...
Any help or advice in this matter is most appreciated, I've trolled
this group but found no concrete info. Reading the documentation is
says it can be done at time of install, but, given my apprehension of
MS products reliability, is this a safe way to move a mission critical
DB?
Thanks a million,
Cheers
- Randall"MSSQL-n00b" <spliffhuxtable@.gmail.com> wrote in message
news:1174576289.977944.137500@.b75g2000hsg.googlegroups.com...
> Hi gang,
> Sorry for the bloody obviousness of this quetion, but I'm a unix/mysql
> guy who's been tasked with moving an web app developed with SQL
> Express (specifically RedDot CMS) to SQL Server 2005 Developer, and,
> having literally NO working experience with the Microsoft products, am
> wondering how one would migrate data from SQL Express to SQL Server
> proper...
> Any help or advice in this matter is most appreciated, I've trolled
> this group but found no concrete info. Reading the documentation is
> says it can be done at time of install, but, given my apprehension of
> MS products reliability, is this a safe way to move a mission critical
> DB?
> Thanks a million,
>
SQL Server Express uses the same engine and has the same file format as the
other editions of SQL Server. So you can take a backup of the database from
Express and restore it on another edition, you can detach the database and
attach it on another edition, or you can upgrade the Express edition to a
higher edition.
David

Moving SQL Express data to SQL Server 2005 Dev?

Hi gang,
Sorry for the bloody obviousness of this quetion, but I'm a unix/mysql
guy who's been tasked with moving an web app developed with SQL
Express (specifically RedDot CMS) to SQL Server 2005 Developer, and,
having literally NO working experience with the Microsoft products, am
wondering how one would migrate data from SQL Express to SQL Server
proper...
Any help or advice in this matter is most appreciated, I've trolled
this group but found no concrete info. Reading the documentation is
says it can be done at time of install, but, given my apprehension of
MS products reliability, is this a safe way to move a mission critical
DB?
Thanks a million,
Cheers
- Randall
"MSSQL-n00b" <spliffhuxtable@.gmail.com> wrote in message
news:1174576289.977944.137500@.b75g2000hsg.googlegr oups.com...
> Hi gang,
> Sorry for the bloody obviousness of this quetion, but I'm a unix/mysql
> guy who's been tasked with moving an web app developed with SQL
> Express (specifically RedDot CMS) to SQL Server 2005 Developer, and,
> having literally NO working experience with the Microsoft products, am
> wondering how one would migrate data from SQL Express to SQL Server
> proper...
> Any help or advice in this matter is most appreciated, I've trolled
> this group but found no concrete info. Reading the documentation is
> says it can be done at time of install, but, given my apprehension of
> MS products reliability, is this a safe way to move a mission critical
> DB?
> Thanks a million,
>
SQL Server Express uses the same engine and has the same file format as the
other editions of SQL Server. So you can take a backup of the database from
Express and restore it on another edition, you can detach the database and
attach it on another edition, or you can upgrade the Express edition to a
higher edition.
David

Moving SQL Express data to SQL Server 2005 Dev?

Hi gang,
Sorry for the bloody obviousness of this quetion, but I'm a unix/mysql
guy who's been tasked with moving an web app developed with SQL
Express (specifically RedDot CMS) to SQL Server 2005 Developer, and,
having literally NO working experience with the Microsoft products, am
wondering how one would migrate data from SQL Express to SQL Server
proper...
Any help or advice in this matter is most appreciated, I've trolled
this group but found no concrete info. Reading the documentation is
says it can be done at time of install, but, given my apprehension of
MS products reliability, is this a safe way to move a mission critical
DB?
Thanks a million,
Cheers
- Randall"MSSQL-n00b" <spliffhuxtable@.gmail.com> wrote in message
news:1174576289.977944.137500@.b75g2000hsg.googlegroups.com...
> Hi gang,
> Sorry for the bloody obviousness of this quetion, but I'm a unix/mysql
> guy who's been tasked with moving an web app developed with SQL
> Express (specifically RedDot CMS) to SQL Server 2005 Developer, and,
> having literally NO working experience with the Microsoft products, am
> wondering how one would migrate data from SQL Express to SQL Server
> proper...
> Any help or advice in this matter is most appreciated, I've trolled
> this group but found no concrete info. Reading the documentation is
> says it can be done at time of install, but, given my apprehension of
> MS products reliability, is this a safe way to move a mission critical
> DB?
> Thanks a million,
>
SQL Server Express uses the same engine and has the same file format as the
other editions of SQL Server. So you can take a backup of the database from
Express and restore it on another edition, you can detach the database and
attach it on another edition, or you can upgrade the Express edition to a
higher edition.
David

Moving of Stored Procedures

Need a little advice,
I am creating an application, created two databases, one for building
the app. And the other is for when it is running. Is there a simple way
of copying the stored procedures to the one that i will be running the
app on? All the tables and columns are named the same in both.
Tom
*** Sent via Developersdex http://www.codecomments.com ***
We migrate the sp with custom made table and sp.
We have table with 'from server', 'To Server', 'sp_name' and' permission'
information, which I populate for any sp migration using bcp. This table and
script can differ depending on your needs.
We also use a script that is built around sp_helptext, which can create the
drop sp statement, and script and permission. This is only useful if you do
extensive version control. Please let me know if you found and easier way to
deal with this.
Sam
|||You can simply script out the stored procedures using Enterprise Manager by
right clicking on the db, going to all tasks then generate scripts. Take
that script(s) and run it on the other database via query analyzer. You can
also invest a few dollars into a tool from www.red-gate.com that will
compare the two db's and tell you want is different. It will also generate
the scripts to make them both the same. It's really worth the few hundred
dollars if you do this often.
Andrew J. Kelly SQL MVP
"Thomas Beyerlein" <tbxml@.yahoo.com> wrote in message
news:%23C7dnX%23NGHA.1676@.TK2MSFTNGP09.phx.gbl...
> Need a little advice,
> I am creating an application, created two databases, one for building
> the app. And the other is for when it is running. Is there a simple way
> of copying the stored procedures to the one that i will be running the
> app on? All the tables and columns are named the same in both.
> Tom
>
> *** Sent via Developersdex http://www.codecomments.com ***

Moving of Stored Procedures

Need a little advice,
I am creating an application, created two databases, one for building
the app. And the other is for when it is running. Is there a simple way
of copying the stored procedures to the one that i will be running the
app on? All the tables and columns are named the same in both.
Tom
*** Sent via Developersdex http://www.developersdex.com ***We migrate the sp with custom made table and sp.
We have table with 'from server', 'To Server', 'sp_name' and' permission'
information, which I populate for any sp migration using bcp. This table and
script can differ depending on your needs.
We also use a script that is built around sp_helptext, which can create the
drop sp statement, and script and permission. This is only useful if you do
extensive version control. Please let me know if you found and easier way to
deal with this.
Sam|||You can simply script out the stored procedures using Enterprise Manager by
right clicking on the db, going to all tasks then generate scripts. Take
that script(s) and run it on the other database via query analyzer. You can
also invest a few dollars into a tool from www.red-gate.com that will
compare the two db's and tell you want is different. It will also generate
the scripts to make them both the same. It's really worth the few hundred
dollars if you do this often.
--
Andrew J. Kelly SQL MVP
"Thomas Beyerlein" <tbxml@.yahoo.com> wrote in message
news:%23C7dnX%23NGHA.1676@.TK2MSFTNGP09.phx.gbl...
> Need a little advice,
> I am creating an application, created two databases, one for building
> the app. And the other is for when it is running. Is there a simple way
> of copying the stored procedures to the one that i will be running the
> app on? All the tables and columns are named the same in both.
> Tom
>
> *** Sent via Developersdex http://www.developersdex.com ***

Moving of Stored Procedures

Need a little advice,
I am creating an application, created two databases, one for building
the app. And the other is for when it is running. Is there a simple way
of copying the stored procedures to the one that i will be running the
app on? All the tables and columns are named the same in both.
Tom
*** Sent via Developersdex http://www.codecomments.com ***We migrate the sp with custom made table and sp.
We have table with 'from server', 'To Server', 'sp_name' and' permission'
information, which I populate for any sp migration using bcp. This table and
script can differ depending on your needs.
We also use a script that is built around sp_helptext, which can create the
drop sp statement, and script and permission. This is only useful if you do
extensive version control. Please let me know if you found and easier way t
o
deal with this.
Sam|||You can simply script out the stored procedures using Enterprise Manager by
right clicking on the db, going to all tasks then generate scripts. Take
that script(s) and run it on the other database via query analyzer. You can
also invest a few dollars into a tool from www.red-gate.com that will
compare the two db's and tell you want is different. It will also generate
the scripts to make them both the same. It's really worth the few hundred
dollars if you do this often.
Andrew J. Kelly SQL MVP
"Thomas Beyerlein" <tbxml@.yahoo.com> wrote in message
news:%23C7dnX%23NGHA.1676@.TK2MSFTNGP09.phx.gbl...
> Need a little advice,
> I am creating an application, created two databases, one for building
> the app. And the other is for when it is running. Is there a simple way
> of copying the stored procedures to the one that i will be running the
> app on? All the tables and columns are named the same in both.
> Tom
>
> *** Sent via Developersdex http://www.codecomments.com ***