Thursday, March 29, 2012
Export DB to SQL Script
I am wanting to export a db.
It is unlikely that i will have access to a destination server via a network
or internet
connection. So i am intending to export my db to an sql script.
I have used the generate sql script option previously, but have found it
only exports the db objects. I need to export both the db objects and the
data they contain.
Any helpful suggestions would be appreciated!!Hi
If your database is small enought to fit onto a CD/DVD then you could use a
backup and restore it onto the new server
http://support.microsoft.com/defaul...b;en-us;Q314546
Failing that you should look at the BCP utility.
If you want to script as insert statements then check out
http://vyaskn.tripod.com/code.htm#inserts although I would not recommend it
for large amounts of data.
John
"AJ" wrote:
> How?
> I am wanting to export a db.
> It is unlikely that i will have access to a destination server via a netwo
rk
> or internet
> connection. So i am intending to export my db to an sql script.
> I have used the generate sql script option previously, but have found it
> only exports the db objects. I need to export both the db objects and the
> data they contain.
> Any helpful suggestions would be appreciated!!|||DB Ghost - www.dbghost.com
1. Use the data and schema scripter to script out all your tables and data
into a temporary directory.
2. Use the change manager - option one to build a database using the scripts
above and record the build into a SQL file. This step ensure the SQL is in
the correct dependancy order which Enterprise Manager cannot always do.
"AJ" wrote:
> How?
> I am wanting to export a db.
> It is unlikely that i will have access to a destination server via a netwo
rk
> or internet
> connection. So i am intending to export my db to an sql script.
> I have used the generate sql script option previously, but have found it
> only exports the db objects. I need to export both the db objects and the
> data they contain.
> Any helpful suggestions would be appreciated!!
Tuesday, March 27, 2012
Export database over the web?
Hi, i'm not sure if this is possible. I have an SQL Server database and a secure web server. I upload code via FTP but I don't have access to the database.
Users of my system login under various regions and record data based on their region. These users need to be able to download their data only into an Access database where they can run their own adhoc reports.
Is there a way whereby users can click a button on my aspx page that will pass a variable (user region) and allow them to download an access model or the data into an access model.
Thanks in advance for any help.
You could export the report to a csv. And then import the data into access.|||Hi thanks for the reply.
Would the users be able to invoke this action and download the file. Users need to import the data into an MS Access database that they hold locally.
|||It would require some training on the users side. The users would export the information from the report into a CSV file and save it to their hard drive. You'd then have a form on the access database that would allow them to "upload" the file into access without having to get into the dirty details of importing.Export data to linked servers (almost impossible) ?
servers)
I'm using Sql server 2005 Express.
I linked a mysql server via MSDASQL.
All done.
I can read from MySql.
What about to write into MySql?
I can't do this stuff:
=======================================
insert into
mysql.mydatabase.dbo.mytable
select
*
from
mymssql
=======================================
Because I can't use four part name (I think because of mysql odbc don't
support this interface)
please can you help me?
Regards.
fabri
MKDS: Joker - 055895 043343
AC:Fabrizio, Kanoemi, 1890 4700 1546
Tetris DS: 748422 559210Hello,
Please check whether the account which you are using sql server to connect
to mysql via odbc having approprriate write permissions.
Thanks,
P.C Sekhar.
"Fabri" <no@.sp.am> wrote in message news:e6rs1l$ek9$1@.nnrp.ngi.it...
> (sorry for eventually double post but i don't see my post in some news
> servers)
>
> I'm using Sql server 2005 Express.
> I linked a mysql server via MSDASQL.
> All done.
> I can read from MySql.
> What about to write into MySql?
> I can't do this stuff:
> =======================================
> insert into
> mysql.mydatabase.dbo.mytable
> select
> *
> from
> mymssql
> =======================================
> Because I can't use four part name (I think because of mysql odbc don't
> support this interface)
> please can you help me?
> Regards.
>
> --
> fabri
> MKDS: Joker - 055895 043343
> AC:Fabrizio, Kanoemi, 1890 4700 1546
> Tetris DS: 748422 559210
Monday, March 26, 2012
Export data from SQL2000 to XML
Is there any tools with SQL for that?
I don't want to use "for xml explicit"...
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!Hi
Check out:
http://sqlxml.org/faqs.aspx?faq=10
http://sqlxml.org/faqs.aspx?faq=29
John
"Leszek Gruszka" <leszek.gruszka@.kana.com.pl> wrote in message
news:415bfe97$0$26155$c397aba@.news.newsgroups.ws.. .
> How can I export data from SQL2000 to XML?
> Is there any tools with SQL for that?
> I don't want to use "for xml explicit"...
>
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!
Export data from SQL Server 2005 Express to Access Database?
We have successfully completed the project for the programmer in our team. Life was good.
Someone told me that I can use SQL Server 2000 instance to export SQL Server 2005.
I tried and cannot be done. Instance in SQL Server 2000 can't find instance in SQL 2005 Express.
:angel:
Friday, February 24, 2012
existing 32 bit apps through to SQL Server 2005 64 bit
we would like to trial our enterprise workforce management application (32
bit VB ActiveX app that currently connects to SQL Server 2000 via ADO)
connecting to SQL Server 2005 64bit server running Win 2003 64 bit.
Do I need to make any changes to application or client access software (ado
etc...) on the clients? or is it as simple as "roll in new 2005 64 server,
convert the database to 2005 64 format [if required] and change the
connection string on the client and watch it fly"...
excuse my ignorance but I need to make sure before signing off on the
business case.
Regards
Steve32-bit or 64-bit is not the problem here: moving the database from SQL
Server 2000 32-bit to 2005 64-bit just requires a detach/attach or
backup/restore.
The issue is if SQL Server 2005 is supported by your application. You need
to contact your application vendor to see if the application is certified for
SQL Server 2005.
Ben Nevarez, MCDBA, OCP
Database Administrator
"Steve" wrote:
> Hi,
> we would like to trial our enterprise workforce management application (32
> bit VB ActiveX app that currently connects to SQL Server 2000 via ADO)
> connecting to SQL Server 2005 64bit server running Win 2003 64 bit.
> Do I need to make any changes to application or client access software (ado
> etc...) on the clients? or is it as simple as "roll in new 2005 64 server,
> convert the database to 2005 64 format [if required] and change the
> connection string on the client and watch it fly"...
> excuse my ignorance but I need to make sure before signing off on the
> business case.
> Regards
> Steve|||thanks Ben,
since it is an in-house Visual Basic 6.0 application that uses ADO for
database connectivity, I would imaging that SQL Server 2005 is support by
Visual Basic and ADO...
"Ben Nevarez" wrote:
> 32-bit or 64-bit is not the problem here: moving the database from SQL
> Server 2000 32-bit to 2005 64-bit just requires a detach/attach or
> backup/restore.
> The issue is if SQL Server 2005 is supported by your application. You need
> to contact your application vendor to see if the application is certified for
> SQL Server 2005.
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "Steve" wrote:
> > Hi,
> > we would like to trial our enterprise workforce management application (32
> > bit VB ActiveX app that currently connects to SQL Server 2000 via ADO)
> > connecting to SQL Server 2005 64bit server running Win 2003 64 bit.
> >
> > Do I need to make any changes to application or client access software (ado
> > etc...) on the clients? or is it as simple as "roll in new 2005 64 server,
> > convert the database to 2005 64 format [if required] and change the
> > connection string on the client and watch it fly"...
> >
> > excuse my ignorance but I need to make sure before signing off on the
> > business case.
> >
> > Regards
> > Steve|||Just because it's an in house VB app doesn't guarantee compatibility.
Although nearly all your old SQL statements are supported, some syntax and
stored procedures have changed. For example the old outer join syntax of
use *= in the where clause is no longer available. Test your application.
Danny
"Steve" <Steve@.discussions.microsoft.com> wrote in message
news:DB94DA15-C4EE-4F1D-835E-34D6CF82E612@.microsoft.com...
> thanks Ben,
> since it is an in-house Visual Basic 6.0 application that uses ADO for
> database connectivity, I would imaging that SQL Server 2005 is support
> by
> Visual Basic and ADO...
> "Ben Nevarez" wrote:
>> 32-bit or 64-bit is not the problem here: moving the database from SQL
>> Server 2000 32-bit to 2005 64-bit just requires a detach/attach or
>> backup/restore.
>> The issue is if SQL Server 2005 is supported by your application. You
>> need
>> to contact your application vendor to see if the application is certified
>> for
>> SQL Server 2005.
>> Ben Nevarez, MCDBA, OCP
>> Database Administrator
>>
>> "Steve" wrote:
>> > Hi,
>> > we would like to trial our enterprise workforce management application
>> > (32
>> > bit VB ActiveX app that currently connects to SQL Server 2000 via ADO)
>> > connecting to SQL Server 2005 64bit server running Win 2003 64 bit.
>> >
>> > Do I need to make any changes to application or client access software
>> > (ado
>> > etc...) on the clients? or is it as simple as "roll in new 2005 64
>> > server,
>> > convert the database to 2005 64 format [if required] and change the
>> > connection string on the client and watch it fly"...
>> >
>> > excuse my ignorance but I need to make sure before signing off on the
>> > business case.
>> >
>> > Regards
>> > Steve|||Run SQL Server 2005 Upgrade Advisor and follow the recommendations.
Implement your test environment to test your application.
Ben Nevarez, MCDBA, OCP
Database Administrator
"Danny" wrote:
> Just because it's an in house VB app doesn't guarantee compatibility.
> Although nearly all your old SQL statements are supported, some syntax and
> stored procedures have changed. For example the old outer join syntax of
> use *= in the where clause is no longer available. Test your application.
> Danny
>
> "Steve" <Steve@.discussions.microsoft.com> wrote in message
> news:DB94DA15-C4EE-4F1D-835E-34D6CF82E612@.microsoft.com...
> > thanks Ben,
> > since it is an in-house Visual Basic 6.0 application that uses ADO for
> > database connectivity, I would imaging that SQL Server 2005 is support
> > by
> > Visual Basic and ADO...
> >
> > "Ben Nevarez" wrote:
> >
> >>
> >> 32-bit or 64-bit is not the problem here: moving the database from SQL
> >> Server 2000 32-bit to 2005 64-bit just requires a detach/attach or
> >> backup/restore.
> >>
> >> The issue is if SQL Server 2005 is supported by your application. You
> >> need
> >> to contact your application vendor to see if the application is certified
> >> for
> >> SQL Server 2005.
> >>
> >> Ben Nevarez, MCDBA, OCP
> >> Database Administrator
> >>
> >>
> >> "Steve" wrote:
> >>
> >> > Hi,
> >> > we would like to trial our enterprise workforce management application
> >> > (32
> >> > bit VB ActiveX app that currently connects to SQL Server 2000 via ADO)
> >> > connecting to SQL Server 2005 64bit server running Win 2003 64 bit.
> >> >
> >> > Do I need to make any changes to application or client access software
> >> > (ado
> >> > etc...) on the clients? or is it as simple as "roll in new 2005 64
> >> > server,
> >> > convert the database to 2005 64 format [if required] and change the
> >> > connection string on the client and watch it fly"...
> >> >
> >> > excuse my ignorance but I need to make sure before signing off on the
> >> > business case.
> >> >
> >> > Regards
> >> > Steve
>
>|||thanks ben and danny, much appreciated feedback
Steve
"Ben Nevarez" wrote:
> Run SQL Server 2005 Upgrade Advisor and follow the recommendations.
> Implement your test environment to test your application.
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "Danny" wrote:
> > Just because it's an in house VB app doesn't guarantee compatibility.
> > Although nearly all your old SQL statements are supported, some syntax and
> > stored procedures have changed. For example the old outer join syntax of
> > use *= in the where clause is no longer available. Test your application.
> >
> > Danny
> >
> >
> > "Steve" <Steve@.discussions.microsoft.com> wrote in message
> > news:DB94DA15-C4EE-4F1D-835E-34D6CF82E612@.microsoft.com...
> > > thanks Ben,
> > > since it is an in-house Visual Basic 6.0 application that uses ADO for
> > > database connectivity, I would imaging that SQL Server 2005 is support
> > > by
> > > Visual Basic and ADO...
> > >
> > > "Ben Nevarez" wrote:
> > >
> > >>
> > >> 32-bit or 64-bit is not the problem here: moving the database from SQL
> > >> Server 2000 32-bit to 2005 64-bit just requires a detach/attach or
> > >> backup/restore.
> > >>
> > >> The issue is if SQL Server 2005 is supported by your application. You
> > >> need
> > >> to contact your application vendor to see if the application is certified
> > >> for
> > >> SQL Server 2005.
> > >>
> > >> Ben Nevarez, MCDBA, OCP
> > >> Database Administrator
> > >>
> > >>
> > >> "Steve" wrote:
> > >>
> > >> > Hi,
> > >> > we would like to trial our enterprise workforce management application
> > >> > (32
> > >> > bit VB ActiveX app that currently connects to SQL Server 2000 via ADO)
> > >> > connecting to SQL Server 2005 64bit server running Win 2003 64 bit.
> > >> >
> > >> > Do I need to make any changes to application or client access software
> > >> > (ado
> > >> > etc...) on the clients? or is it as simple as "roll in new 2005 64
> > >> > server,
> > >> > convert the database to 2005 64 format [if required] and change the
> > >> > connection string on the client and watch it fly"...
> > >> >
> > >> > excuse my ignorance but I need to make sure before signing off on the
> > >> > business case.
> > >> >
> > >> > Regards
> > >> > Steve
> >
> >
> >
existing 32 bit apps through to SQL Server 2005 64 bit
we would like to trial our enterprise workforce management application (32
bit VB ActiveX app that currently connects to SQL Server 2000 via ADO)
connecting to SQL Server 2005 64bit server running Win 2003 64 bit.
Do I need to make any changes to application or client access software (ado
etc...) on the clients? or is it as simple as "roll in new 2005 64 server,
convert the database to 2005 64 format [if required] and change the
connection string on the client and watch it fly"...
excuse my ignorance but I need to make sure before signing off on the
business case.
Regards
Steve32-bit or 64-bit is not the problem here: moving the database from SQL
Server 2000 32-bit to 2005 64-bit just requires a detach/attach or
backup/restore.
The issue is if SQL Server 2005 is supported by your application. You need
to contact your application vendor to see if the application is certified fo
r
SQL Server 2005.
Ben Nevarez, MCDBA, OCP
Database Administrator
"Steve" wrote:
> Hi,
> we would like to trial our enterprise workforce management application (32
> bit VB ActiveX app that currently connects to SQL Server 2000 via ADO)
> connecting to SQL Server 2005 64bit server running Win 2003 64 bit.
> Do I need to make any changes to application or client access software (ad
o
> etc...) on the clients? or is it as simple as "roll in new 2005 64 server,
> convert the database to 2005 64 format [if required] and change the
> connection string on the client and watch it fly"...
> excuse my ignorance but I need to make sure before signing off on the
> business case.
> Regards
> Steve|||thanks Ben,
since it is an in-house Visual Basic 6.0 application that uses ADO for
database connectivity, I would imaging that SQL Server 2005 is support by
Visual Basic and ADO...
"Ben Nevarez" wrote:
[vbcol=seagreen]
> 32-bit or 64-bit is not the problem here: moving the database from SQL
> Server 2000 32-bit to 2005 64-bit just requires a detach/attach or
> backup/restore.
> The issue is if SQL Server 2005 is supported by your application. You need
> to contact your application vendor to see if the application is certified
for
> SQL Server 2005.
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "Steve" wrote:
>|||Xref: TK2MSFTNGP01.phx.gbl microsoft.public.sqlserver.server:433951
Just because it's an in house VB app doesn't guarantee compatibility.
Although nearly all your old SQL statements are supported, some syntax and
stored procedures have changed. For example the old outer join syntax of
use *= in the where clause is no longer available. Test your application.
Danny
"Steve" <Steve@.discussions.microsoft.com> wrote in message
news:DB94DA15-C4EE-4F1D-835E-34D6CF82E612@.microsoft.com...[vbcol=seagreen]
> thanks Ben,
> since it is an in-house Visual Basic 6.0 application that uses ADO for
> database connectivity, I would imaging that SQL Server 2005 is support
> by
> Visual Basic and ADO...
> "Ben Nevarez" wrote:
>|||Run SQL Server 2005 Upgrade Advisor and follow the recommendations.
Implement your test environment to test your application.
Ben Nevarez, MCDBA, OCP
Database Administrator
"Danny" wrote:
> Just because it's an in house VB app doesn't guarantee compatibility.
> Although nearly all your old SQL statements are supported, some syntax and
> stored procedures have changed. For example the old outer join syntax of
> use *= in the where clause is no longer available. Test your application.
> Danny
>
> "Steve" <Steve@.discussions.microsoft.com> wrote in message
> news:DB94DA15-C4EE-4F1D-835E-34D6CF82E612@.microsoft.com...
>
>