I want the server side (sql and business logic) to know about one type. And
the client app(s) could derive there own types as needed but also store
their derivations so they can deserialize them. Is there a pattern for
this? What I am thinking now is simple example like:
public interface IVehicle
{
string Name
{
get;
set;
}
string Type
{
get;
set;
}
string Guid
{
get;
set;
}
public class Vehicle : IVehicle
{
private string name;
private string type;
private string data;
public string Name { get/set imp }
public string Type { get/set imp } // Derived type name. Used by
client to know how to deserilize Data.
public string Data { get/set imp} // Derived types xml.
}
So server knows about the Vehicle type and that is all. It can store three
columns: Name, Type, and Data.
If a client just wants to use Vehicle(s) then it is all set. However, it
may want to derive a Corvette or some other vehicle from base like so.
public class Corvette : IVehicle
{
private string name;
private string type;
private string data;
// Derived fields.
private string color;
public string Name { get/set imp }
public string Type { get/set imp }
public string Data { get/set imp}
public string Color { get/set imp}
public Corvette() { }
public Corvette(Vehicle vehicle) { //create a corvette from a vehicle. }
}
So I can get Vehicles from the server and create Corvettes on the client
side. However I need to store back a Corvette on the server, but the server
only knows about Vehicle type. So I am thinking serialize the Corvette type
into xml string, create a new Vehicle using same Name. Set vehicle.Type to
"Corvette" and store xml string in vehicle.Data. Now send the Vehicle type
to server for storage in SQL using the 3 columns in Vehicle. Now if the
client needs Corvette type, it gets the Vehicle, checks the Type and
deserializes the Data string into Corvette type and uses it. So that is the
round trip. Not pretty, but only way I can figure so far to do it. Any
ideas? TIA
William Stacey [MVP]
William Stacey [MVP]
There was an MSDN article written by Andrew Conrad that covers a scenario
very close to what you want to do. He uses an xml overflow column to store
the additional properties of the subclass.
"Death, Taxes, and Relational Databases, Part 1"
http://msdn.microsoft.com/library/de...ml04212003.asp
Specifically the section entitled: "Extending the Business Objects"
"William Stacey [MVP]" wrote:
> I want the server side (sql and business logic) to know about one type. And
> the client app(s) could derive there own types as needed but also store
> their derivations so they can deserialize them. Is there a pattern for
> this? What I am thinking now is simple example like:
> public interface IVehicle
> {
> string Name
> {
> get;
> set;
> }
> string Type
> {
> get;
> set;
> }
> string Guid
> {
> get;
> set;
> }
> public class Vehicle : IVehicle
> {
> private string name;
> private string type;
> private string data;
> public string Name { get/set imp }
> public string Type { get/set imp } // Derived type name. Used by
> client to know how to deserilize Data.
> public string Data { get/set imp} // Derived types xml.
> }
> So server knows about the Vehicle type and that is all. It can store three
> columns: Name, Type, and Data.
> If a client just wants to use Vehicle(s) then it is all set. However, it
> may want to derive a Corvette or some other vehicle from base like so.
> public class Corvette : IVehicle
> {
> private string name;
> private string type;
> private string data;
> // Derived fields.
> private string color;
> public string Name { get/set imp }
> public string Type { get/set imp }
> public string Data { get/set imp}
> public string Color { get/set imp}
> public Corvette() { }
> public Corvette(Vehicle vehicle) { //create a corvette from a vehicle. }
> }
> So I can get Vehicles from the server and create Corvettes on the client
> side. However I need to store back a Corvette on the server, but the server
> only knows about Vehicle type. So I am thinking serialize the Corvette type
> into xml string, create a new Vehicle using same Name. Set vehicle.Type to
> "Corvette" and store xml string in vehicle.Data. Now send the Vehicle type
> to server for storage in SQL using the 3 columns in Vehicle. Now if the
> client needs Corvette type, it gets the Vehicle, checks the Type and
> deserializes the Data string into Corvette type and uses it. So that is the
> round trip. Not pretty, but only way I can figure so far to do it. Any
> ideas? TIA
> --
> William Stacey [MVP]
> --
> William Stacey [MVP]
>
>
|||Thanks Todd. :-)
William Stacey [MVP]
"Todd Pfleiger [MSFT]" <ToddPfleigerMSFT@.discussions.microsoft.com> wrote in
message news:3B2852EA-495E-4D03-8CD7-10646EEF42E4@.microsoft.com...[vbcol=seagreen]
> There was an MSDN article written by Andrew Conrad that covers a scenario
> very close to what you want to do. He uses an xml overflow column to store
> the additional properties of the subclass.
> "Death, Taxes, and Relational Databases, Part 1"
> http://msdn.microsoft.com/library/de...ml04212003.asp
> Specifically the section entitled: "Extending the Business Objects"
>
> "William Stacey [MVP]" wrote:
Showing posts with label own. Show all posts
Showing posts with label own. Show all posts
Tuesday, March 27, 2012
Derived types and backend.
I want the server side (sql and business logic) to know about one type. And
the client app(s) could derive there own types as needed but also store
their derivations so they can deserialize them. Is there a pattern for
this? What I am thinking now is simple example like:
public interface IVehicle
{
string Name
{
get;
set;
}
string Type
{
get;
set;
}
string Guid
{
get;
set;
}
public class Vehicle : IVehicle
{
private string name;
private string type;
private string data;
public string Name { get/set imp }
public string Type { get/set imp } // Derived type name. Used by
client to know how to deserilize Data.
public string Data { get/set imp} // Derived types xml.
}
So server knows about the Vehicle type and that is all. It can store three
columns: Name, Type, and Data.
If a client just wants to use Vehicle(s) then it is all set. However, it
may want to derive a Corvette or some other vehicle from base like so.
public class Corvette : IVehicle
{
private string name;
private string type;
private string data;
// Derived fields.
private string color;
public string Name { get/set imp }
public string Type { get/set imp }
public string Data { get/set imp}
public string Color { get/set imp}
public Corvette() { }
public Corvette(Vehicle vehicle) { //create a corvette from a vehicle. }
}
So I can get Vehicles from the server and create Corvettes on the client
side. However I need to store back a Corvette on the server, but the server
only knows about Vehicle type. So I am thinking serialize the Corvette type
into xml string, create a new Vehicle using same Name. Set vehicle.Type to
"Corvette" and store xml string in vehicle.Data. Now send the Vehicle type
to server for storage in SQL using the 3 columns in Vehicle. Now if the
client needs Corvette type, it gets the Vehicle, checks the Type and
deserializes the Data string into Corvette type and uses it. So that is the
round trip. Not pretty, but only way I can figure so far to do it. Any
ideas? TIA
--
William Stacey [MVP]
William Stacey [MVP]There was an MSDN article written by Andrew Conrad that covers a scenario
very close to what you want to do. He uses an xml overflow column to store
the additional properties of the subclass.
"Death, Taxes, and Relational Databases, Part 1"
http://msdn.microsoft.com/library/d.../>
4212003.asp
Specifically the section entitled: "Extending the Business Objects"
"William Stacey [MVP]" wrote:
> I want the server side (sql and business logic) to know about one type. A
nd
> the client app(s) could derive there own types as needed but also store
> their derivations so they can deserialize them. Is there a pattern for
> this? What I am thinking now is simple example like:
> public interface IVehicle
> {
> string Name
> {
> get;
> set;
> }
> string Type
> {
> get;
> set;
> }
> string Guid
> {
> get;
> set;
> }
> public class Vehicle : IVehicle
> {
> private string name;
> private string type;
> private string data;
> public string Name { get/set imp }
> public string Type { get/set imp } // Derived type name. Used by
> client to know how to deserilize Data.
> public string Data { get/set imp} // Derived types xml.
> }
> So server knows about the Vehicle type and that is all. It can store thre
e
> columns: Name, Type, and Data.
> If a client just wants to use Vehicle(s) then it is all set. However, it
> may want to derive a Corvette or some other vehicle from base like so.
> public class Corvette : IVehicle
> {
> private string name;
> private string type;
> private string data;
> // Derived fields.
> private string color;
> public string Name { get/set imp }
> public string Type { get/set imp }
> public string Data { get/set imp}
> public string Color { get/set imp}
> public Corvette() { }
> public Corvette(Vehicle vehicle) { //create a corvette from a vehicle.
}
> }
> So I can get Vehicles from the server and create Corvettes on the client
> side. However I need to store back a Corvette on the server, but the serv
er
> only knows about Vehicle type. So I am thinking serialize the Corvette ty
pe
> into xml string, create a new Vehicle using same Name. Set vehicle.Type t
o
> "Corvette" and store xml string in vehicle.Data. Now send the Vehicle typ
e
> to server for storage in SQL using the 3 columns in Vehicle. Now if the
> client needs Corvette type, it gets the Vehicle, checks the Type and
> deserializes the Data string into Corvette type and uses it. So that is t
he
> round trip. Not pretty, but only way I can figure so far to do it. Any
> ideas? TIA
> --
> William Stacey [MVP]
> --
> William Stacey [MVP]
>
>|||Thanks Todd. :-)
William Stacey [MVP]
"Todd Pfleiger [MSFT]" <ToddPfleigerMSFT@.discussions.microsoft.com> wrote in
message news:3B2852EA-495E-4D03-8CD7-10646EEF42E4@.microsoft.com...
> There was an MSDN article written by Andrew Conrad that covers a scenario
> very close to what you want to do. He uses an xml overflow column to store
> the additional properties of the subclass.
> "Death, Taxes, and Relational Databases, Part 1"
> http://msdn.microsoft.com/library/d...
l04212003.asp
> Specifically the section entitled: "Extending the Business Objects"
>
> "William Stacey [MVP]" wrote:
>
the client app(s) could derive there own types as needed but also store
their derivations so they can deserialize them. Is there a pattern for
this? What I am thinking now is simple example like:
public interface IVehicle
{
string Name
{
get;
set;
}
string Type
{
get;
set;
}
string Guid
{
get;
set;
}
public class Vehicle : IVehicle
{
private string name;
private string type;
private string data;
public string Name { get/set imp }
public string Type { get/set imp } // Derived type name. Used by
client to know how to deserilize Data.
public string Data { get/set imp} // Derived types xml.
}
So server knows about the Vehicle type and that is all. It can store three
columns: Name, Type, and Data.
If a client just wants to use Vehicle(s) then it is all set. However, it
may want to derive a Corvette or some other vehicle from base like so.
public class Corvette : IVehicle
{
private string name;
private string type;
private string data;
// Derived fields.
private string color;
public string Name { get/set imp }
public string Type { get/set imp }
public string Data { get/set imp}
public string Color { get/set imp}
public Corvette() { }
public Corvette(Vehicle vehicle) { //create a corvette from a vehicle. }
}
So I can get Vehicles from the server and create Corvettes on the client
side. However I need to store back a Corvette on the server, but the server
only knows about Vehicle type. So I am thinking serialize the Corvette type
into xml string, create a new Vehicle using same Name. Set vehicle.Type to
"Corvette" and store xml string in vehicle.Data. Now send the Vehicle type
to server for storage in SQL using the 3 columns in Vehicle. Now if the
client needs Corvette type, it gets the Vehicle, checks the Type and
deserializes the Data string into Corvette type and uses it. So that is the
round trip. Not pretty, but only way I can figure so far to do it. Any
ideas? TIA
--
William Stacey [MVP]
William Stacey [MVP]There was an MSDN article written by Andrew Conrad that covers a scenario
very close to what you want to do. He uses an xml overflow column to store
the additional properties of the subclass.
"Death, Taxes, and Relational Databases, Part 1"
http://msdn.microsoft.com/library/d.../>
4212003.asp
Specifically the section entitled: "Extending the Business Objects"
"William Stacey [MVP]" wrote:
> I want the server side (sql and business logic) to know about one type. A
nd
> the client app(s) could derive there own types as needed but also store
> their derivations so they can deserialize them. Is there a pattern for
> this? What I am thinking now is simple example like:
> public interface IVehicle
> {
> string Name
> {
> get;
> set;
> }
> string Type
> {
> get;
> set;
> }
> string Guid
> {
> get;
> set;
> }
> public class Vehicle : IVehicle
> {
> private string name;
> private string type;
> private string data;
> public string Name { get/set imp }
> public string Type { get/set imp } // Derived type name. Used by
> client to know how to deserilize Data.
> public string Data { get/set imp} // Derived types xml.
> }
> So server knows about the Vehicle type and that is all. It can store thre
e
> columns: Name, Type, and Data.
> If a client just wants to use Vehicle(s) then it is all set. However, it
> may want to derive a Corvette or some other vehicle from base like so.
> public class Corvette : IVehicle
> {
> private string name;
> private string type;
> private string data;
> // Derived fields.
> private string color;
> public string Name { get/set imp }
> public string Type { get/set imp }
> public string Data { get/set imp}
> public string Color { get/set imp}
> public Corvette() { }
> public Corvette(Vehicle vehicle) { //create a corvette from a vehicle.
}
> }
> So I can get Vehicles from the server and create Corvettes on the client
> side. However I need to store back a Corvette on the server, but the serv
er
> only knows about Vehicle type. So I am thinking serialize the Corvette ty
pe
> into xml string, create a new Vehicle using same Name. Set vehicle.Type t
o
> "Corvette" and store xml string in vehicle.Data. Now send the Vehicle typ
e
> to server for storage in SQL using the 3 columns in Vehicle. Now if the
> client needs Corvette type, it gets the Vehicle, checks the Type and
> deserializes the Data string into Corvette type and uses it. So that is t
he
> round trip. Not pretty, but only way I can figure so far to do it. Any
> ideas? TIA
> --
> William Stacey [MVP]
> --
> William Stacey [MVP]
>
>|||Thanks Todd. :-)
William Stacey [MVP]
"Todd Pfleiger [MSFT]" <ToddPfleigerMSFT@.discussions.microsoft.com> wrote in
message news:3B2852EA-495E-4D03-8CD7-10646EEF42E4@.microsoft.com...
> There was an MSDN article written by Andrew Conrad that covers a scenario
> very close to what you want to do. He uses an xml overflow column to store
> the additional properties of the subclass.
> "Death, Taxes, and Relational Databases, Part 1"
> http://msdn.microsoft.com/library/d...
l04212003.asp
> Specifically the section entitled: "Extending the Business Objects"
>
> "William Stacey [MVP]" wrote:
>
Friday, March 9, 2012
Deploying many reports to different network
Hello,
We have a situation where we have a main reporting server on our main
network and a separate isolated network with it's own reporting server. There
is no external connectivity to the second network.
We need to be able to periodically synchronise the two servers (copy all
new/updated reports from the main server to the isolated server). We have
over 150 reports to transfer in this way (and only likely to increase), any
ideas on the easiest way to do this would be much appreciated. Is it a
question of copying the RDLs to the server and then running a script to
deploy the reports? Or can you backup and restore the RS databases?
Cheers,
--
BenHi Ben,
I would probably recommend following the strategy of writing a custom script
to extract all of the reports by enumerating through all of the report
objects - Reports, Datasources and Security settings etc. to extract them
out. Then write another script to migrate them to the new database.
From what I have seen the reporting service databases are fairly specific to
a machine/webfarm and it would be probably more trouble that it is worth to
just to a detach/attach.
regards,
Adrian.
"Ben S" <BenS@.discussions.microsoft.com> wrote in message
news:A8A126FA-C1CE-4126-972B-D4EBB28F0722@.microsoft.com...
> Hello,
> We have a situation where we have a main reporting server on our main
> network and a separate isolated network with it's own reporting server.
> There
> is no external connectivity to the second network.
> We need to be able to periodically synchronise the two servers (copy all
> new/updated reports from the main server to the isolated server). We have
> over 150 reports to transfer in this way (and only likely to increase),
> any
> ideas on the easiest way to do this would be much appreciated. Is it a
> question of copying the RDLs to the server and then running a script to
> deploy the reports? Or can you backup and restore the RS databases?
> Cheers,
> --
> Ben|||Or just follow MS suggested method of migrating an RS database :)
http://support.microsoft.com/?kbid=842425
"Ben S" <BenS@.discussions.microsoft.com> wrote in message
news:A8A126FA-C1CE-4126-972B-D4EBB28F0722@.microsoft.com...
> Hello,
> We have a situation where we have a main reporting server on our main
> network and a separate isolated network with it's own reporting server.
> There
> is no external connectivity to the second network.
> We need to be able to periodically synchronise the two servers (copy all
> new/updated reports from the main server to the isolated server). We have
> over 150 reports to transfer in this way (and only likely to increase),
> any
> ideas on the easiest way to do this would be much appreciated. Is it a
> question of copying the RDLs to the server and then running a script to
> deploy the reports? Or can you backup and restore the RS databases?
> Cheers,
> --
> Ben|||Thank you Adrian for both options.
I will leave this option as for now and try the scripting option first - I
should then be able to write it to only pick those reports modified after a
particular date to save transferring the whole lot each time.
Thanks again
Ben
"Adrian Russell" wrote:
> Or just follow MS suggested method of migrating an RS database :)
> http://support.microsoft.com/?kbid=842425
> "Ben S" <BenS@.discussions.microsoft.com> wrote in message
> news:A8A126FA-C1CE-4126-972B-D4EBB28F0722@.microsoft.com...
> > Hello,
> >
> > We have a situation where we have a main reporting server on our main
> > network and a separate isolated network with it's own reporting server.
> > There
> > is no external connectivity to the second network.
> >
> > We need to be able to periodically synchronise the two servers (copy all
> > new/updated reports from the main server to the isolated server). We have
> > over 150 reports to transfer in this way (and only likely to increase),
> > any
> > ideas on the easiest way to do this would be much appreciated. Is it a
> > question of copying the RDLs to the server and then running a script to
> > deploy the reports? Or can you backup and restore the RS databases?
> >
> > Cheers,
> > --
> > Ben
>
>|||Try 'RSScripter' from http://www.sqldbatips.com/ - it can create the
scripts and supporting files for you|||Thanks Parker, that looks very useful!
"Parker" wrote:
> Try 'RSScripter' from http://www.sqldbatips.com/ - it can create the
> scripts and supporting files for you
>
We have a situation where we have a main reporting server on our main
network and a separate isolated network with it's own reporting server. There
is no external connectivity to the second network.
We need to be able to periodically synchronise the two servers (copy all
new/updated reports from the main server to the isolated server). We have
over 150 reports to transfer in this way (and only likely to increase), any
ideas on the easiest way to do this would be much appreciated. Is it a
question of copying the RDLs to the server and then running a script to
deploy the reports? Or can you backup and restore the RS databases?
Cheers,
--
BenHi Ben,
I would probably recommend following the strategy of writing a custom script
to extract all of the reports by enumerating through all of the report
objects - Reports, Datasources and Security settings etc. to extract them
out. Then write another script to migrate them to the new database.
From what I have seen the reporting service databases are fairly specific to
a machine/webfarm and it would be probably more trouble that it is worth to
just to a detach/attach.
regards,
Adrian.
"Ben S" <BenS@.discussions.microsoft.com> wrote in message
news:A8A126FA-C1CE-4126-972B-D4EBB28F0722@.microsoft.com...
> Hello,
> We have a situation where we have a main reporting server on our main
> network and a separate isolated network with it's own reporting server.
> There
> is no external connectivity to the second network.
> We need to be able to periodically synchronise the two servers (copy all
> new/updated reports from the main server to the isolated server). We have
> over 150 reports to transfer in this way (and only likely to increase),
> any
> ideas on the easiest way to do this would be much appreciated. Is it a
> question of copying the RDLs to the server and then running a script to
> deploy the reports? Or can you backup and restore the RS databases?
> Cheers,
> --
> Ben|||Or just follow MS suggested method of migrating an RS database :)
http://support.microsoft.com/?kbid=842425
"Ben S" <BenS@.discussions.microsoft.com> wrote in message
news:A8A126FA-C1CE-4126-972B-D4EBB28F0722@.microsoft.com...
> Hello,
> We have a situation where we have a main reporting server on our main
> network and a separate isolated network with it's own reporting server.
> There
> is no external connectivity to the second network.
> We need to be able to periodically synchronise the two servers (copy all
> new/updated reports from the main server to the isolated server). We have
> over 150 reports to transfer in this way (and only likely to increase),
> any
> ideas on the easiest way to do this would be much appreciated. Is it a
> question of copying the RDLs to the server and then running a script to
> deploy the reports? Or can you backup and restore the RS databases?
> Cheers,
> --
> Ben|||Thank you Adrian for both options.
I will leave this option as for now and try the scripting option first - I
should then be able to write it to only pick those reports modified after a
particular date to save transferring the whole lot each time.
Thanks again
Ben
"Adrian Russell" wrote:
> Or just follow MS suggested method of migrating an RS database :)
> http://support.microsoft.com/?kbid=842425
> "Ben S" <BenS@.discussions.microsoft.com> wrote in message
> news:A8A126FA-C1CE-4126-972B-D4EBB28F0722@.microsoft.com...
> > Hello,
> >
> > We have a situation where we have a main reporting server on our main
> > network and a separate isolated network with it's own reporting server.
> > There
> > is no external connectivity to the second network.
> >
> > We need to be able to periodically synchronise the two servers (copy all
> > new/updated reports from the main server to the isolated server). We have
> > over 150 reports to transfer in this way (and only likely to increase),
> > any
> > ideas on the easiest way to do this would be much appreciated. Is it a
> > question of copying the RDLs to the server and then running a script to
> > deploy the reports? Or can you backup and restore the RS databases?
> >
> > Cheers,
> > --
> > Ben
>
>|||Try 'RSScripter' from http://www.sqldbatips.com/ - it can create the
scripts and supporting files for you|||Thanks Parker, that looks very useful!
"Parker" wrote:
> Try 'RSScripter' from http://www.sqldbatips.com/ - it can create the
> scripts and supporting files for you
>
Friday, February 24, 2012
deploy SQL2000 database to other server
hi,
I am sorting data from all different sources, xml, access, text..etc
to my own sql2000 server. (computer name is "testingmachine")
atfter I clean up the database, I will give the final database to the
client and install in their server (computer name is "SQLS")
1) what's the best way to move database structure and data over to
their server? there are few different methods, which one is the best
solution in my situation. thank you!
PS. I use *.adp ("access running time" as frontend client interface)
thank you!
This KB article should give you a few methods. You can decide which way is
best for your situation:
http://support.microsoft.com/default...46&Product=sql
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Bob Yang" <bobyang3@.hotmail.com> wrote in message
news:35582154.0406301458.2553431b@.posting.google.c om...
> hi,
> I am sorting data from all different sources, xml, access, text..etc
> to my own sql2000 server. (computer name is "testingmachine")
> atfter I clean up the database, I will give the final database to the
> client and install in their server (computer name is "SQLS")
> 1) what's the best way to move database structure and data over to
> their server? there are few different methods, which one is the best
> solution in my situation. thank you!
>
> PS. I use *.adp ("access running time" as frontend client interface)
> thank you!
I am sorting data from all different sources, xml, access, text..etc
to my own sql2000 server. (computer name is "testingmachine")
atfter I clean up the database, I will give the final database to the
client and install in their server (computer name is "SQLS")
1) what's the best way to move database structure and data over to
their server? there are few different methods, which one is the best
solution in my situation. thank you!
PS. I use *.adp ("access running time" as frontend client interface)
thank you!
This KB article should give you a few methods. You can decide which way is
best for your situation:
http://support.microsoft.com/default...46&Product=sql
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Bob Yang" <bobyang3@.hotmail.com> wrote in message
news:35582154.0406301458.2553431b@.posting.google.c om...
> hi,
> I am sorting data from all different sources, xml, access, text..etc
> to my own sql2000 server. (computer name is "testingmachine")
> atfter I clean up the database, I will give the final database to the
> client and install in their server (computer name is "SQLS")
> 1) what's the best way to move database structure and data over to
> their server? there are few different methods, which one is the best
> solution in my situation. thank you!
>
> PS. I use *.adp ("access running time" as frontend client interface)
> thank you!
deploy SQL2000 database to other server
hi,
I am sorting data from all different sources, xml, access, text..etc
to my own sql2000 server. (computer name is "testingmachine")
atfter I clean up the database, I will give the final database to the
client and install in their server (computer name is "SQLS")
1) what's the best way to move database structure and data over to
their server? there are few different methods, which one is the best
solution in my situation. thank you!
PS. I use *.adp ("access running time" as frontend client interface)
thank you!This KB article should give you a few methods. You can decide which way is
best for your situation:
http://support.microsoft.com/default.aspx?scid=kb;en-us;314546&Product=sql
--
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Bob Yang" <bobyang3@.hotmail.com> wrote in message
news:35582154.0406301458.2553431b@.posting.google.com...
> hi,
> I am sorting data from all different sources, xml, access, text..etc
> to my own sql2000 server. (computer name is "testingmachine")
> atfter I clean up the database, I will give the final database to the
> client and install in their server (computer name is "SQLS")
> 1) what's the best way to move database structure and data over to
> their server? there are few different methods, which one is the best
> solution in my situation. thank you!
>
> PS. I use *.adp ("access running time" as frontend client interface)
> thank you!
I am sorting data from all different sources, xml, access, text..etc
to my own sql2000 server. (computer name is "testingmachine")
atfter I clean up the database, I will give the final database to the
client and install in their server (computer name is "SQLS")
1) what's the best way to move database structure and data over to
their server? there are few different methods, which one is the best
solution in my situation. thank you!
PS. I use *.adp ("access running time" as frontend client interface)
thank you!This KB article should give you a few methods. You can decide which way is
best for your situation:
http://support.microsoft.com/default.aspx?scid=kb;en-us;314546&Product=sql
--
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Bob Yang" <bobyang3@.hotmail.com> wrote in message
news:35582154.0406301458.2553431b@.posting.google.com...
> hi,
> I am sorting data from all different sources, xml, access, text..etc
> to my own sql2000 server. (computer name is "testingmachine")
> atfter I clean up the database, I will give the final database to the
> client and install in their server (computer name is "SQLS")
> 1) what's the best way to move database structure and data over to
> their server? there are few different methods, which one is the best
> solution in my situation. thank you!
>
> PS. I use *.adp ("access running time" as frontend client interface)
> thank you!
deploy SQL2000 database to other server
hi,
I am sorting data from all different sources, xml, access, text..etc
to my own sql2000 server. (computer name is "testingmachine")
atfter I clean up the database, I will give the final database to the
client and install in their server (computer name is "SQLS")
1) what's the best way to move database structure and data over to
their server? there are few different methods, which one is the best
solution in my situation. thank you!
PS. I use *.adp ("access running time" as frontend client interface)
thank you!This KB article should give you a few methods. You can decide which way is
best for your situation:
http://support.microsoft.com/defaul...546&Product=sql
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Bob Yang" <bobyang3@.hotmail.com> wrote in message
news:35582154.0406301458.2553431b@.posting.google.com...
> hi,
> I am sorting data from all different sources, xml, access, text..etc
> to my own sql2000 server. (computer name is "testingmachine")
> atfter I clean up the database, I will give the final database to the
> client and install in their server (computer name is "SQLS")
> 1) what's the best way to move database structure and data over to
> their server? there are few different methods, which one is the best
> solution in my situation. thank you!
>
> PS. I use *.adp ("access running time" as frontend client interface)
> thank you!
I am sorting data from all different sources, xml, access, text..etc
to my own sql2000 server. (computer name is "testingmachine")
atfter I clean up the database, I will give the final database to the
client and install in their server (computer name is "SQLS")
1) what's the best way to move database structure and data over to
their server? there are few different methods, which one is the best
solution in my situation. thank you!
PS. I use *.adp ("access running time" as frontend client interface)
thank you!This KB article should give you a few methods. You can decide which way is
best for your situation:
http://support.microsoft.com/defaul...546&Product=sql
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Bob Yang" <bobyang3@.hotmail.com> wrote in message
news:35582154.0406301458.2553431b@.posting.google.com...
> hi,
> I am sorting data from all different sources, xml, access, text..etc
> to my own sql2000 server. (computer name is "testingmachine")
> atfter I clean up the database, I will give the final database to the
> client and install in their server (computer name is "SQLS")
> 1) what's the best way to move database structure and data over to
> their server? there are few different methods, which one is the best
> solution in my situation. thank you!
>
> PS. I use *.adp ("access running time" as frontend client interface)
> thank you!
Sunday, February 19, 2012
deploy MS Reporting services to IIS on my own pc
How do I deploy a report developed in MS Reporting Services to an IIS
on my own pc?
FrancoOn 14 Oct 2005 10:13:45 -0700, francowell@.gmail.com wrote:
>How do I deploy a report developed in MS Reporting Services to an IIS
>on my own pc?
>Franco
You can't - at least not if you only have IIS on the machine.
You can deploy to a server running Reporting Services, which also
require IIS.
Or, if you are using Reporting Services 2005, you can also use the new
ReportViewer controls which don't require Reporting Services on a
server but have more limited functionality.
Andrew Watt
MVP - InfoPath|||My PC also has SQL 2000 and VS Studio.net 2003 installed on it. Do I
have what is needeed to deploy a report on this pc?
Franco|||On 14 Oct 2005 11:30:12 -0700, francowell@.gmail.com wrote:
>My PC also has SQL 2000 and VS Studio.net 2003 installed on it. Do I
>have what is needeed to deploy a report on this pc?
>Franco
If you have SQL Server 2000 then, assuming you obtained Reporting
Services 2000, you can deploy on the machine.
If you have SQL Server 2000 Developer Edition you can test deployment
but you are not licensed, as I understand it, to deploy for production
use.
Andrew Watt
MVP - InfoPath|||This is only for testing the reports that I am developing. How do I go
about deploying the report?
Franco|||On 14 Oct 2005 12:26:11 -0700, francowell@.gmail.com wrote:
>This is only for testing the reports that I am developing. How do I go
>about deploying the report?
>Franco
Franco,
In VS2003, open Solution Explorer, right click on the Solution name,
select Deploy Solution.
Likely it will deploy to the correct location by default if you are
deploying locally.
Try accessing the report by going to http://localhost/reports/ in
Internet Explorer.
Andrew Watt
MVP - InfoPath|||Andrew
Your suggestion is not working, but thank you anyway. I appreciate
your help.
Have a great weekend....Franco|||Hi Franco,
There are lots of possibilities for it not working.
If you describe which aspect isn't working and what error message(s)
you get, then I can suggest how you can maybe fix it.
Andrew Watt
MVP - InfoPath
On 14 Oct 2005 13:16:16 -0700, francowell@.gmail.com wrote:
>Andrew
>Your suggestion is not working, but thank you anyway. I appreciate
>your help.
>Have a great weekend....Franco|||Franco, Have you ever installed Reporting Services Server. I assume since
you have created a report you installed the tools. Did you ever install
Reporting Services. Can you go to the website and see Report Manager?
You need to make sure it is installed and working properly before trying to
deploy.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<francowell@.gmail.com> wrote in message
news:1129320976.701766.251640@.g44g2000cwa.googlegroups.com...
> Andrew
> Your suggestion is not working, but thank you anyway. I appreciate
> your help.
> Have a great weekend....Franco
>
on my own pc?
FrancoOn 14 Oct 2005 10:13:45 -0700, francowell@.gmail.com wrote:
>How do I deploy a report developed in MS Reporting Services to an IIS
>on my own pc?
>Franco
You can't - at least not if you only have IIS on the machine.
You can deploy to a server running Reporting Services, which also
require IIS.
Or, if you are using Reporting Services 2005, you can also use the new
ReportViewer controls which don't require Reporting Services on a
server but have more limited functionality.
Andrew Watt
MVP - InfoPath|||My PC also has SQL 2000 and VS Studio.net 2003 installed on it. Do I
have what is needeed to deploy a report on this pc?
Franco|||On 14 Oct 2005 11:30:12 -0700, francowell@.gmail.com wrote:
>My PC also has SQL 2000 and VS Studio.net 2003 installed on it. Do I
>have what is needeed to deploy a report on this pc?
>Franco
If you have SQL Server 2000 then, assuming you obtained Reporting
Services 2000, you can deploy on the machine.
If you have SQL Server 2000 Developer Edition you can test deployment
but you are not licensed, as I understand it, to deploy for production
use.
Andrew Watt
MVP - InfoPath|||This is only for testing the reports that I am developing. How do I go
about deploying the report?
Franco|||On 14 Oct 2005 12:26:11 -0700, francowell@.gmail.com wrote:
>This is only for testing the reports that I am developing. How do I go
>about deploying the report?
>Franco
Franco,
In VS2003, open Solution Explorer, right click on the Solution name,
select Deploy Solution.
Likely it will deploy to the correct location by default if you are
deploying locally.
Try accessing the report by going to http://localhost/reports/ in
Internet Explorer.
Andrew Watt
MVP - InfoPath|||Andrew
Your suggestion is not working, but thank you anyway. I appreciate
your help.
Have a great weekend....Franco|||Hi Franco,
There are lots of possibilities for it not working.
If you describe which aspect isn't working and what error message(s)
you get, then I can suggest how you can maybe fix it.
Andrew Watt
MVP - InfoPath
On 14 Oct 2005 13:16:16 -0700, francowell@.gmail.com wrote:
>Andrew
>Your suggestion is not working, but thank you anyway. I appreciate
>your help.
>Have a great weekend....Franco|||Franco, Have you ever installed Reporting Services Server. I assume since
you have created a report you installed the tools. Did you ever install
Reporting Services. Can you go to the website and see Report Manager?
You need to make sure it is installed and working properly before trying to
deploy.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<francowell@.gmail.com> wrote in message
news:1129320976.701766.251640@.g44g2000cwa.googlegroups.com...
> Andrew
> Your suggestion is not working, but thank you anyway. I appreciate
> your help.
> Have a great weekend....Franco
>
Subscribe to:
Posts (Atom)