Editor's Note: Send your SQL Server questions to Richard Waymire, program manager for SQL Server development at Microsoft, at questions@sqlmag.com.
Which SQL Server releases run on Windows 2000 Server? If SQL Server 6.5 Service Pack 5a (SP5a) does, what is the installation process?
SQL Server 2000, 7.0, and 6.5 run on Win2K Server. To install SQL Server 6.5, run setup as usual, then immediately apply SP5a. For information about a side effect of installing SQL Server 6.5 on Win2K Server and a solution to the problem, see the Microsoft article "Bug: Install of SQL Server 6.5 on Windows 2000 Modifies DTC Service" at http://support.microsoft.com/support/kb/articles/q249/3/10.asp.
Since I upgraded to SQL Server 7.0, I have encountered a problem in SQL Server Profiler: I am unable to capture SQL statements that have been parameterized. Instead of the parameter @P1, I want the actual value that was used in the query execution. How can I place the substitution without referencing other lines in the trace?
You have to retrieve other parts of the trace, such as the results from SP:StmtCompleted, and put them together, statement first, to capture the full query. You're seeing the result of SQL Server Profiler's method of recovering data from the SQL Server relational engine. We have the same concern in SQL Server 2000. However, we can't make a change at this time because the place where we generate this event doesn't know the values of the parameters inside the engine.
We want to replicate data from our mainframe DB2 database to our SQL Server 7.0 database. Before migrating to SQL Server 7.0, we unloaded the data from the DB2 tables, used FTP to pull the data down to the SQL Server machine, then loaded the data with the bulk copy program (bcp). After we migrated to SQL Server 7.0, we expected to be able to save time by moving the batch files that we currently use with Data Transformation Services (DTS). However, we've been able to move only an incomplete set of data that way. We've connected the SQL Server machine to DB2 using DB2 Connect Enterprise Edition, but when we try to bring decimal values from the mainframe database to the SQL Server database, we receive an error message saying that we're trying to store too much data in the SQL Server column. However, if we bring down a table with no decimal values, the data comes through DB2 Connect successfully.
In trying another avenue to solve the problem, we succeeded in using Microsoft Access to link SQL Server to the DB2 tables through DB2 Connect. We can also use DTS to bring complete data into SQL Server, but transferring the data this way takes 10 times longer than using FTP to bring the file down, load the data into the bcp, then pour the data into the tables. How can we get DTS to bring down the data from DB2 on our mainframe?
I talked to the SQL Server DTS program manager, and we agree that you should stick with your FTP scheme. However, he also noted that SQL Server 2000 has a DTS custom task for FTP. For information about using custom tasks in SQL Server 7.0, see Don Awalt and Brian Lawton, "Constructing DTS Custom Tasks," September 1999. When you use DTS as a batch environment by calling bcp or bulk insert from DTS, you can choose the transformation option. If you don't need transformation, a bulk insert or bcp operation will always be faster.
I'm trying to set up a Data Transformation Services (DTS) package that will copy all the objects and data to our backup disaster recovery server every night, but I keep getting error messages. Should I use DTS to transfer all objects and data? I tried replication, but that process transfers only data and stored procedures. What is the best way to accomplish the backup?
Execute a detach/file copy/attach command by using sp_detach_db, executing a file copy, then executing sp_attach_db for SQL Server 7.0. In SQL Server 2000, you can use the Copy Database Wizard to execute the detach/file copy/attach command.
I need to collect statistics such as transactions per second (tps) on my SQL Server machines for periodic reporting. I've used the Performance Monitor extensively, but I'm unable to produce a set of SQL Server performance numbers that are meaningful to DBAs. Are any utilities available to easily gather these statistics?
One of the Performance Monitor counters for SQL Server collects tps, so using the Performance Monitor is the easiest way to capture this counter. You might consider installing Performance Monitor as a service using the Microsoft Windows NT Server 4.0 Resource Kit or Microsoft Windows 2000 Server Resource Kit as well. I also recommend Steve Adrien DeLuca et al., Microsoft SQL Server 7.0 Performance Tuning Technical Reference (Microsoft Press, 2000) to learn about measuring meaningful performance data with SQL Server.
Prev. page
[1]
2
next page 
