move/copy database objects from SQL Server Express to SQL Server Standard?

Can anyone refer me to good 'recipes' or sources of information on this
topic??

I have Visual Studio Tools for Office, which installs SS 2005 Express
locally to my XP box, and I want to develop in SS 2005, then copy the
tables or queries or reports etc. to a SS 2005 Standard server.

Thank you, TomHi Tom

If the objects are on source code control you may just want to check out the
scripts and run them through SQLCMD.

If you want the whole database then you can either use backup/restore or
sp_detach_db/sp_attach_db, failing that you could use the import/export
wizard, If SQLExpress is does not allow external connections then you will
need to push it (export) from the SQLExpress machine.

Check out http://support.microsoft.com/kb/314546
John

"tlyczko" <tlyczko@.gmail.comwrote in message
news:1157561832.911996.148780@.b28g2000cwb.googlegr oups.com...

Quote:

Originally Posted by

Can anyone refer me to good 'recipes' or sources of information on this
topic??
>
I have Visual Studio Tools for Office, which installs SS 2005 Express
locally to my XP box, and I want to develop in SS 2005, then copy the
tables or queries or reports etc. to a SS 2005 Standard server.
>
Thank you, Tom
>

|||I should have said SS 2005 Developer, not Express, I am installing SS
2005 Dev to my workstation here.

But everything you said should work, I just have to learn how!!!!!!!!

I will read the KB article, I suppose I could learn SSIS for just
tables or queries etc., or even just re-create the queries on the SS
dev box.

Thanks a lot for answering!!

:) tom

John Bell wrote:

Quote:

Originally Posted by

Hi Tom
>
If the objects are on source code control you may just want to check out the
scripts and run them through SQLCMD.
>
If you want the whole database then you can either use backup/restore or
sp_detach_db/sp_attach_db, failing that you could use the import/export
wizard, If SQLExpress is does not allow external connections then you will
need to push it (export) from the SQLExpress machine.
>
Check out http://support.microsoft.com/kb/314546
>
John
>
>
"tlyczko" <tlyczko@.gmail.comwrote in message
news:1157561832.911996.148780@.b28g2000cwb.googlegr oups.com...

Quote:

Originally Posted by

Can anyone refer me to good 'recipes' or sources of information on this
topic??

I have Visual Studio Tools for Office, which installs SS 2005 Express
locally to my XP box, and I want to develop in SS 2005, then copy the
tables or queries or reports etc. to a SS 2005 Standard server.

Thank you, Tom

|||tlyczko wrote:

Quote:

Originally Posted by

I should have said SS 2005 Developer, not Express, I am installing SS
2005 Dev to my workstation here.

I found this link, I can't remember where:

http://blogs.msdn.com/euanga/archiv.../18/668916.aspx
HTH tom

move/copy database items from SS 2005 Express to SS 2005 Standard?

Can anyone refer me to good 'recipes' or sources of information on this
topic'
I have Visual Studio Tools for Office, which installs SS 2005 Express
locally to my XP box, and I want to develop in SS 2005, then copy the
tables or queries or reports etc. to a SS 2005 Standard server.
Thank you, TomYou can:
1. Using SSMS, script out the code to re-create the table, views, queries,
etc.
2. Using SSIS, Transfer the entire database, schema and/or data
3. Pull your script files from source control, thereby making sure that
nothing is moved to the production server except items that 'should' be
moved to production. (You are using source control, aren't you?)
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"tlyczko" <tlyczko@.gmail.com> wrote in message
news:1157562224.879951.99990@.e3g2000cwe.googlegroups.com...
> Can anyone refer me to good 'recipes' or sources of information on this
> topic'
> I have Visual Studio Tools for Office, which installs SS 2005 Express
> locally to my XP box, and I want to develop in SS 2005, then copy the
> tables or queries or reports etc. to a SS 2005 Standard server.
> Thank you, Tom
>|||I don't know anything yet about source control...do you mean Visual
SourceSafe'
I tried looking around a few months ago for decent documentation,
how-to, etc. about VSS 2005, and I didn't find anything, it was not
terribly intuitive either...
I don't always need to transfer the entire database either, I might
only have to transfer a query, for example.
Or I might have to refresh the tables in my dev workstation from the
main server...
Thank you,
Tom
Arnie Rowland wrote:[vbcol=seagreen]
> You can:
> 1. Using SSMS, script out the code to re-create the table, views, queries,
> etc.
> 2. Using SSIS, Transfer the entire database, schema and/or data
> 3. Pull your script files from source control, thereby making sure that
> nothing is moved to the production server except items that 'should' be
> moved to production. (You are using source control, aren't you?)
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "tlyczko" <tlyczko@.gmail.com> wrote in message
> news:1157562224.879951.99990@.e3g2000cwe.googlegroups.com...|||Visual SourceSafe is but one of many source control products, albeit one
that is included with Visual Studio.
You might find part 4 of this tutorial useful for an introductory view of
Sourcesafe.
http://msdn2.microsoft.com/en-us/library/ms167593.aspx
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"tlyczko" <tlyczko@.gmail.com> wrote in message
news:1157567635.523378.239270@.p79g2000cwp.googlegroups.com...
>I don't know anything yet about source control...do you mean Visual
> SourceSafe'
> I tried looking around a few months ago for decent documentation,
> how-to, etc. about VSS 2005, and I didn't find anything, it was not
> terribly intuitive either...
> I don't always need to transfer the entire database either, I might
> only have to transfer a query, for example.
> Or I might have to refresh the tables in my dev workstation from the
> main server...
> Thank you,
> Tom
> Arnie Rowland wrote:
>|||Visual SourceSafe didn't come with our Visual Studio...
Thank you for sending the link, I think I remember that Perforce makes
a single-user version that I could use...I'll check their website.
Thank you, Tom

> Most good judgment comes from experience.
> Most experience comes from bad judgment.
Agreed.
Thank you, Tom

move/copy database items from SS 2005 Express to SS 2005 Standard?

Can anyone refer me to good 'recipes' or sources of information on this
topic'
I have Visual Studio Tools for Office, which installs SS 2005 Express
locally to my XP box, and I want to develop in SS 2005, then copy the
tables or queries or reports etc. to a SS 2005 Standard server.
Thank you, TomYou can:
1. Using SSMS, script out the code to re-create the table, views, queries,
etc.
2. Using SSIS, Transfer the entire database, schema and/or data
3. Pull your script files from source control, thereby making sure that
nothing is moved to the production server except items that 'should' be
moved to production. (You are using source control, aren't you?)
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"tlyczko" <tlyczko@.gmail.com> wrote in message
news:1157562224.879951.99990@.e3g2000cwe.googlegroups.com...
> Can anyone refer me to good 'recipes' or sources of information on this
> topic'
> I have Visual Studio Tools for Office, which installs SS 2005 Express
> locally to my XP box, and I want to develop in SS 2005, then copy the
> tables or queries or reports etc. to a SS 2005 Standard server.
> Thank you, Tom
>|||I don't know anything yet about source control...do you mean Visual
SourceSafe'
I tried looking around a few months ago for decent documentation,
how-to, etc. about VSS 2005, and I didn't find anything, it was not
terribly intuitive either...
I don't always need to transfer the entire database either, I might
only have to transfer a query, for example.
Or I might have to refresh the tables in my dev workstation from the
main server...
Thank you,
Tom
Arnie Rowland wrote:
> You can:
> 1. Using SSMS, script out the code to re-create the table, views, queries,
> etc.
> 2. Using SSIS, Transfer the entire database, schema and/or data
> 3. Pull your script files from source control, thereby making sure that
> nothing is moved to the production server except items that 'should' be
> moved to production. (You are using source control, aren't you?)
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "tlyczko" <tlyczko@.gmail.com> wrote in message
> news:1157562224.879951.99990@.e3g2000cwe.googlegroups.com...
> > Can anyone refer me to good 'recipes' or sources of information on this
> > topic'
> >
> > I have Visual Studio Tools for Office, which installs SS 2005 Express
> > locally to my XP box, and I want to develop in SS 2005, then copy the
> > tables or queries or reports etc. to a SS 2005 Standard server.
> >
> > Thank you, Tom
> >|||Visual SourceSafe is but one of many source control products, albeit one
that is included with Visual Studio.
You might find part 4 of this tutorial useful for an introductory view of
Sourcesafe.
http://msdn2.microsoft.com/en-us/library/ms167593.aspx
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"tlyczko" <tlyczko@.gmail.com> wrote in message
news:1157567635.523378.239270@.p79g2000cwp.googlegroups.com...
>I don't know anything yet about source control...do you mean Visual
> SourceSafe'
> I tried looking around a few months ago for decent documentation,
> how-to, etc. about VSS 2005, and I didn't find anything, it was not
> terribly intuitive either...
> I don't always need to transfer the entire database either, I might
> only have to transfer a query, for example.
> Or I might have to refresh the tables in my dev workstation from the
> main server...
> Thank you,
> Tom
> Arnie Rowland wrote:
>> You can:
>> 1. Using SSMS, script out the code to re-create the table, views,
>> queries,
>> etc.
>> 2. Using SSIS, Transfer the entire database, schema and/or data
>> 3. Pull your script files from source control, thereby making sure that
>> nothing is moved to the production server except items that 'should' be
>> moved to production. (You are using source control, aren't you?)
>> --
>> Arnie Rowland, Ph.D.
>> Westwood Consulting, Inc
>> Most good judgment comes from experience.
>> Most experience comes from bad judgment.
>> - Anonymous
>>
>> "tlyczko" <tlyczko@.gmail.com> wrote in message
>> news:1157562224.879951.99990@.e3g2000cwe.googlegroups.com...
>> > Can anyone refer me to good 'recipes' or sources of information on this
>> > topic'
>> >
>> > I have Visual Studio Tools for Office, which installs SS 2005 Express
>> > locally to my XP box, and I want to develop in SS 2005, then copy the
>> > tables or queries or reports etc. to a SS 2005 Standard server.
>> >
>> > Thank you, Tom
>> >
>|||Visual SourceSafe didn't come with our Visual Studio...
Thank you for sending the link, I think I remember that Perforce makes
a single-user version that I could use...I'll check their website.
Thank you, Tom
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
Agreed.
Thank you, Tom

Move existing tables to a new Filegroup!

Hi All,
Is there any tools that I can use OR is there any way
that I can move existing tables in PRIMARY group to a new
filegroup programmingly. I have about 500 tables with
data on them that need to be moved to a new filegroup.
Thanks,
tom
If the tables have a clustered index (and most should) you can drop the CI
and recreate it specifying the other Filegroup and it will move the data
over. If you want to move the non-clustered indexes you will have to drop
and recreate them as well. This can all be done programmatically. But be
prepared for it to take a while if there is a lot of data and make sure your
log file can handle the load.
Andrew J. Kelly SQL MVP
"tt" <anonymous@.discussions.microsoft.com> wrote in message
news:480001c47363$df1294f0$a301280a@.phx.gbl...
> Hi All,
> Is there any tools that I can use OR is there any way
> that I can move existing tables in PRIMARY group to a new
> filegroup programmingly. I have about 500 tables with
> data on them that need to be moved to a new filegroup.
> Thanks,
> tom