Help in Chosing the Software for Reporting Services

Hi All,

I have downloaded SQL Server 2005 Express Edition with Advanced Services SP2 from the following link

http://msdn.microsoft.com/vstudio/express/sql/download/

This I did after hearing Advanced Services provide Reporting Services tool with basic functionalities. After installion I am not able to find the SQL Server Business Intelligence Development Studio. Also there is no provision for installing the Reporting Services.

I already have Visual Studio Express installed.

Could someone tell me what else to download? Also it is asking for another software to be downloaded along with the existing one.

Regards

Karthik

In Visual Studio, when you try and create new projects, do you see a folder called "business intelligence"?|||

I am using Visual Web Developer 2005 Express Edition not Visual Studio. I don't have that option.

I was browsing through many other but couldn't understand clearly what is going wrong. Could you tell me the pre-requisites required for the installation?

|||http://www.microsoft.com/technet/prodtechnol/sql/2005/usingssrswithsqlexpress.mspx|||

Thanks for the link...

After lot of searching I figured out the option to install Reporting Services would not appear till IIS is installed. After doing this it is working fine now.

Could you please let me know if installation of SQL Server 2005 Express Edition with Advanced Services SP2 is possible in Vista Home Basic. Nowhere it is clearly explained if it can be done or not.

Help in choosing SQL Server edition

My company has a website that connects to a sql server (on a different box). I am trying to convince them to get sql server 2005. However, I do not know if SQL Server 2005 Workgroup edition is okay for our needs. Can someone please tell me if it is.

Basically, our setup is the following:

The SQL Server will only have one/two clients - the web server

The SQL Server will have a number of different user accounts though

The SQL Server will have its databases replicated to another SQL Server - both will be 2005

The SQL Server will not have more than 4Gb of RAM

The SQL Server will only have one processor - possible Xeon, and/or Dual Core

The database will not have complicated analysis done on them. The most that will be done are complicated selects which indexing should be able to handle.

We use crystal reports.

Thank you for any help.

Jagdip.

One other big consideration to make in your analysis is the volume of traffic you're going to have to the web server. If your web server is incredibly active and is going to be hammering the SQL server with requests, that will definitely affect your decision.

This page illustrates the differences between the editions:

http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx

Off the bat, it sounds like one feature that the Workgroup edition might lack that you need is Mirroring. Other than that, from what you described, I would think that the Workgroup edition would be fine for you. If you can find a way around the requirement for Mirroring (some other replication scheme--several exist), then you might be able to stick with the Workgroup rather than going with Standard.

Ryan

|||

Hi ya,

You have got a difficult choice. Well if you don't want to have that much and can replicate using your own logic then Sql Server express, the only limit for Database size which is a 4 GB. Workgroup would be better but you have got RAM limit of 3 GB although no limit on actual DB itself.

If you want to be cost effective then use SQL Express, if you can okay with small cost then workgroup

You can read the whole comparision about it from thislink

Hope that helps

Cheers

|||

Thank you both for your replies.

SQL Express is not an option as some of the databases are already over 4Gb.

The volume of traffic is not going to be great. If things go the way they are, we are looking at about 10 users per hour !!!

Thank you for the links as well. I had read these and was still unsure. Database Mirroring sounds good - but we are implementing a failover solution on the web server instead. If the primary web server/database fails over, then the secondaries will become active (using either Neverfail or Doubletake software). We are planning on using merge replication, so this should not be a problem.

The one thing I am worried about is the number of clients that can access the sql server simultaneously. Will the sql server restrict the number of users logged at once?

|||

I can't find anything anywhere about a limit on concurrent users for Workgroup Edition. If any of you SQL guys out there know of one, please chime in. It sounds like you're looking at VERY low usage though, so you should be fine. Were it not for your other requirements, SQL Express would be the perfect solution here. It sounds like you have a good plan in place and like you've got a good idea of which product is the right one for you. The nice thing about SQL is that it's easy to upgrade down the road as well, so if your requirements change in the future you should remain flexible.

|||

Hi ya,

If sql express is out of the question still workgroup would be more then enough as there is no hard core limit on concurrent no of users that can attach to a Sql Server. However it does depend on the actual machine performance which you already explained would be having 2-3 GB.

Hope that helps

Cheers

|||

Brilliant.

I just found out that we do not need to spend ￡300 for a server license of visual sourcesafe - so the money will hopefully go towards a new sql server.

|||Awesome. That worked out great. I'm glad you were able to find the right product for your needs.

Help Import Export Wizard SQL Server 2005

Hi! I have XP sp2, with SQL server 2005 Developer Edition 9.00.3054.00 and also have Microsoft SQL Server Express Edition 9.00.3042.00, well my problem alway I want import data into any server from any data source I recive this message:

TITLE: SQL Server Import and Export Wizard

The operation could not be completed.

ADDITIONAL INFORMATION:

Could not load file or assembly 'System.EnterpriseServices.Wrapper.dll' or one of its dependencies. The system cannot find the file specified. (System.EnterpriseServices)

Could not load file or assembly 'System.EnterpriseServices.Wrapper.dll' or one of its dependencies. The system cannot find the file specified.

The system cannot find the file specified. (Exception from HRESULT: 0x80070002)

BUTTONS:

OK

I have this name space but, I try for many ways and I can't import data in my server, What can I do?

Thanks a lot.

Do you have your Dev edition and Express edition of SQL Server installed on the same machine?

This could be some sort of side by side problem. Could you try to install only the dev edition and then attempt the data import?

Thanks,

Bob

|||

Hi! I find the problem... Well I have install frameWork 1.1 2.0 and 3.0 but in Assemblie cache have System.EnterpriseServices.dll version 1.0 so... There are 2 solutions..

1.- Uninstall FrameWork 1.1 and reinstall 2.0

2.- Use gacutil and register System.EnterpriseServices.dll from version 2.0 <- this work for me.

Thans a lot for every one.

help connecting via vbscript to sql 2005 express edition

Hi guys,
I need to connect to a newly created sql 2005 express edition database.
I tried to recycle the connection string used with sql 2000 server but
it doesn't work anymore:
dbConn.Connectionstring="DRIVER=SQL
Server;Trusted_Connection=Yes;DATABASE=" & sSQLDB & ";SERVER=" &
sSQLServer
database, ssqldb and ssqlserver are variables that correspond to
database names, table names, ecc.
IP and NamedPipes are enabled, so are remote connections (I'm actually
trying this from the same computer).
Any help ?Try specifying:
DRIVER={SQL Server};
Notice the parenthesis.
http://www.connectionstrings.com/
http://www.carlprothman.net/Default.aspx?tabid=81
<zerbie45@.gmail.com> wrote in message
news:1140536817.286087.242470@.g47g2000cwa.googlegroups.com...
> Hi guys,
> I need to connect to a newly created sql 2005 express edition database.
> I tried to recycle the connection string used with sql 2000 server but
> it doesn't work anymore:
> dbConn.Connectionstring="DRIVER=SQL
> Server;Trusted_Connection=Yes;DATABASE=" & sSQLDB & ";SERVER=" &
> sSQLServer
> database, ssqldb and ssqlserver are variables that correspond to
> database names, table names, ecc.
> IP and NamedPipes are enabled, so are remote connections (I'm actually
> trying this from the same computer).
> Any help ?
>|||Where are you trying to connect from? Are you sure the app code is running
as a windows authenticated user that has been granted access to the
database?
Also, I would use (more out of habit than anything):
"Provider=SQLOLEDB.1; Data Source=" & sSQLServer & "; Initial Catalog=" &
sSQLDB & "; Trusted_Connection=Yes;"
And I would try using SQL Authentication first, because you would have had
to do a lot more on purpose in order to get a trusted connection working.
<zerbie45@.gmail.com> wrote in message
news:1140536817.286087.242470@.g47g2000cwa.googlegroups.com...
> Hi guys,
> I need to connect to a newly created sql 2005 express edition database.
> I tried to recycle the connection string used with sql 2000 server but
> it doesn't work anymore:
> dbConn.Connectionstring="DRIVER=SQL
> Server;Trusted_Connection=Yes;DATABASE=" & sSQLDB & ";SERVER=" &
> sSQLServer
> database, ssqldb and ssqlserver are variables that correspond to
> database names, table names, ecc.
> IP and NamedPipes are enabled, so are remote connections (I'm actually
> trying this from the same computer).
> Any help ?
>|||Thanks for your answers. I'll give it a try tomorrow at work.
I'm actually trying to connect from the same machine where sql server
2005 express ed is installed. Sql server is using windows auth (I tried
configuring it to use both windows auth and sql auth). The user is
domain administrator, so it should not be a permission issue.
Thanks again for your attention.

Help , Several Connections , Port : 1433

Environment:
SQL Server Standard Edition
Microsoft Windows NT - 5.2 (3790)
8.00.760 (SP3)
DOS Command : netstat -n . Results as follows
Find several connections about port 1433
Who can help me ? How to resolve the problem ?
Please , thank you .
.
.
.
.
TCP 202.168.198.117:4941 202.181.68.244:1433 FIN_WAIT_1
TCP 202.168.198.117:4942 202.181.71.66:1433 FIN_WAIT_1
TCP 202.168.198.117:4943 202.168.198.116:1433 TIME_WAIT
TCP 202.168.198.117:4945 202.181.68.123:1433 FIN_WAIT_1
TCP 202.168.198.117:4950 202.181.68.123:1433 FIN_WAIT_1
TCP 202.168.198.117:4959 202.181.70.183:1433 FIN_WAIT_1
TCP 202.168.198.117:4959 202.181.92.3:1433 FIN_WAIT_1
TCP 202.168.198.117:4963 202.181.71.66:1433 FIN_WAIT_1
TCP 202.168.198.117:4964 202.181.95.40:1433 FIN_WAIT_1
TCP 202.168.198.117:4966 202.181.87.84:1433 FIN_WAIT_1
TCP 202.168.198.117:4966 202.181.94.137:1433 FIN_WAIT_1
TCP 202.168.198.117:4968 202.181.66.159:1433 FIN_WAIT_1
TCP 202.168.198.117:4970 202.181.71.66:1433 FIN_WAIT_1
TCP 202.168.198.117:4971 202.181.64.246:1433 FIN_WAIT_1
TCP 202.168.198.117:4976 202.181.94.137:1433 FIN_WAIT_1
TCP 202.168.198.117:4984 202.181.95.40:1433 FIN_WAIT_1
TCP 202.168.198.117:4985 202.181.95.40:1433 FIN_WAIT_1
TCP 202.168.198.117:4989 202.181.90.133:1433 FIN_WAIT_1
TCP 202.168.198.117:4992 202.181.66.159:1433 FIN_WAIT_1
TCP 202.168.198.117:4992 202.181.90.133:1433 FIN_WAIT_1
TCP 202.168.198.117:4996 202.181.88.249:1433 FIN_WAIT_1
TCP 202.168.198.117:4999 202.181.87.238:1433 FIN_WAIT_1
.
.
.Hi
You may want to do a netstat -n -o to find what process is trying to connect
to the servers. It sounds like some process is browsing the network for
servers and port 1433 is open on the remote servers.
John
"test" wrote:
>
> Environment:
> SQL Server Standard Edition
> Microsoft Windows NT - 5.2 (3790)
> 8.00.760 (SP3)
>
> DOS Command : netstat -n . Results as follows
> Find several connections about port 1433
>
> Who can help me ? How to resolve the problem ?
> Please , thank you .
>
> ..
> ..
> ..
> ..
> TCP 202.168.198.117:4941 202.181.68.244:1433 FIN_WAIT_1
> TCP 202.168.198.117:4942 202.181.71.66:1433 FIN_WAIT_1
> TCP 202.168.198.117:4943 202.168.198.116:1433 TIME_WAIT
> TCP 202.168.198.117:4945 202.181.68.123:1433 FIN_WAIT_1
> TCP 202.168.198.117:4950 202.181.68.123:1433 FIN_WAIT_1
> TCP 202.168.198.117:4959 202.181.70.183:1433 FIN_WAIT_1
> TCP 202.168.198.117:4959 202.181.92.3:1433 FIN_WAIT_1
> TCP 202.168.198.117:4963 202.181.71.66:1433 FIN_WAIT_1
> TCP 202.168.198.117:4964 202.181.95.40:1433 FIN_WAIT_1
> TCP 202.168.198.117:4966 202.181.87.84:1433 FIN_WAIT_1
> TCP 202.168.198.117:4966 202.181.94.137:1433 FIN_WAIT_1
> TCP 202.168.198.117:4968 202.181.66.159:1433 FIN_WAIT_1
> TCP 202.168.198.117:4970 202.181.71.66:1433 FIN_WAIT_1
> TCP 202.168.198.117:4971 202.181.64.246:1433 FIN_WAIT_1
> TCP 202.168.198.117:4976 202.181.94.137:1433 FIN_WAIT_1
> TCP 202.168.198.117:4984 202.181.95.40:1433 FIN_WAIT_1
> TCP 202.168.198.117:4985 202.181.95.40:1433 FIN_WAIT_1
> TCP 202.168.198.117:4989 202.181.90.133:1433 FIN_WAIT_1
> TCP 202.168.198.117:4992 202.181.66.159:1433 FIN_WAIT_1
> TCP 202.168.198.117:4992 202.181.90.133:1433 FIN_WAIT_1
> TCP 202.168.198.117:4996 202.181.88.249:1433 FIN_WAIT_1
> TCP 202.168.198.117:4999 202.181.87.238:1433 FIN_WAIT_1
> ..
> ..
> ..
>
>
>|||netstat -ano , find : SID = 5664
tasklist , find : 5664 = syswinxp.exe
"syswinxp.exe" maybe a trojan .
Thanks for your help .
"John Bell" <jbellnewsposts@.hotmail.com> ¼¶¼g©ó¶l¥ó·s»D:46CCFA26-F813-4A39-8EF9-EF517084BB6E@.microsoft.com...
> Hi
> You may want to do a netstat -n -o to find what process is trying to
> connect
> to the servers. It sounds like some process is browsing the network for
> servers and port 1433 is open on the remote servers.
> John
> "test" wrote:
>>
>> Environment:
>> SQL Server Standard Edition
>> Microsoft Windows NT - 5.2 (3790)
>> 8.00.760 (SP3)
>>
>> DOS Command : netstat -n . Results as follows
>> Find several connections about port 1433
>>
>> Who can help me ? How to resolve the problem ?
>> Please , thank you .
>>
>> ..
>> ..
>> ..
>> ..
>> TCP 202.168.198.117:4941 202.181.68.244:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4942 202.181.71.66:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4943 202.168.198.116:1433 TIME_WAIT
>> TCP 202.168.198.117:4945 202.181.68.123:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4950 202.181.68.123:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4959 202.181.70.183:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4959 202.181.92.3:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4963 202.181.71.66:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4964 202.181.95.40:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4966 202.181.87.84:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4966 202.181.94.137:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4968 202.181.66.159:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4970 202.181.71.66:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4971 202.181.64.246:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4976 202.181.94.137:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4984 202.181.95.40:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4985 202.181.95.40:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4989 202.181.90.133:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4992 202.181.66.159:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4992 202.181.90.133:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4996 202.181.88.249:1433 FIN_WAIT_1
>> TCP 202.168.198.117:4999 202.181.87.238:1433 FIN_WAIT_1
>> ..
>> ..
>> ..
>>
>>
>>

Help - SQL Server 2005->Compact Edition Replication

Hi All ...

Ihave been following the MS on-line tutorials to get replication setupbetween SQL Server 2005 and SQL Server Compact Edition. I get to thepoint where I run the Configure Web Synchronization and it is runningthrough the process where it is doing the automated configuration ofthe shared directory - assigning users etc.

I have attemptedthis step with a user account that I expressly created for snapshotsand with the Administrator account and get the following error message:

* The operation completed successfully. (Exception from HRESULT: 0x80070000)

Atfirst, I thought this was a rights issue due to the fact that I wasusing an account that I manually created. However, by using theAdministrator account (test only until I can figure this out) thatshould have removed any rights issues associated with accessing theshared directory where the snapshot will reside.

Any help in getting this figured out will be greatly appreciated.

David L. Collison
Any day above ground is a good day!Is the account local admin on the box? Also does the account belong to "sa" group?|||

Administrator is a local account - windows user.

"sa" is the database account - and yes, for test purposes I have the system using "sa". Again, tried a local account that I had created, but got error message. Once I can get working under Administrator and SA, I will then work on getting the local account working correctly.

|||

Whatever account you use should be BOTH local admin on the box as well as sysadmin for the db.

|||

I've made the changes to allow <localaccount>\Administrator to be a sysadmin on the DB. Still get the same error message.

Any other ideas?

|||Can you try re-initializing the snapshot? Also, when you login with the <Administrator> account and browse to the shared folder do you have write access to the folder?|||

As an update:

1. I have disabled Publishing and Distribution for the database and then reconfigured.

2. I have dropped the Snapshot Agent.

3. I have dropped and recreated the virtual folder off the Default Web Site.

4. I have switched between the Administrator account and a specific account I created to manage activity on the snapshots.

5. I have switched between the DB SA account and a specific DB account that I created to manage activity on the snapshots.

6. I have modified the rights of the DOMAIN Users Administrator and the specific account I created to have "Full Control" rights to the snapshot directory and to the virtual directory.

7. I have modified the DB rights of the DB users to have db_owner, db_datareader, db_datawriter.I continue to get the error:The operation completed successfully. (Exception from HRESULT: 0x80070000)(mscorlib)

8. I have attempted to create the virtual directory manually within the Default Web location and assign the rights and then run the wizard to no avail, I get the same error message.

I'm at my wits end on this.

|||

Let me explain. Create one domain account. Add the account to the Administrator group for the box. Also, add the same account to both the SQL Server's (publisher and subscriber) and give it "sa" rights (on both servers). Replication agents copy the files to the local folder and then copy it onto the subscriber. So the account that does all this needs to be local admin as well as "sa" on the SQL box. Grant the rights at the server level. Individual db_owner, db_reader is not required if you give the account "sa" rights at the server level. Also, make sure you are logged into the box where you are setting up replication. Just logging into the SQL server through enterprise manager and setting up replication will not work. You need to be logged onto the server locally. When you are done, check each of the replication jobs. See what account each job is running under. It should be the same domain account that was created earlier.

|||

Dinakar

I've setup the accounts as you have indicated and I'm still getting the error message on the last page of the wizard. I don't want to, but I'm thinking I may have to blow away SQL Server and reinstall everything - which causes me a great deal of heartburn because of all of the development activity I have on this server, not to mention having to reconfigure SQL Server Reporting Services.

Any further ideas before I take this fatalistic step?

Thanks

|||

Folks ...

I finally ended up initiating an incident with Microsoft on this issue and have found a resolution to the problem.

1) You must create a Network share - I was forced to use the NET SHARE command from a Command Prompt - for whatever reason, the system would not recognize the share created via Windows.

2) Next, during the Wizard, you get to the screen labeld "Snapshot Share Access". In this window, I had browsed to the physical directory directory where the snapshot exists - THIS IS NOT VALID (note to MS - remove the Browse function). Here, you must enter the share created in the previous step -\\ComputerName\ShareName

The wizard then completes normally.

Side note, during all of this, MS tech support had me delete the Snapshot and recreate the snapshot. Once I deleted the snapshot and was attempting to recreate the snapshot, I began receiving errors that certain system tables did not exist. I was forced to manually remove the replication functionality by opening SQL Server Management Studio and executing the following:

1) USE <dbName>

2) EXEC sp_removedbreplication '<dbName>'

I was then able to recreate the snapshot.

Hope this helps others out who are having similar issues.

HELP - Connecting SQL Express Edition

I have two machines and same problem.
I installed SQL EE on XP HOME EDITION it is OK !
Localy work OK !
I try to connect from another machine with SQL Server Management Studio and
I can't.
I some how successed to connect with named pipes but TCP/IP is not working.
I turn on all protocols with Menager. Shout down firewall on both machines.
I tried with SQL Native Client from code but nothing.
For now anly named pipes working.
What is wrong ?Have a look at these:
http://www.datamasker.com/SSE2005_NetworkCfg.htm Configuring Express
for Remote Access
https://blogs.msdn.com/sqlexpress/a.../05/415084.aspx
Configuring Remote Access
http://www.kbalertz.com/Feedback_914277.aspx Configuring SQL2005 for
remote access
http://msdn.microsoft.com/library/d...r />
rview.asp
Express Overview
http://msdn2.microsoft.com/en-us/library/ms165672.aspx Comparing Express
with MSDE
http://msdn.microsoft.com/sql/defau... />
erinst.asp
User Instances
http://msdn.microsoft.com/sql/expre...qlexcustapp.asp
Embedding Express in Apps
http://blogs.msdn.com/rogerwolterbl.../13/575974.aspx
Backing up Express
Automating Database maintenance in SQL 2005 Express Edition Part I
http://www.sqldbatips.com/showarticle.asp?ID=27
Automating Database maintenance in SQL 2005 Express Edition Part II
http://www.sqldbatips.com/showarticle.asp?ID=29
Andrew J. Kelly SQL MVP
"Soko" <sokcic@.hotmail.com> wrote in message
news:eQqmarSiGHA.4660@.TK2MSFTNGP03.phx.gbl...
>I have two machines and same problem.
> I installed SQL EE on XP HOME EDITION it is OK !
> Localy work OK !
> I try to connect from another machine with SQL Server Management Studio
> and I can't.
> I some how successed to connect with named pipes but TCP/IP is not
> working.
> I turn on all protocols with Menager. Shout down firewall on both
> machines.
> I tried with SQL Native Client from code but nothing.
> For now anly named pipes working.
> What is wrong ?
>|||Hi Soko,
I have a very similar (if not the same problem). Have you actually solve it?
Thanks
Zib
From http://www.developmentnow.com/g/100...ess-Edition.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com|||SQL Server Express installs as a named instance. Unless you change it the
instance is called <computername>\SQLExpress.
The SQL Server Browser service resolves the name, to the TCP/IP port number.
I suspect the SQL Server Browser service is not running on your computer. If
you start it, then you may be able to connect.
"Soko" <sokcic@.hotmail.com> wrote in message
news:eQqmarSiGHA.4660@.TK2MSFTNGP03.phx.gbl...
>I have two machines and same problem.
> I installed SQL EE on XP HOME EDITION it is OK !
> Localy work OK !
> I try to connect from another machine with SQL Server Management Studio
> and I can't.
> I some how successed to connect with named pipes but TCP/IP is not
> working.
> I turn on all protocols with Menager. Shout down firewall on both
> machines.
> I tried with SQL Native Client from code but nothing.
> For now anly named pipes working.
> What is wrong ?
>