Hongju - can you be a little more specific on how to back up and restore the
databases. I have a very similar problem. I created a project that has a
database in APP_DATA. I'm hosting on GoDaddy and I need to take the APP_DAT
A
database (.mdf) and move it to one of their MySQL databases. I have no clue
on how to do that. Any help would be greatly appreciated.
Thanks
"hongju" wrote:
> You can backup local database and restore on the host database.
> If you developed database file using Visual Studio, you can attach databas
e
> on the host.
> And can modifiy connection string.
> "Noozer"?? ??? ??:
>Moving it to a MySQL database might take a little more work. Use the
"Generate scripts..." function in Management Studio and run those script
in the mysql database.
You will most likely need to modify them some to get them to work.
It's probably a good idea not to generate scripts for everything at
once, but to start with the tables first, then the views, then the SP's
etc etc...
Michelle wrote:
> Hongju - can you be a little more specific on how to back up and restore t
he
> databases. I have a very similar problem. I created a project that has a
> database in APP_DATA. I'm hosting on GoDaddy and I need to take the APP_D
ATA
> database (.mdf) and move it to one of their MySQL databases. I have no cl
ue
> on how to do that. Any help would be greatly appreciated.
> Thanks
> "hongju" wrote:
>
Showing posts with label similar. Show all posts
Showing posts with label similar. Show all posts
Friday, March 30, 2012
Monday, March 19, 2012
How to detect any changes made in Dev DB compared to Live DB
Hi,
I was just wondering if there's any way to detect what database objects
were lately modified in Dev database as compared to the similar one in Live
database.
When I develop in Dev datatabse, its very tough to keep track of all the
activities & changes that I do.
Is there a T-SQL where I can run it in a snapshot and know what tables,
columns, views, stored procs, triggers, user-defined function, etc. differ
than that in Live database.
This way, I know which objects to publish from Dev to Live.
Thanks,
Sam.
Message posted via http://www.sqlmonster.com
Nothing directly that comes with SQL Server. You can try
third party tools to do this - one is SQL Compare from Red
Gate:
http://www.red-gate.com/sql/summary.htm
The only free thing I know of is a script on
sql-server-performance.com which compares databases. Check
the following article:
http://www.sql-server-performance.co...parison_sp.asp
-Sue
On Tue, 15 Mar 2005 21:47:54 GMT, "Sameer Premji via
SQLMonster.com" <forum@.SQLMonster.com> wrote:
>Hi,
>I was just wondering if there's any way to detect what database objects
>were lately modified in Dev database as compared to the similar one in Live
>database.
>When I develop in Dev datatabse, its very tough to keep track of all the
>activities & changes that I do.
>Is there a T-SQL where I can run it in a snapshot and know what tables,
>columns, views, stored procs, triggers, user-defined function, etc. differ
>than that in Live database.
>This way, I know which objects to publish from Dev to Live.
>Thanks,
>Sam.
I was just wondering if there's any way to detect what database objects
were lately modified in Dev database as compared to the similar one in Live
database.
When I develop in Dev datatabse, its very tough to keep track of all the
activities & changes that I do.
Is there a T-SQL where I can run it in a snapshot and know what tables,
columns, views, stored procs, triggers, user-defined function, etc. differ
than that in Live database.
This way, I know which objects to publish from Dev to Live.
Thanks,
Sam.
Message posted via http://www.sqlmonster.com
Nothing directly that comes with SQL Server. You can try
third party tools to do this - one is SQL Compare from Red
Gate:
http://www.red-gate.com/sql/summary.htm
The only free thing I know of is a script on
sql-server-performance.com which compares databases. Check
the following article:
http://www.sql-server-performance.co...parison_sp.asp
-Sue
On Tue, 15 Mar 2005 21:47:54 GMT, "Sameer Premji via
SQLMonster.com" <forum@.SQLMonster.com> wrote:
>Hi,
>I was just wondering if there's any way to detect what database objects
>were lately modified in Dev database as compared to the similar one in Live
>database.
>When I develop in Dev datatabse, its very tough to keep track of all the
>activities & changes that I do.
>Is there a T-SQL where I can run it in a snapshot and know what tables,
>columns, views, stored procs, triggers, user-defined function, etc. differ
>than that in Live database.
>This way, I know which objects to publish from Dev to Live.
>Thanks,
>Sam.
How to detect any changes made in Dev DB compared to Live DB
Hi,
I was just wondering if there's any way to detect what database objects
were lately modified in Dev database as compared to the similar one in Live
database.
When I develop in Dev datatabse, its very tough to keep track of all the
activities & changes that I do.
Is there a T-SQL where I can run it in a snapshot and know what tables,
columns, views, stored procs, triggers, user-defined function, etc. differ
than that in Live database.
This way, I know which objects to publish from Dev to Live.
Thanks,
Sam.
--
Message posted via http://www.sqlmonster.comNothing directly that comes with SQL Server. You can try
third party tools to do this - one is SQL Compare from Red
Gate:
http://www.red-gate.com/sql/summary.htm
The only free thing I know of is a script on
sql-server-performance.com which compares databases. Check
the following article:
http://www.sql-server-performance.com/vg_database_comparison_sp.asp
-Sue
On Tue, 15 Mar 2005 21:47:54 GMT, "Sameer Premji via
SQLMonster.com" <forum@.SQLMonster.com> wrote:
>Hi,
>I was just wondering if there's any way to detect what database objects
>were lately modified in Dev database as compared to the similar one in Live
>database.
>When I develop in Dev datatabse, its very tough to keep track of all the
>activities & changes that I do.
>Is there a T-SQL where I can run it in a snapshot and know what tables,
>columns, views, stored procs, triggers, user-defined function, etc. differ
>than that in Live database.
>This way, I know which objects to publish from Dev to Live.
>Thanks,
>Sam.
I was just wondering if there's any way to detect what database objects
were lately modified in Dev database as compared to the similar one in Live
database.
When I develop in Dev datatabse, its very tough to keep track of all the
activities & changes that I do.
Is there a T-SQL where I can run it in a snapshot and know what tables,
columns, views, stored procs, triggers, user-defined function, etc. differ
than that in Live database.
This way, I know which objects to publish from Dev to Live.
Thanks,
Sam.
--
Message posted via http://www.sqlmonster.comNothing directly that comes with SQL Server. You can try
third party tools to do this - one is SQL Compare from Red
Gate:
http://www.red-gate.com/sql/summary.htm
The only free thing I know of is a script on
sql-server-performance.com which compares databases. Check
the following article:
http://www.sql-server-performance.com/vg_database_comparison_sp.asp
-Sue
On Tue, 15 Mar 2005 21:47:54 GMT, "Sameer Premji via
SQLMonster.com" <forum@.SQLMonster.com> wrote:
>Hi,
>I was just wondering if there's any way to detect what database objects
>were lately modified in Dev database as compared to the similar one in Live
>database.
>When I develop in Dev datatabse, its very tough to keep track of all the
>activities & changes that I do.
>Is there a T-SQL where I can run it in a snapshot and know what tables,
>columns, views, stored procs, triggers, user-defined function, etc. differ
>than that in Live database.
>This way, I know which objects to publish from Dev to Live.
>Thanks,
>Sam.
How to detect any changes made in Dev DB compared to Live DB
Hi,
I was just wondering if there's any way to detect what database objects
were lately modified in Dev database as compared to the similar one in Live
database.
When I develop in Dev datatabse, its very tough to keep track of all the
activities & changes that I do.
Is there a T-SQL where I can run it in a snapshot and know what tables,
columns, views, stored procs, triggers, user-defined function, etc. differ
than that in Live database.
This way, I know which objects to publish from Dev to Live.
Thanks,
Sam.
Message posted via http://www.droptable.comNothing directly that comes with SQL Server. You can try
third party tools to do this - one is SQL Compare from Red
Gate:
http://www.red-gate.com/sql/summary.htm
The only free thing I know of is a script on
sql-server-performance.com which compares databases. Check
the following article:
http://www.sql-server-performance.c...mparison_sp.asp
-Sue
On Tue, 15 Mar 2005 21:47:54 GMT, "Sameer Premji via
droptable.com" <forum@.droptable.com> wrote:
>Hi,
>I was just wondering if there's any way to detect what database objects
>were lately modified in Dev database as compared to the similar one in Live
>database.
>When I develop in Dev datatabse, its very tough to keep track of all the
>activities & changes that I do.
>Is there a T-SQL where I can run it in a snapshot and know what tables,
>columns, views, stored procs, triggers, user-defined function, etc. differ
>than that in Live database.
>This way, I know which objects to publish from Dev to Live.
>Thanks,
>Sam.
I was just wondering if there's any way to detect what database objects
were lately modified in Dev database as compared to the similar one in Live
database.
When I develop in Dev datatabse, its very tough to keep track of all the
activities & changes that I do.
Is there a T-SQL where I can run it in a snapshot and know what tables,
columns, views, stored procs, triggers, user-defined function, etc. differ
than that in Live database.
This way, I know which objects to publish from Dev to Live.
Thanks,
Sam.
Message posted via http://www.droptable.comNothing directly that comes with SQL Server. You can try
third party tools to do this - one is SQL Compare from Red
Gate:
http://www.red-gate.com/sql/summary.htm
The only free thing I know of is a script on
sql-server-performance.com which compares databases. Check
the following article:
http://www.sql-server-performance.c...mparison_sp.asp
-Sue
On Tue, 15 Mar 2005 21:47:54 GMT, "Sameer Premji via
droptable.com" <forum@.droptable.com> wrote:
>Hi,
>I was just wondering if there's any way to detect what database objects
>were lately modified in Dev database as compared to the similar one in Live
>database.
>When I develop in Dev datatabse, its very tough to keep track of all the
>activities & changes that I do.
>Is there a T-SQL where I can run it in a snapshot and know what tables,
>columns, views, stored procs, triggers, user-defined function, etc. differ
>than that in Live database.
>This way, I know which objects to publish from Dev to Live.
>Thanks,
>Sam.
How to design link tables?
I have been having a similar discussion on the MS Access newsgroup for the
last w
and I wanted to discuss the issues in the context of MS SQL in
addition to MS Access. I hope this form of cross posting is not offensive to
anyone.
Lets assume I have to relations: student and course and I want to create a
junction table to record which students are taking which courses.
(1) If I create a two column table containing fkStudent and fkCourse where
the primary consists of these two columns. Now I want to perform a join to
find out all the courses a particular student is taking. Since the primary
key index structure requires both foreign keys and I'm only providing the
value for fkStudent and not fkCourse, will I be preforming a linear search
on the junction table when I preform a join to determine what courses I am
taking?
My guess is yes. If your answer is yes, would you anticipate a linear search
to be a problem? I would. If you agree that we should avoid linear searches,
then what would you recommend for a primary key on this link table? Do we
need a pimary key at all? Most folks say yes -- but I'm not clear on why.
(2) Lets say I have many thousands of job titles -- too many for a combo
box. I want to have a M:M relationship between Job Titles and Job Postings.
Let's say I find a job posting on the web and I need to find the foriegn key
for a job title (if it exists) or create a job title (if it does not exist).
I can assume it does not exist and try an SQL INSERT and, if that fails, use
a SELECT. Or, I can assume it does exist and use SELECT and if I don't find
any, use INSERT. Either way, the worst case scenerio requires two redundant
lookups. Is there a better approach?
Thanks,
SiegfriedHi
1) Look at [Order Details] table in Northwind database.
It is a "junction table" between Orders and Product tables.
2)
IF NOT EXISTS (SELECT * FROM Table WHERE....)
INSERT INTO ......
ELSE
SELECT <columns> FROM ......
"Siegfried Heintze" <siegfried@.heintze.com> wrote in message
news:%23ofWEqlsFHA.460@.TK2MSFTNGP15.phx.gbl...
>I have been having a similar discussion on the MS Access newsgroup for the
> last w
and I wanted to discuss the issues in the context of MS SQL in
> addition to MS Access. I hope this form of cross posting is not offensive
> to
> anyone.
> Lets assume I have to relations: student and course and I want to create a
> junction table to record which students are taking which courses.
> (1) If I create a two column table containing fkStudent and fkCourse where
> the primary consists of these two columns. Now I want to perform a join to
> find out all the courses a particular student is taking. Since the primary
> key index structure requires both foreign keys and I'm only providing the
> value for fkStudent and not fkCourse, will I be preforming a linear search
> on the junction table when I preform a join to determine what courses I am
> taking?
> My guess is yes. If your answer is yes, would you anticipate a linear
> search
> to be a problem? I would. If you agree that we should avoid linear
> searches,
> then what would you recommend for a primary key on this link table? Do we
> need a pimary key at all? Most folks say yes -- but I'm not clear on why.
> (2) Lets say I have many thousands of job titles -- too many for a combo
> box. I want to have a M:M relationship between Job Titles and Job
> Postings.
> Let's say I find a job posting on the web and I need to find the foriegn
> key
> for a job title (if it exists) or create a job title (if it does not
> exist).
> I can assume it does not exist and try an SQL INSERT and, if that fails,
> use
> a SELECT. Or, I can assume it does exist and use SELECT and if I don't
> find
> any, use INSERT. Either way, the worst case scenerio requires two
> redundant
> lookups. Is there a better approach?
> Thanks,
> Siegfried
>
last w
addition to MS Access. I hope this form of cross posting is not offensive to
anyone.
Lets assume I have to relations: student and course and I want to create a
junction table to record which students are taking which courses.
(1) If I create a two column table containing fkStudent and fkCourse where
the primary consists of these two columns. Now I want to perform a join to
find out all the courses a particular student is taking. Since the primary
key index structure requires both foreign keys and I'm only providing the
value for fkStudent and not fkCourse, will I be preforming a linear search
on the junction table when I preform a join to determine what courses I am
taking?
My guess is yes. If your answer is yes, would you anticipate a linear search
to be a problem? I would. If you agree that we should avoid linear searches,
then what would you recommend for a primary key on this link table? Do we
need a pimary key at all? Most folks say yes -- but I'm not clear on why.
(2) Lets say I have many thousands of job titles -- too many for a combo
box. I want to have a M:M relationship between Job Titles and Job Postings.
Let's say I find a job posting on the web and I need to find the foriegn key
for a job title (if it exists) or create a job title (if it does not exist).
I can assume it does not exist and try an SQL INSERT and, if that fails, use
a SELECT. Or, I can assume it does exist and use SELECT and if I don't find
any, use INSERT. Either way, the worst case scenerio requires two redundant
lookups. Is there a better approach?
Thanks,
SiegfriedHi
1) Look at [Order Details] table in Northwind database.
It is a "junction table" between Orders and Product tables.
2)
IF NOT EXISTS (SELECT * FROM Table WHERE....)
INSERT INTO ......
ELSE
SELECT <columns> FROM ......
"Siegfried Heintze" <siegfried@.heintze.com> wrote in message
news:%23ofWEqlsFHA.460@.TK2MSFTNGP15.phx.gbl...
>I have been having a similar discussion on the MS Access newsgroup for the
> last w
> addition to MS Access. I hope this form of cross posting is not offensive
> to
> anyone.
> Lets assume I have to relations: student and course and I want to create a
> junction table to record which students are taking which courses.
> (1) If I create a two column table containing fkStudent and fkCourse where
> the primary consists of these two columns. Now I want to perform a join to
> find out all the courses a particular student is taking. Since the primary
> key index structure requires both foreign keys and I'm only providing the
> value for fkStudent and not fkCourse, will I be preforming a linear search
> on the junction table when I preform a join to determine what courses I am
> taking?
> My guess is yes. If your answer is yes, would you anticipate a linear
> search
> to be a problem? I would. If you agree that we should avoid linear
> searches,
> then what would you recommend for a primary key on this link table? Do we
> need a pimary key at all? Most folks say yes -- but I'm not clear on why.
> (2) Lets say I have many thousands of job titles -- too many for a combo
> box. I want to have a M:M relationship between Job Titles and Job
> Postings.
> Let's say I find a job posting on the web and I need to find the foriegn
> key
> for a job title (if it exists) or create a job title (if it does not
> exist).
> I can assume it does not exist and try an SQL INSERT and, if that fails,
> use
> a SELECT. Or, I can assume it does exist and use SELECT and if I don't
> find
> any, use INSERT. Either way, the worst case scenerio requires two
> redundant
> lookups. Is there a better approach?
> Thanks,
> Siegfried
>
Subscribe to:
Posts (Atom)