SQL Server
-
Hi guys, new to the site, and new to SQL Server. Hope you can help.
My plan as the company business analyst/web developer I wanted to change the reporting techniques, so as I can write SQL using ASP I thought about SQL Server, however, I wanted to house our existing Database on SQL but our software house said they will not support it we have to use AN-OTHER Server.
My question is then, can you have SQL run alongside the normal database and connect to it and still have the efficency and tools etc associated. Or does it defeat the object. I use ODBC at the moment and it's slow when you have to run large table queries.
Any suggestions would be great.
Thanks,
Doogle.
-
To be honest, your post is hard to follow.
From what I'm getting, your company doesn't use SQL Server, but that's the direction you want to go? And you're looking for some reasons, overcome some of the issues you've found to date?
As fr as running SQL alongside the normal database... SQL Server is a relational database management system (RDBMS) just like Oracle and DB2. SQL queries get executed against SQL Server just as heavily with these other products. It's the expected interface.
When you say you use ODBC at the moment and it's slow on large table queries, there are reasons that could be: the table is extremely large (meaning none of the database packages are going to handle it much differently given identical hardware), the query needs tuning, or the method of handling the data in the ASP code needs tuning. We would need more details to help you out in this regard.
K. Brian Kelley
@kbriankelley -
Agree with Brian that this is confusing. Does the existing software run on SQL Server, but you want a second database? Or is it running on other database software?
I've had people want separate SQL Servers for each database. Soemtimes it makes sense for support/performance if one database (or tempdb) is heavily used, but it's not how SQL Server was designed. You can run dozens or hundreds of databases on one server.
-
Thanks and apologies.
I'll try again,
A. Our database provider will not support SQL Server (only a linux or an-other database server)
B. I use ODBC etc to write/create reports but it's slow as the database is in constant use by the rest of the office.
C. I thought about SQL server linked to A. to allow me to create/design reports that could be run by users.
Is this possible or like you said not designed for that.
Thanks in advance.
David.
-
It depends on how you handle the SQL Server setup to the database server (MySQL or what have you). If you already have a contention accessing the data, unless you're periodically retrieving the data from the overloaded server and storing it on SQL Server, you're probably going to run into the same results. A linked server connection will still ultimately depend on the remote server to get the data. You'll just be going from client through the ODBC connection to remote server to a situation with client to SQL Server through an ODBC connection to the remote server.
If you're going to pull the data on a periodic basis then of course the questions about how often you need to refresh, how you store the data, handling conversion of data types, etc. will all need to be dealt with. This raises the question, if your hosting provider won't support SQL Server, is this support going to fall to you?
K. Brian Kelley
@kbriankelley -
Thanks for that,
I was hoping I could pull off the data periodically but didn't think it could be done, that is good news because I would not need the ODBC, could this update be done overnight for example.
Our database provider will not support their own databse if we put it on SQL Server? (Is this normal) They will only support it if it's on an-other.
So in answer to your question, support for SQL Server would ultimately fall to me.
Do you think then in this case it would be a good idea to implement SQL and have an overnight update in place if possible.
Thanks in advance,
David.
-
I was hoping I could pull off the data periodically but didn't think it could be done I have an overnight job that sucks 6GB of data from 3rd party system/database
I would not need the ODBC If you access the 3rd party DB using ODBC, then SQL Server will still use it to retrieve data
could this update be done overnight for example As above
Our database provider will not support their own databse if we put it on SQL Server? I have come across several vendors like this that will not allow it
or charge a large fee (and large maintenance fees) to achieve it 
support for SQL Server would ultimately fall to me. Yep, always happens to innovators
Do you think then in this case it would be a good idea to implement SQL and have an overnight update in place if possible. Depends on what servers/capacity you have. It works great for me
Far away is close at hand in the images of elsewhere.
Anon. -
Thank you for that, I'm just downloading a trial version of SQL, and will continue my quest for researched knowledge. Appreciate your help guys.
------------------------
I will be connected using a 1GB connection. The Server my Network guy tells me is the muts nuts.
Now looking at the points bkelly raised, i.e conversion of data types, storage etc..
Are there wizards to help with this?
Thanks,
David.
-
If you are transferring data then you probably use DTS (Data Transformation Services). DTS has an import/export data wizard and if you point it at the source table, it will allow you to create the destination table or view the sql. I view the CREATE TABLE sql as SQL Server does not always get it right but it is probably a good starting point.
Far away is close at hand in the images of elsewhere.
Anon. -
Thanks a million,
I've just downloaded the trial version and have it for 120 days. Whilst I'm not connecting to our main database I can still query the Northwind DB's etc that come with the trial version can't I?
No doubt I'll be back. Thanks for all your help.
David.
-
Yes, you can use Northwind and pubs.
As far as getting the data from your source... if you're using MySQL make sure myODBC is installed on your SQL Server. If it's something else, you'll have to install the requisite drivers. Then you can use DTS, etc. to make it all happen.
K. Brian Kelley
@kbriankelley -
I have a problem with linked server slowness.
I am trying to insert data from SQL server to Oracle in a Sql server stored procedure. It is working ok, with out any problem except slowness. Some times it may insert upto 5000 rows.
Following is my code in SQL Server SP. Please let me know if there is any alternative method.
CREATE PROCEDURE [dbo].[proc_res_data]
@pid NUMERIC(8), @ppid VARCHAR(1000) AS
DECLARE
@local_sqlstmt NVARCHAR(4000);
SET @local_sqlstmt = 'INSERT INTO bo..USER1.ORA_TABLE'
SET @local_sqlstmt = @local_sqlstmt + '(Oracle table field list)'
SET @local_sqlstmt = @local_sqlstmt + 'SELECT sql table field list'
SET @local_sqlstmt = @local_sqlstmt + ' FROM SQL_TABLE'
SET @local_sqlstmt = @local_sqlstmt + ' WHERE id = ' + CAST(@pid AS VARCHAR)
SET @local_sqlstmt = @local_sqlstmt + ' AND pid IN (' +@ppid + ')'
EXECUTE sp_executesql @local_sqlstmt;
GO
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply