Bigint handling

I have a subreport that gives me the error :
An error occurred while executing the subreport
â'PlanLocationbyItemNumberLocations_subreportâ': Error during processing of
â'item_idâ' report parameter.
Preview complete -- 0 errors, 1 warnings
This problem only occurs when the value of the bigint in field "item_id"
(which is passed as a parmater to the subreport) is very large. Since I
can't find a report parameter option of bigint, only integer, what options do
I have?You can use Float instead of Integer.
--
| Thread-Topic: Bigint handling
| thread-index: AcS7okSK6UOq2ghATlGlwu+m0Ima4g==| X-WBNR-Posting-Host: 65.207.30.6
| From: "=?Utf-8?B?S0I=?=" <KB@.discussions.microsoft.com>
| Subject: Bigint handling
| Date: Tue, 26 Oct 2004 14:25:08 -0700
| Lines: 12
| Message-ID: <384D7CB6-0F38-4BCC-B8A7-DC550E2EE13C@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 8bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.reportingsvcs:33239
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
|
|
| I have a subreport that gives me the error :
| An error occurred while executing the subreport
| â'PlanLocationbyItemNumberLocations_subreportâ': Error during
processing of
| â'item_idâ' report parameter.
| Preview complete -- 0 errors, 1 warnings
|
| This problem only occurs when the value of the bigint in field "item_id"
| (which is passed as a parmater to the subreport) is very large. Since I
| can't find a report parameter option of bigint, only integer, what
options do
| I have?
|

BI Deployment Experiences

I'm trying to get some info on how other companies are handling BI
implementations. We have a data warehouse project that we expect will have
continuos changes. That is, new data sources coming in, more reports, etc.
That implies new Integration Services packages, new Reporting Services
reports, changes in tables, view, stored procedures, etc. We also have a 3
environment installation: Development, QA, Production.
I would appreciate any info on how other people are handling this. Can you
manage with only Visual Studio? Is there any third vendor tool anybody would
recommend? The issue is that we could potentially have the 3 environments
with different versions and we might want to move objects from development t
o
QA, for example, without just duplicating the 2 environments (we could have
different stages of development and only want to move finished objects).
Any help is appreciated,
Carmen.We have pretty much the exact same setup you do. We use Visual Studio and
Visual Source Safe to manage all our code. Using the new features for
managing environments within Visual Studio - makes promoting SSIS packages a
snap. Using DTS was more challenging when you for example moved from DEV to
TEST you had to change all your data sources to point to new places - but
SSIS makes that part easy.
If you tie your solutions into VSS and have your coders do all their work
inside of VSS - that will ensure it's managed correctly. Where I work won't
spring for the new Visual Studio Team Edition for DB Professionals - but
that def makes things easier in managing your DB code within the same
solution as your SSIS packages. You can still add the DB into your
solution, but not have ALL the cool features Team Edition offers.
So our developers, by using the VSS integration inside VS, it auto checks
out all the code, whether it be packages or stored procedures. Your
promoting to new environments from Visual Source Safe will endure you are
promoting the right stuff.
It's not that hard - once you get it sorted out and documented and follow
the process - you will be good.
"Carmen" <Carmen@.discussions.microsoft.com> wrote in message
news:B9EAA9CD-B73C-43D3-A314-5E99EE3DC694@.microsoft.com...
> I'm trying to get some info on how other companies are handling BI
> implementations. We have a data warehouse project that we expect will have
> continuos changes. That is, new data sources coming in, more reports, etc.
> That implies new Integration Services packages, new Reporting Services
> reports, changes in tables, view, stored procedures, etc. We also have a 3
> environment installation: Development, QA, Production.
> I would appreciate any info on how other people are handling this. Can you
> manage with only Visual Studio? Is there any third vendor tool anybody
> would
> recommend? The issue is that we could potentially have the 3 environments
> with different versions and we might want to move objects from development
> to
> QA, for example, without just duplicating the 2 environments (we could
> have
> different stages of development and only want to move finished objects).
> Any help is appreciated,
> Carmen.|||Our approach is to use XMLA scripts (using ascmd utility from SP1) and the
AS syncronize feature (again via XMLA scripts). Works fine - and no
Integration Services required.
Chris
www.activeinterface.com
"Carmen" <Carmen@.discussions.microsoft.com> wrote in message
news:B9EAA9CD-B73C-43D3-A314-5E99EE3DC694@.microsoft.com...
> I'm trying to get some info on how other companies are handling BI
> implementations. We have a data warehouse project that we expect will have
> continuos changes. That is, new data sources coming in, more reports, etc.
> That implies new Integration Services packages, new Reporting Services
> reports, changes in tables, view, stored procedures, etc. We also have a 3
> environment installation: Development, QA, Production.
> I would appreciate any info on how other people are handling this. Can you
> manage with only Visual Studio? Is there any third vendor tool anybody
> would
> recommend? The issue is that we could potentially have the 3 environments
> with different versions and we might want to move objects from development
> to
> QA, for example, without just duplicating the 2 environments (we could
> have
> different stages of development and only want to move finished objects).
> Any help is appreciated,
> Carmen.|||Chris,
Thanks for the info!
Carmen.
"ChrisHarrington" wrote:

> Our approach is to use XMLA scripts (using ascmd utility from SP1) and the
> AS syncronize feature (again via XMLA scripts). Works fine - and no
> Integration Services required.
> Chris
> www.activeinterface.com
> "Carmen" <Carmen@.discussions.microsoft.com> wrote in message
> news:B9EAA9CD-B73C-43D3-A314-5E99EE3DC694@.microsoft.com...
>
>|||Joe,
Thanks for the info. I'll definitely investigate the options you mentioned.
Carmen.
"Joe" wrote:

> We have pretty much the exact same setup you do. We use Visual Studio and
> Visual Source Safe to manage all our code. Using the new features for
> managing environments within Visual Studio - makes promoting SSIS packages
a
> snap. Using DTS was more challenging when you for example moved from DEV
to
> TEST you had to change all your data sources to point to new places - but
> SSIS makes that part easy.
> If you tie your solutions into VSS and have your coders do all their work
> inside of VSS - that will ensure it's managed correctly. Where I work won
't
> spring for the new Visual Studio Team Edition for DB Professionals - but
> that def makes things easier in managing your DB code within the same
> solution as your SSIS packages. You can still add the DB into your
> solution, but not have ALL the cool features Team Edition offers.
> So our developers, by using the VSS integration inside VS, it auto checks
> out all the code, whether it be packages or stored procedures. Your
> promoting to new environments from Visual Source Safe will endure you are
> promoting the right stuff.
> It's not that hard - once you get it sorted out and documented and follow
> the process - you will be good.
> "Carmen" <Carmen@.discussions.microsoft.com> wrote in message
> news:B9EAA9CD-B73C-43D3-A314-5E99EE3DC694@.microsoft.com...
>

BI Deployment Experiences

I'm trying to get some info on how other companies are handling BI
implementations. We have a data warehouse project that we expect will have
continuos changes. That is, new data sources coming in, more reports, etc.
That implies new Integration Services packages, new Reporting Services
reports, changes in tables, view, stored procedures, etc. We also have a 3
environment installation: Development, QA, Production.
I would appreciate any info on how other people are handling this. Can you
manage with only Visual Studio? Is there any third vendor tool anybody would
recommend? The issue is that we could potentially have the 3 environments
with different versions and we might want to move objects from development to
QA, for example, without just duplicating the 2 environments (we could have
different stages of development and only want to move finished objects).
Any help is appreciated,
Carmen.
We have pretty much the exact same setup you do. We use Visual Studio and
Visual Source Safe to manage all our code. Using the new features for
managing environments within Visual Studio - makes promoting SSIS packages a
snap. Using DTS was more challenging when you for example moved from DEV to
TEST you had to change all your data sources to point to new places - but
SSIS makes that part easy.
If you tie your solutions into VSS and have your coders do all their work
inside of VSS - that will ensure it's managed correctly. Where I work won't
spring for the new Visual Studio Team Edition for DB Professionals - but
that def makes things easier in managing your DB code within the same
solution as your SSIS packages. You can still add the DB into your
solution, but not have ALL the cool features Team Edition offers.
So our developers, by using the VSS integration inside VS, it auto checks
out all the code, whether it be packages or stored procedures. Your
promoting to new environments from Visual Source Safe will endure you are
promoting the right stuff.
It's not that hard - once you get it sorted out and documented and follow
the process - you will be good.
"Carmen" <Carmen@.discussions.microsoft.com> wrote in message
news:B9EAA9CD-B73C-43D3-A314-5E99EE3DC694@.microsoft.com...
> I'm trying to get some info on how other companies are handling BI
> implementations. We have a data warehouse project that we expect will have
> continuos changes. That is, new data sources coming in, more reports, etc.
> That implies new Integration Services packages, new Reporting Services
> reports, changes in tables, view, stored procedures, etc. We also have a 3
> environment installation: Development, QA, Production.
> I would appreciate any info on how other people are handling this. Can you
> manage with only Visual Studio? Is there any third vendor tool anybody
> would
> recommend? The issue is that we could potentially have the 3 environments
> with different versions and we might want to move objects from development
> to
> QA, for example, without just duplicating the 2 environments (we could
> have
> different stages of development and only want to move finished objects).
> Any help is appreciated,
> Carmen.
|||Our approach is to use XMLA scripts (using ascmd utility from SP1) and the
AS syncronize feature (again via XMLA scripts). Works fine - and no
Integration Services required.
Chris
www.activeinterface.com
"Carmen" <Carmen@.discussions.microsoft.com> wrote in message
news:B9EAA9CD-B73C-43D3-A314-5E99EE3DC694@.microsoft.com...
> I'm trying to get some info on how other companies are handling BI
> implementations. We have a data warehouse project that we expect will have
> continuos changes. That is, new data sources coming in, more reports, etc.
> That implies new Integration Services packages, new Reporting Services
> reports, changes in tables, view, stored procedures, etc. We also have a 3
> environment installation: Development, QA, Production.
> I would appreciate any info on how other people are handling this. Can you
> manage with only Visual Studio? Is there any third vendor tool anybody
> would
> recommend? The issue is that we could potentially have the 3 environments
> with different versions and we might want to move objects from development
> to
> QA, for example, without just duplicating the 2 environments (we could
> have
> different stages of development and only want to move finished objects).
> Any help is appreciated,
> Carmen.
|||Chris,
Thanks for the info!
Carmen.
"ChrisHarrington" wrote:

> Our approach is to use XMLA scripts (using ascmd utility from SP1) and the
> AS syncronize feature (again via XMLA scripts). Works fine - and no
> Integration Services required.
> Chris
> www.activeinterface.com
> "Carmen" <Carmen@.discussions.microsoft.com> wrote in message
> news:B9EAA9CD-B73C-43D3-A314-5E99EE3DC694@.microsoft.com...
>
>
|||Joe,
Thanks for the info. I'll definitely investigate the options you mentioned.
Carmen.
"Joe" wrote:

> We have pretty much the exact same setup you do. We use Visual Studio and
> Visual Source Safe to manage all our code. Using the new features for
> managing environments within Visual Studio - makes promoting SSIS packages a
> snap. Using DTS was more challenging when you for example moved from DEV to
> TEST you had to change all your data sources to point to new places - but
> SSIS makes that part easy.
> If you tie your solutions into VSS and have your coders do all their work
> inside of VSS - that will ensure it's managed correctly. Where I work won't
> spring for the new Visual Studio Team Edition for DB Professionals - but
> that def makes things easier in managing your DB code within the same
> solution as your SSIS packages. You can still add the DB into your
> solution, but not have ALL the cool features Team Edition offers.
> So our developers, by using the VSS integration inside VS, it auto checks
> out all the code, whether it be packages or stored procedures. Your
> promoting to new environments from Visual Source Safe will endure you are
> promoting the right stuff.
> It's not that hard - once you get it sorted out and documented and follow
> the process - you will be good.
> "Carmen" <Carmen@.discussions.microsoft.com> wrote in message
> news:B9EAA9CD-B73C-43D3-A314-5E99EE3DC694@.microsoft.com...
>

Best Way to Handle Data Access

This may be a loaded question, but I was wondering if anyone could outline the main options we have available to us for handling data access with ASP.net 2.0 / SQL Server 2005.

I know at one extreme you can simply use the Data Controls like GridView, FormView, and DetailsView, specifying the necessary SQL on a page-by-page basis. At the other extreme, my understanding is that you can basically set up a SQLConnection object, explicitly specify your SQL (or call a stored procedure) and then execute these items from within the code.

Can anyone either outline the main options or point me to a resource that better explains this? Thanks!

Josh

This is an awfully tall order for a forums question. I suggest you take a look at theData Access section of the ASP.NET Developer Center. Or hit upGoogle.|||

Thanks for the prompt reply; this looks like exactly the kind of resource I was looking for. My suspicion is that for relatively straightforward data models you can just use the DataControls and write a minimum of code. I'm guessing that for more sophisitcated apps, you'll have to write a data access layer of classes which maybe calls the Stored Procedures so that you wind up using the ObjectDataSourceControl? I may have made some statements here which really don't make sense.

If I come to any reasonably straightforward or simple conclusions, I'll make sure to summarize them here. Thanks again!

Josh