Showing posts with label internal. Show all posts
Showing posts with label internal. Show all posts

Sunday, March 25, 2012

DataSet2 is using an internal DataSet1!

Hi,
I have a report with a dataset_1 (select * from SQL_ServeTable // Name:
"dsDATA"). Is it possible to use this dataset "dsDATA" in the same report
from an other dataset_2 for example "select sum(AMOUNT) from dsDATA"?
Thank you for your consideration,
RalphNo, you can not do as you envision. However you can put in expressions that
do aggragates. Look in the index of the help for aggregate functions.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ralph Hüttenmoser" <spam_no_spam@.bluewin.ch> wrote in message
news:evnFqsNzEHA.260@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I have a report with a dataset_1 (select * from SQL_ServeTable // Name:
> "dsDATA"). Is it possible to use this dataset "dsDATA" in the same report
> from an other dataset_2 for example "select sum(AMOUNT) from dsDATA"?
> Thank you for your consideration,
> Ralph
>|||Thanks Bruce

Friday, February 17, 2012

Database Versioning?

Hi,

Could someone point me in the right direction? I have an internal development database and a production database. Is there an easy way to replicate the changes that have been made to the development version on the production server without modifying the actual data in the tables? So, if I add a new user in my development version I offcourse don't want to see it pop up in the live version. But adding/deleting/updating a new table or column should.

And if possible I'd also like to know how you could do the following: Let's say we have an OrderDetail table containing information about the purchased product. Let's say I'd like to add a new column 'total' to skip calculation on the database every time I want to know the totals. It should be able to initialise the value by doing 'times ordered * price' for every existing row. Is that possible as well?

Srry for the noob questions Smile

edit: Using MSSQL 2005

There are tools like Red-Gate Compare and Visual Studio for Database Professionals that might be helpful for this situation.

Check out "Computed Columns" in the Books Online.

WesleyB

Visit my SQL Server weblog @. http://dis4ea.blogspot.com

|||http://www.red-gate.com/

And ApexSQL has a tool for this too, I believe.
http://www.apexsql.com/sql_tools_script.asp

HTH...

Joe|||

Also, check out Visual Studio 2005 Team Edition for Database Professionals.

http://msdn2.microsoft.com/en-us/teamsystem/aa718807.aspx

Database Versioning?

Hi,

Could someone point me in the right direction? I have an internal development database and a production database. Is there an easy way to replicate the changes that have been made to the development version on the production server without modifying the actual data in the tables? So, if I add a new user in my development version I offcourse don't want to see it pop up in the live version. But adding/deleting/updating a new table or column should.

And if possible I'd also like to know how you could do the following: Let's say we have an OrderDetail table containing information about the purchased product. Let's say I'd like to add a new column 'total' to skip calculation on the database every time I want to know the totals. It should be able to initialise the value by doing 'times ordered * price' for every existing row. Is that possible as well?

Srry for the noob questions Smile

edit: Using MSSQL 2005

There are tools like Red-Gate Compare and Visual Studio for Database Professionals that might be helpful for this situation.

Check out "Computed Columns" in the Books Online.

WesleyB

Visit my SQL Server weblog @. http://dis4ea.blogspot.com

|||http://www.red-gate.com/

And ApexSQL has a tool for this too, I believe.
http://www.apexsql.com/sql_tools_script.asp

HTH...

Joe|||

Also, check out Visual Studio 2005 Team Edition for Database Professionals.

http://msdn2.microsoft.com/en-us/teamsystem/aa718807.aspx

Database Version 539 vs. 611 (using SMO)

Hi
The number you are referring to is the internal version number of the
internal database schema. It generally gets updated between major releases.
To see this in action, attach or restore a SQL Server 2000 DB in 2005 using
T-SQL code in Management Studio. You will notice towards the end of the
operation, multiple messages showing the DB being upgraded one revision at a
time to the latest release.
There is no guarantee that between hotfixes or service packs the DB is not
upgraded. 611 is SQL Server 2005 RTM.
Querying the server for it's version number is more reliable.
Regards
--
Mike
This posting is provided "AS IS" with no warranties, and confers no rights.
"Amos Soma" <amos_j_soma@.yahoo.com> wrote in message
news:eH3R7kXlGHA.3816@.TK2MSFTNGP02.phx.gbl...
>I am using SMO in my .NET application to determine the version of a
>database (2000 or 2005). When I get the version of a SQL 2000 database, it
>returns 539. When I get the version of a SQL 2005 database, it returns 611.
> My question is this. Can I safely assume that a value of 539 always means
> the database is a SQL 2000 database, and can I safely assume that a value
> of 611 always means a SQL 2005 database?
> Also, does anyone know what '539' and '611' refer to?
> Thanks, Amos.
>Hi,
wait a minute, you queried for the wrong property. Guess you queried
for something like the Build Number. Use the following peroperty on SMO
to get the information:
Server.Information.Version.Major --whereas 8 is SQL 2000 and 9 is
SQL2k5
HTH, jens Suessmeyer.
http://www.sqlserver2005.de
--|||I am using SMO in my .NET application to determine the version of a database
(2000 or 2005). When I get the version of a SQL 2000 database, it returns
539. When I get the version of a SQL 2005 database, it returns 611.
My question is this. Can I safely assume that a value of 539 always means
the database is a SQL 2000 database, and can I safely assume that a value of
611 always means a SQL 2005 database?
Also, does anyone know what '539' and '611' refer to?
Thanks, Amos.|||Hi
The number you are referring to is the internal version number of the
internal database schema. It generally gets updated between major releases.
To see this in action, attach or restore a SQL Server 2000 DB in 2005 using
T-SQL code in Management Studio. You will notice towards the end of the
operation, multiple messages showing the DB being upgraded one revision at a
time to the latest release.
There is no guarantee that between hotfixes or service packs the DB is not
upgraded. 611 is SQL Server 2005 RTM.
Querying the server for it's version number is more reliable.
Regards
--
Mike
This posting is provided "AS IS" with no warranties, and confers no rights.
"Amos Soma" <amos_j_soma@.yahoo.com> wrote in message
news:eH3R7kXlGHA.3816@.TK2MSFTNGP02.phx.gbl...
>I am using SMO in my .NET application to determine the version of a
>database (2000 or 2005). When I get the version of a SQL 2000 database, it
>returns 539. When I get the version of a SQL 2005 database, it returns 611.
> My question is this. Can I safely assume that a value of 539 always means
> the database is a SQL 2000 database, and can I safely assume that a value
> of 611 always means a SQL 2005 database?
> Also, does anyone know what '539' and '611' refer to?
> Thanks, Amos.
>|||Hi,
wait a minute, you queried for the wrong property. Guess you queried
for something like the Build Number. Use the following peroperty on SMO
to get the information:
Server.Information.Version.Major --whereas 8 is SQL 2000 and 9 is
SQL2k5
HTH, jens Suessmeyer.
http://www.sqlserver2005.de
--|||Jens,
Fantastic! Thanks very much.
Amos.
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1150928369.273988.134490@.g10g2000cwb.googlegroups.com...
> Hi,
> wait a minute, you queried for the wrong property. Guess you queried
> for something like the Build Number. Use the following peroperty on SMO
> to get the information:
> Server.Information.Version.Major --whereas 8 is SQL 2000 and 9 is
> SQL2k5
> HTH, jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>|||Jens,
Fantastic! Thanks very much.
Amos.
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1150928369.273988.134490@.g10g2000cwb.googlegroups.com...
> Hi,
> wait a minute, you queried for the wrong property. Guess you queried
> for something like the Build Number. Use the following peroperty on SMO
> to get the information:
> Server.Information.Version.Major --whereas 8 is SQL 2000 and 9 is
> SQL2k5
> HTH, jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>

Tuesday, February 14, 2012

Database update issues

I have a simple, one table, database to hold an internal telephonedirectory. All is working well, except for the update. If Iedit a record, and for example, enter a value in a field that is blank,and then update, nothing happens! However, if i alter data thatwas already in that field and update, the changes take effect!!

Any help with this would be gratefully received,

Thanks in advance,

Vern.

I have been able to do this in Visual Web Developer 2005 Express. I just make a gridview or detailview and when going through the wizard for configuring the source for my SELECT I check *, then I click "Advanced" and select the Generate UPDATE, INSERT, DELETE ( i dont remember exactly what the name of it is, but its the only radio button you can select under advanced as long as the SELECT is set as *. After that just click next through the wizard, test your query if you want and click finish. Run your site and it should work.

I hope this helps, again I did this all with Visual Web Developer 2005 Express and didn't need to write any code, I am not sure how you are approaching this but if you want to use this was very easy, probably took literally 45 seconds to get working.

Good luck,

Brian

|||

Thanks for the reply Brian.

However, that exactlyhow I set it up. The strange thing is that I have now set thedefault value for a field to '-'. This means there is alwayssomething ing the field to start with. The field will then updatewhen the - is deleted and new data entered. What still is notworking, is that if you delete the data and then update, leaving thefield empty, you cannot then edit that field in the same way!