How to make the report show fields in multiple columns?

I am writing a report in SQL server 2005 Reporting service. The report has two parts: first part shows basic information about the client; the second part lists all the softwares the client has. My question is how to make the softwares listed in two columns as shown below?

John Smith

Title: MSTP Location: Main Campus IP:127.0.0.1

Softwares:

Adobe Standard 7.0 Access 5.0

Internet Explore 6.0 Office XP

Any suggestion is appreciated.

There is an option in Crystal Reports -- "Format with multiple columns". I couldn't find the similar configuration in SQL reporting. There is a "Columns" setting in Body Properties, but it doesn't work as making the report in multiple columns. Please help!!

How to make part of the report show in 2 columns?

I am writing a report in SQL server 2005 Reporting service. The report has two parts: first part shows basic information about the client; the second part lists all the softwares the client has. My question is how to make the softwares listed in two columns as shown below?

John Smith

Title: MSTP Location: Main Campus IP:127.0.0.1

Softwares:

Adobe Standard 7.0 Access 5.0

Internet Explore 6.0 Office XP

Any suggestion is appreciated.

In Crystal Reports, there is an option called "format with multiple columns". Could not find the similar configuration in SQL reporting. Please help!

|||

HI, MiaF:

You can manualy select the two columns in the data section. Right click and select merge cells.

|||

Rex,

Can you explain a little bit more please? I wanted the results to show in multiple columns, how can I make it happen by merging cells? Also, when you say merging cells, you mean in a table?

I found this article that seems saying that what I asked is impossible:

http://msdn2.microsoft.com/en-us/library/ms155816.aspx

"A multi-column layout applies to the entire report. It is not possible to specify a multi-column layout on the top half of the report, and a tabular layout on the bottom half of the report. " Is there anyway to get around this? Thanks.

How to link/connect to Oracle server from SQL server 2000?

Greetings,
I want to connet to Oracle databse from SQL server 2000 since I am more comfortable with SQL 2000 client package. The oracle server is 8i or above.
I am running a SQL Server 2000 on a PC with Windows XP OS.
Please help what I need to do and configuration information.

Thank you all in advance.

BPGUgh, I'm not really sure that you want to do this. Try downloading the freeware version of Quest's TOAD for Oracle. That being said, if you really insist:

1. Install the Oracle client on your Windows XP box. Choose the client install.

2. Configure your SQL Net settings for the Oracle connection.

3. Using either Enterprise Manager or Query Analyzer (spaddlinkedserver). Add the Oracle instance to your SQL Server. The server instance on your PC must be up and running. Specific settings for an Oracle server can be found in BOL or Google.

4. Query the linked server by using OPENQUERY or OPENROWSET.

I AM NOT recommending this. The client interface for Oracle as a SQL worksheet which you can use and which is adequate for most things. The freeware version of TOAD (already mentioned) is equally capable (and in some respects superior to QA).

Regards,

hmscott

Greetings,
I want to connet to Oracle databse from SQL server 2000 since I am more comfortable with SQL 2000 client package. The oracle server is 8i or above.
I am running a SQL Server 2000 on a PC with Windows XP OS.
Please help what I need to do and configuration information.

Thank you all in advance.

BPG

How to launch package from client machine, display progress and finally results?

Please help. I'm completely new to SSIS, and I was hoping someone could point me in the right direction(s).

I am developing a winforms client app, and I need to be able to provide the user with the ability to import data in CSV format into our application's database.

I'd like to use SSIS if possible, as long as what I am trying to do isn't near impossible.

I'm thinking of a UI where the user can specify a flat file (CSV) to upload and be processed by an SSIS package on a remote database server.

This package will be responsible for validating the CSV file and inserting data into the database as appropriate.

Is there a way I can:

launch an SSIS package remotely, from a winforms app on the client machine that is not running SQL server (preferably asynchronously) -- and pass it some parameters, including the import file itself

(optionally) provide progress feedback to the client pc to let them know it is being processed

display a nice SSRS report on the client upon completion that tells them exactly what the success/failure of the import was (how many rows processed, which ones failed and why, etc)

Any helpful examples, links, etc would be most appreciated.

Thanks in advance!

1 - How about hosting it on the SQL Server, and start ith through T-SQL. The best way to get the asycn behaviour is to use a job.

How to: Run a Package Using a SQL Server Agent Job
(http://msdn2.microsoft.com/en-us/library/69d3958c-6abc-41ae-8428-312917867c9a.aspx)

2 - You will not get anything back from the job, as it you have no handle back to it. You could turn on logging in your package, perhaps to SQL Server, and then query the table on a polling basis to provide progress to a user.

3 - A combination of SQL logging and some custom logging within the package and you should be able to achieve this.

How to Launch an Oracle SP from SQL Trigger?

I need to know a few things about this..
1. What do I need running or available on SQL Server machine (presuming an Oracle client)
2. Has anyone done this and perhaps can give me some quidance?
3. Any concerns about going from outside a firewall to the Oracle instance?

Architecture is probably going look like this:

SQL -> ON INSERT Trigger -> business logic -> Call Oracle Procedure

Any help is appreciated, thanks!

JTGISDo NOT try to create this Frankenstein monster of database architecture.
The scope of triggers should be limited to their own table if possible, and to their own database at the most. Otherwise, you risk your database stability and data integrity on a chain of technologies stretching across multiple database engines and right through your network.
This is NOT a good idea, and trying to do this sort of thing is what has given triggers a bad name over the years.
I encourage you, instead, to use a trigger on your table to populate a staging table, and then running a frequent batch process (scheduler can run once per minute) to process the data in the staging table and make whatever external calls to the Oracle database are necessary.
The big advantage of this setup is that if you network connection fails or your Oracle database goes down, your SQL Server database is unaffected and continues running merrily along loading data into the staging table, which can then be processed once all systems are up and working again with no loss of data and no loss of service on your SQL Server database.|||Blindman, thanks. I appreciate what you said and it makes sense. Ok, so no trigger other than to populate and use a storage table with the salient records.

What mechanisms exist to push this data into an Oracle table? That is the really important part because I do not want Oracle to have to pull that data. I know Oracle has transparent gateways and access managers for manipulating other data sources. Where do I go to make the same sorts of things happen for SQL server? My biggest constraint is that the data must be no older than a few seconds for this application is analyzing utility data for electrical outages. Optimally I could populate the salient records to an oracle resident table and the oracle side can handle itself (I already have that side built but I am having to "punt" due to problems with an SNMP tool failure that indicates the need for a better, more straight forward architecture).

Any pointers would be appreciated.|||To send the data to Oracle, use either a DTS package or the OPENQUERY function.

How to know a server is running on a specified port?

Dear all,
How to know that whether a server is running on a specified port?
For example, server A is running on port 1888. For a client, how to know
this?
Thanks,
GordonHi ,
Easy way is to check the SQL Server Error Log.
Thanks
Hari
MCDBA
"Gordon" <sdgwedh@.hotmail.com> wrote in message
news:#fyAagwyDHA.2620@.TK2MSFTNGP09.phx.gbl...

quote:

---

> Dear all,
> How to know that whether a server is running on a specified port?
> For example, server A is running on port 1888. For a client, how to know
> this?
> Thanks,
> Gordon
>

---

|||You can check :
1. SQL Errorlog
2. NT application log
3. Run netstat -an
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thanks. But my question is for a client, how to know this.
A client doesn't have permission to check the items you list.
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:nX$xzv9yDHA.3532@.cpmsftngxa07.phx.gbl...

quote:

---

> You can check :
> 1. SQL Errorlog
> 2. NT application log
> 3. Run netstat -an
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>

---

|||Hey Gordon,
Our MDAC 2.6 and greater clients will send a UDP packet to the server to
determine what port the server's listening on as long as it's a Named
Instance.
Otherwise, the NT admin or SQL Admin would have to tell the client what
port they're listening on. Typically, if you were to roll out an
application that was listening on an alternate port, you would either
instruct the clients how to connect or configure an alias for them. The
only other way a client could find this information out would be to port
scan the remote machine.
265808 INF: How to Connect to an SQL Server 2000 Named Instance with the
http://support.microsoft.com/?id=265808
286303 INF: Behavior of SQL Server 2000 Network Library During Dynamic Port
http://support.microsoft.com/?id=286303
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.