| Groups | Blog | Home |
sql server new users : AdventureWorksDB.msi installation on remote server
SQL Server 2000 installed on my desktop, but do not want to install SQL Server 2005 until I have learned a bit, so I can then upgrade my existing SQL Server 2000 databases to 2005. I would like to use a remote SQL Server 2005 installation on my ISP's server to install AdventureWorks. I do not have normal sa permissions, but am allowed to create a database using the ISP's console and then manage my db. So, I created an empty "AdventureWorks" database, and can connect to it. Now I want to install the sample AdventureWorksDB.msi onto the remote server. How do I go about this? Cheers, Charax
[quoted text, click to view]
> I would like to use a remote SQL Server 2005 installation on my ISP's > server to install AdventureWorks. I do not have normal sa permissions, but > am allowed to create a database using the ISP's console and then manage my > db. > > So, I created an empty "AdventureWorks" database, and can connect to it. > Now I want to install the sample AdventureWorksDB.msi onto the remote > server. How do I go about this? Creating an empty database named AdventureWorks isn't going to help you. The AdventureWorksDB.msi doesn't "create" the AdventureWorks database. It merely copies the data and log files (.mdf and .ldf) to the local server. You then have to manually attach the database to the instance of SQL Server. It sounds like you would have to have the ISP run the msi on their server and attach the AdventureWorks database and give you appropriate permissions to use it. If I were you, I would just go for the gusto and install SQL Server 2005 on your own local machine. There are no problems running SQL Server 2000 and 2005 side by side. -- Gail Erickson [MS] SQL Server Documentation Team This posting is provided "AS IS" with no warranties, and confers no rights Download the latest version of Books Online from http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx [quoted text, click to view] "Charax" <chopkins@ameritech.net> wrote in message news:OKtMgXJyGHA.4548@TK2MSFTNGP05.phx.gbl... >I have 2005 SSMS installed on my desktop, but not the database. I also have >SQL Server 2000 installed on my desktop, but do not want to install SQL >Server 2005 until I have learned a bit, so I can then upgrade my existing >SQL Server 2000 databases to 2005. > > I would like to use a remote SQL Server 2005 installation on my ISP's > server to install AdventureWorks. I do not have normal sa permissions, but > am allowed to create a database using the ISP's console and then manage my > db. > > So, I created an empty "AdventureWorks" database, and can connect to it. > Now I want to install the sample AdventureWorksDB.msi onto the remote > server. How do I go about this? > > Cheers, > > Charax
You could script out the AdventureWorks objects and data, and then after
connecting to the remote server, run the scripts. Look at ApexSQL's SQLDiff product as one option to create object and data scripts that can be used to move a database to a remote server. -- Arnie Rowland, Ph.D. Westwood Consulting, Inc Most good judgment comes from experience. Most experience comes from bad judgment. - Anonymous [quoted text, click to view] "Charax" <chopkins@ameritech.net> wrote in message news:OKtMgXJyGHA.4548@TK2MSFTNGP05.phx.gbl... >I have 2005 SSMS installed on my desktop, but not the database. I also have >SQL Server 2000 installed on my desktop, but do not want to install SQL >Server 2005 until I have learned a bit, so I can then upgrade my existing >SQL Server 2000 databases to 2005. > > I would like to use a remote SQL Server 2005 installation on my ISP's > server to install AdventureWorks. I do not have normal sa permissions, but > am allowed to create a database using the ISP's console and then manage my > db. > > So, I created an empty "AdventureWorks" database, and can connect to it. > Now I want to install the sample AdventureWorksDB.msi onto the remote > server. How do I go about this? > > Cheers, > > Charax
Actually, I think that the price for Diff is more like ~$500. Well worth the
expense if you need the functionality. I suggest that you download the 'fully functional' eval version and try it out. Then decide about value/cost... (OR check out Red-Gates' SQLCompare.) Generally, by 'script out', we mean that we create SQL scripts to recreate tables, views, stored procedures, logins, data inserts, etc. During development it is a recurring task, and can consume a lot of time continually revising the scripts as the schema and data needs evolve. That is how scripting tools such as ApexSQL's Diff or Red-Gates' SQLCompare provide value -they create the scripts that will allow you to transfer data to a server where you can run scripts, but you cannot install a MSI. -- Arnie Rowland, Ph.D. Westwood Consulting, Inc Most good judgment comes from experience. Most experience comes from bad judgment. - Anonymous [quoted text, click to view] "Charax" <chopkins@ameritech.net> wrote in message news:%23iNcrwMyGHA.1340@TK2MSFTNGP05.phx.gbl... > "Arnie Rowland" <arnie@1568.com> wrote in message > news:OLKAfeLyGHA.3844@TK2MSFTNGP06.phx.gbl... >> You could script out the AdventureWorks objects and data, and then after >> connecting to the remote server, run the scripts. >> >> Look at ApexSQL's SQLDiff product as one option to create object and data >> scripts that can be used to move a database to a remote server. >> >> -- >> Arnie Rowland, Ph.D. >> Westwood Consulting, Inc > > > Arnie, could you point me to more information where "script out" is > explained? Am I correct to I suppose you mean I must create a script that > recreates my local db on the ISP's remote server? > > And $1,600 for a program to write a one-time script for a small > non-commercial db seems a bit overkill.... > > Cheers, > > Charax
Thanks, Gail, but...
----- Original Message ----- From: "Gail Erickson [MS]" <gaile@online.microsoft.com> Newsgroups: microsoft.public.sqlserver.newusers Sent: Friday, August 25, 2006 10:08 PM Subject: Re: AdventureWorksDB.msi installation on remote server [quoted text, click to view] > Creating an empty database named AdventureWorks isn't going to help you. > The AdventureWorksDB.msi doesn't "create" the AdventureWorks database. It > merely copies the data and log files (.mdf and .ldf) to the local server. > You then have to manually attach the database to the instance of SQL > Server. It sounds like you would have to have the ISP run the msi on > their server and attach the AdventureWorks database and give you > appropriate permissions to use it. If I were you, I would just go for the > gusto and install SQL Server 2005 on your own local machine. There are no > problems running SQL Server 2000 and 2005 side by side. .... this raises the big issue: If I do have SQL Server 2005 installed on my desktop and converted my 2000 databases to 2005, how do I then publish/copy/move/restore (or whatever the correct terminology) the production database on my desktop to the ISP's server? Cheers, Charax
[quoted text, click to view]
"Arnie Rowland" <arnie@1568.com> wrote in message news:OLKAfeLyGHA.3844@TK2MSFTNGP06.phx.gbl... > You could script out the AdventureWorks objects and data, and then after > connecting to the remote server, run the scripts. > > Look at ApexSQL's SQLDiff product as one option to create object and data > scripts that can be used to move a database to a remote server. > > -- > Arnie Rowland, Ph.D. > Westwood Consulting, Inc Arnie, could you point me to more information where "script out" is explained? Am I correct to I suppose you mean I must create a script that recreates my local db on the ISP's remote server? And $1,600 for a program to write a one-time script for a small non-commercial db seems a bit overkill.... Cheers, Charax
Many thanks for your answer, Arnie. I'll do some more study and try to
follow your hints. As I mentioned to Gail, the real issue is how to relocate my production SQL Server database from my desktop computer to my ISP's server. But I'm stuck in the MS Access/FrontPage paradigm and not sure how to proceed. I use an MS Access 2003 front end through ODBC to SQL Server 2000. Upsizing my db taught me about handling SQL Server connections and tables, but not how to "move" or "publish" a database from one server to another. Isn't this is a common process? I must not know how to pose the question properly. Using the MS FrontPage metaphor, how do I maintain an SQL Server database on my local desktop and "publish" it to the ISP's server? Am I asking the right question? Cheers, Charax [quoted text, click to view] "Arnie Rowland" <arnie@1568.com> wrote in message
news:evE%23MGOyGHA.2208@TK2MSFTNGP03.phx.gbl... > Actually, I think that the price for Diff is more like ~$500. Well worth > the expense if you need the functionality. I suggest that you download the > 'fully functional' eval version and try it out. Then decide about > value/cost... (OR check out Red-Gates' SQLCompare.) > > Generally, by 'script out', we mean that we create SQL scripts to recreate > tables, views, stored procedures, logins, data inserts, etc. During > development it is a recurring task, and can consume a lot of time > continually revising the scripts as the schema and data needs evolve. That > is how scripting tools such as ApexSQL's Diff or Red-Gates' SQLCompare > provide value -they create the scripts that will allow you to transfer > data to a server where you can run scripts, but you cannot install a MSI. > > -- > Arnie Rowland, Ph.D. > Westwood Consulting, Inc
For a 'one time' pushing of the databases to the ISP's SQL Server, one of
the scripting tools would work for you. They are capable of creating scripts of only the differences between different databases. However, as I now understand you, another option to investigate may be Snapshot 'Replication'. (Replication schemes are where one (or multiple) servers keep each other's data synchronized. I suggest that you read up in Books Online about "How Replication Works". There are several alternatives, the correct one, perhaps other than Snapshot, will depend upon your need.) Of course, you may hot have the level of permission/access to the ISP's SQL Server to engage in any of the Replication schemes. I suspect that scripting may be your only choice. -- Arnie Rowland, Ph.D. Westwood Consulting, Inc Most good judgment comes from experience. Most experience comes from bad judgment. - Anonymous [quoted text, click to view] "Charax" <chopkins@ameritech.net> wrote in message news:eNjTtARyGHA.3908@TK2MSFTNGP05.phx.gbl... > Many thanks for your answer, Arnie. I'll do some more study and try to > follow your hints. > > As I mentioned to Gail, the real issue is how to relocate my production > SQL Server database from my desktop computer to my ISP's server. But I'm > stuck in the MS Access/FrontPage paradigm and not sure how to proceed. > > I use an MS Access 2003 front end through ODBC to SQL Server 2000. > Upsizing my db taught me about handling SQL Server connections and tables, > but not how to "move" or "publish" a database from one server to another. > Isn't this is a common process? I must not know how to pose the question > properly. > > Using the MS FrontPage metaphor, how do I maintain an SQL Server database > on my local desktop and "publish" it to the ISP's server? Am I asking the > right question? > > Cheers, > > Charax > > > "Arnie Rowland" <arnie@1568.com> wrote in message > news:evE%23MGOyGHA.2208@TK2MSFTNGP03.phx.gbl... >> Actually, I think that the price for Diff is more like ~$500. Well worth >> the expense if you need the functionality. I suggest that you download >> the 'fully functional' eval version and try it out. Then decide about >> value/cost... (OR check out Red-Gates' SQLCompare.) >> >> Generally, by 'script out', we mean that we create SQL scripts to >> recreate tables, views, stored procedures, logins, data inserts, etc. >> During development it is a recurring task, and can consume a lot of time >> continually revising the scripts as the schema and data needs evolve. >> That is how scripting tools such as ApexSQL's Diff or Red-Gates' >> SQLCompare provide value -they create the scripts that will allow you to >> transfer data to a server where you can run scripts, but you cannot >> install a MSI. >> >> -- >> Arnie Rowland, Ph.D. >> Westwood Consulting, Inc >
Don't see what you're looking for? Try a search.
|
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |