Newbie needs a hand with SQL2005 Reports

I'm trying to run some reports on SQL 2005, but can't even pass the first step of launching the report builder. I have SQL2005 on my local machine, but the report server is installed on a remote server. I launched SQL Business Intelligence Development Studio, which brings Visual studio, but i keep getting a prompt to enter a connection string. How do i get the connection string, or how do i set up my datasource?

Help!

To answer your question, try the following, but i think you need to configure 'iis', as well as 'reporting services configuration' before hand:

open sql server business intelligence studio
file
new
project
report server project
ok
view
solution explorer
right click reports
add
new item
data source
add
edit
<enter your database details here>

...and so on

look up the microsoft tutorial for creating a basic report in 'sql server business intelligence studio' help

Newbie advise

Hi
I have an ms access background. After hearing all the good stuff about
vb2005/sql2005 I am aiming to switch over. My problem is that I am not very
familiar with features of sql server that are not found in access such as
triggers, stored procedures etc and am not sure when these should be used. I
need to know things like;
- Is it recommended to keep all/most queries as stored procedures and pass
them parameters from vb.net client or is it ok to have the queries in the vb
app?
- Are views essential or just a mater of convenience?
- Triggers, how important are these?
- What about new features of vb2005/sql2005, when should they be used?
...and so on.
Is there a place where I can get some more information, to have a better
idea of how to take the best advantage of these features?
Thanks
Regards
Hi
As most of your questions are generic then reading the SQL 2000 books online
will give you a good idea of where you should be heading. See
http://msdn.microsoft.com/library/de...ortal_7ap1.asp
In general using stored procedures is the best way to manage code and
optimize it's execution. Having Views is not essential, the need for them is
something that will be determined as part of your design process. Similarly
with triggers, your design may require them, but quite often there are
alternatives such as check constraints provide the same functionality and you
may find them easier to manage.
If you have specific issues then you may want to post a new message just
relating to that specific issue.
HTH
John
"John" wrote:

> Hi
> I have an ms access background. After hearing all the good stuff about
> vb2005/sql2005 I am aiming to switch over. My problem is that I am not very
> familiar with features of sql server that are not found in access such as
> triggers, stored procedures etc and am not sure when these should be used. I
> need to know things like;
> - Is it recommended to keep all/most queries as stored procedures and pass
> them parameters from vb.net client or is it ok to have the queries in the vb
> app?
> - Are views essential or just a mater of convenience?
> - Triggers, how important are these?
> - What about new features of vb2005/sql2005, when should they be used?
> ...and so on.
> Is there a place where I can get some more information, to have a better
> idea of how to take the best advantage of these features?
> Thanks
> Regards
>
>
|||What in the wide world of sports is MS SQL and why is it important on some of
the new programs?
Chuck
"John" wrote:

> Hi
> I have an ms access background. After hearing all the good stuff about
> vb2005/sql2005 I am aiming to switch over. My problem is that I am not very
> familiar with features of sql server that are not found in access such as
> triggers, stored procedures etc and am not sure when these should be used. I
> need to know things like;
> - Is it recommended to keep all/most queries as stored procedures and pass
> them parameters from vb.net client or is it ok to have the queries in the vb
> app?
> - Are views essential or just a mater of convenience?
> - Triggers, how important are these?
> - What about new features of vb2005/sql2005, when should they be used?
> ...and so on.
> Is there a place where I can get some more information, to have a better
> idea of how to take the best advantage of these features?
> Thanks
> Regards
>
>

Newbie advise

Hi
I have an ms access background. After hearing all the good stuff about
vb2005/sql2005 I am aiming to switch over. My problem is that I am not very
familiar with features of sql server that are not found in access such as
triggers, stored procedures etc and am not sure when these should be used. I
need to know things like;
- Is it recommended to keep all/most queries as stored procedures and pass
them parameters from vb.net client or is it ok to have the queries in the vb
app?
- Are views essential or just a mater of convenience?
- Triggers, how important are these?
- What about new features of vb2005/sql2005, when should they be used?
...and so on.
Is there a place where I can get some more information, to have a better
idea of how to take the best advantage of these features?
Thanks
RegardsHi
As most of your questions are generic then reading the SQL 2000 books online
will give you a good idea of where you should be heading. See
http://msdn.microsoft.com/library/d...
ap1.asp
In general using stored procedures is the best way to manage code and
optimize it's execution. Having Views is not essential, the need for them is
something that will be determined as part of your design process. Similarly
with triggers, your design may require them, but quite often there are
alternatives such as check constraints provide the same functionality and yo
u
may find them easier to manage.
If you have specific issues then you may want to post a new message just
relating to that specific issue.
HTH
John
"John" wrote:

> Hi
> I have an ms access background. After hearing all the good stuff about
> vb2005/sql2005 I am aiming to switch over. My problem is that I am not ver
y
> familiar with features of sql server that are not found in access such as
> triggers, stored procedures etc and am not sure when these should be used.
I
> need to know things like;
> - Is it recommended to keep all/most queries as stored procedures and pass
> them parameters from vb.net client or is it ok to have the queries in the
vb
> app?
> - Are views essential or just a mater of convenience?
> - Triggers, how important are these?
> - What about new features of vb2005/sql2005, when should they be used?
> ...and so on.
> Is there a place where I can get some more information, to have a better
> idea of how to take the best advantage of these features?
> Thanks
> Regards
>
>|||What in the wide world of sports is MS SQL and why is it important on some o
f
the new programs'
--
Chuck
"John" wrote:

> Hi
> I have an ms access background. After hearing all the good stuff about
> vb2005/sql2005 I am aiming to switch over. My problem is that I am not ver
y
> familiar with features of sql server that are not found in access such as
> triggers, stored procedures etc and am not sure when these should be used.
I
> need to know things like;
> - Is it recommended to keep all/most queries as stored procedures and pass
> them parameters from vb.net client or is it ok to have the queries in the
vb
> app?
> - Are views essential or just a mater of convenience?
> - Triggers, how important are these?
> - What about new features of vb2005/sql2005, when should they be used?
> ...and so on.
> Is there a place where I can get some more information, to have a better
> idea of how to take the best advantage of these features?
> Thanks
> Regards
>
>

Newbie advise

Hi
I have an ms access background. After hearing all the good stuff about
vb2005/sql2005 I am aiming to switch over. My problem is that I am not very
familiar with features of sql server that are not found in access such as
triggers, stored procedures etc and am not sure when these should be used. I
need to know things like;
- Is it recommended to keep all/most queries as stored procedures and pass
them parameters from vb.net client or is it ok to have the queries in the vb
app?
- Are views essential or just a mater of convenience?
- Triggers, how important are these?
- What about new features of vb2005/sql2005, when should they be used?
...and so on.
Is there a place where I can get some more information, to have a better
idea of how to take the best advantage of these features?
Thanks
RegardsHi
As most of your questions are generic then reading the SQL 2000 books online
will give you a good idea of where you should be heading. See
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/startsql/portal_7ap1.asp
In general using stored procedures is the best way to manage code and
optimize it's execution. Having Views is not essential, the need for them is
something that will be determined as part of your design process. Similarly
with triggers, your design may require them, but quite often there are
alternatives such as check constraints provide the same functionality and you
may find them easier to manage.
If you have specific issues then you may want to post a new message just
relating to that specific issue.
HTH
John
"John" wrote:
> Hi
> I have an ms access background. After hearing all the good stuff about
> vb2005/sql2005 I am aiming to switch over. My problem is that I am not very
> familiar with features of sql server that are not found in access such as
> triggers, stored procedures etc and am not sure when these should be used. I
> need to know things like;
> - Is it recommended to keep all/most queries as stored procedures and pass
> them parameters from vb.net client or is it ok to have the queries in the vb
> app?
> - Are views essential or just a mater of convenience?
> - Triggers, how important are these?
> - What about new features of vb2005/sql2005, when should they be used?
> ...and so on.
> Is there a place where I can get some more information, to have a better
> idea of how to take the best advantage of these features?
> Thanks
> Regards
>
>|||What in the wide world of sports is MS SQL and why is it important on some of
the new programs'
--
Chuck
"John" wrote:
> Hi
> I have an ms access background. After hearing all the good stuff about
> vb2005/sql2005 I am aiming to switch over. My problem is that I am not very
> familiar with features of sql server that are not found in access such as
> triggers, stored procedures etc and am not sure when these should be used. I
> need to know things like;
> - Is it recommended to keep all/most queries as stored procedures and pass
> them parameters from vb.net client or is it ok to have the queries in the vb
> app?
> - Are views essential or just a mater of convenience?
> - Triggers, how important are these?
> - What about new features of vb2005/sql2005, when should they be used?
> ...and so on.
> Is there a place where I can get some more information, to have a better
> idea of how to take the best advantage of these features?
> Thanks
> Regards
>
>

Newbie advise

Hi
I have an ms access background. After hearing all the good stuff about
vb2005/sql2005 I am aiming to switch over. My problem is that I am not very
familiar with features of sql server that are not found in access such as
triggers, stored procedures etc and am not sure when these should be used. I
need to know things like;
- Is it recommended to keep all/most queries as stored procedures and pass
them parameters from vb.net client or is it ok to have the queries in the vb
app?
- Are views essential or just a mater of convenience?
- Triggers, how important are these?
- What about new features of vb2005/sql2005, when should they be used?
...and so on.
Is there a place where I can get some more information, to have a better
idea of how to take the best advantage of these features?
Thanks
RegardsHi
As most of your questions are generic then reading the SQL 2000 books online
will give you a good idea of where you should be heading. See
ap1.asp" target="_blank">http://msdn.microsoft.com/library/d...
ap1.asp
In general using stored procedures is the best way to manage code and
optimize it's execution. Having Views is not essential, the need for them is
something that will be determined as part of your design process. Similarly
with triggers, your design may require them, but quite often there are
alternatives such as check constraints provide the same functionality and yo
u
may find them easier to manage.
If you have specific issues then you may want to post a new message just
relating to that specific issue.
HTH
John
"John" wrote:

> Hi
> I have an ms access background. After hearing all the good stuff about
> vb2005/sql2005 I am aiming to switch over. My problem is that I am not ver
y
> familiar with features of sql server that are not found in access such as
> triggers, stored procedures etc and am not sure when these should be used.
I
> need to know things like;
> - Is it recommended to keep all/most queries as stored procedures and pass
> them parameters from vb.net client or is it ok to have the queries in the
vb
> app?
> - Are views essential or just a mater of convenience?
> - Triggers, how important are these?
> - What about new features of vb2005/sql2005, when should they be used?
> ...and so on.
> Is there a place where I can get some more information, to have a better
> idea of how to take the best advantage of these features?
> Thanks
> Regards
>
>|||What in the wide world of sports is MS SQL and why is it important on some o
f
the new programs'
--
Chuck
"John" wrote:

> Hi
> I have an ms access background. After hearing all the good stuff about
> vb2005/sql2005 I am aiming to switch over. My problem is that I am not ver
y
> familiar with features of sql server that are not found in access such as
> triggers, stored procedures etc and am not sure when these should be used.
I
> need to know things like;
> - Is it recommended to keep all/most queries as stored procedures and pass
> them parameters from vb.net client or is it ok to have the queries in the
vb
> app?
> - Are views essential or just a mater of convenience?
> - Triggers, how important are these?
> - What about new features of vb2005/sql2005, when should they be used?
> ...and so on.
> Is there a place where I can get some more information, to have a better
> idea of how to take the best advantage of these features?
> Thanks
> Regards
>
>

newbe to SQL2005 & MSDE

HELP!!
having on trouble installing, just gettting everything connected.
(xp sp2)
First i loaded MSDE, then realized i needed the web admin tool to create the db...but can't get the web admin tool to connnect to anything..
so I took a stab at SQL 2005 Std ed beta....loaded fine, but then realized i need another admin tool to create db so I loaded the xpress manager...again, loads fine, but doesnt'connec to any DB..
why is this so difficult for me....SQL Svr v6 was so much easier with enterprise manager!!!
HELP!!
DonDon, what do you mean by "the web admin tool"? The utility that comes with Visual Studio .NET 2005?
Can you explain what you mean by "but doesn't connect to any DB."? Are you receiving any error messages?