Search results for query: *

Well I feel a bit foolish here, just realized I wasn't connected to the correct instance of SQL. Once I changed the connection everything worked fine. By running the xp_fixeddrives that's what tipped me off. Thanks!

I have a Windows 2008 R2 X64 Std Edt. and SQL 2008 (Developer Edt.) SP1 server. When I open SSMS and run the following queries: exec xp_cmdshell 'dir C:\' exec xp_cmdshell 'dir F:\' exec xp_cmdshell 'dir E:\' The first two (C: and F:) work fine but the last (E:) gives the message: "The...

I have an user who's been added to the dbo role in a sql 2000 database. When using Sql Server 2005 Management Studio to create the table the table always has the name domain\login_name as the owner of the table. It doesn't make any difference if he adds the dbo to the name before he goes to...

You could try granting execute permissions to the login for the stored procedure: sp_help_log_shipping_monitor

Do you know the sql 'sa' account password. If you login that way you will have sysadmin rights.

All of the sql logins will be orphaned when restoring a backup from one sql server to a different sql server. Your right in your thinking that it has to do with the SIDS since they will end up being different on the server your restoring too. It's a simple process to update the logins by...

I've written the following script to get the size, usedSpace and freeSpace of my databases. However, the results don't always match what SQL Management Studio (2005) shows. I'm sure I'm not taking something into account and any help would be appreciated. if...

I have log shipping between two servers that has been running for several years. I've rebooted both many times without any problems.

If when you set up log shipping and you confiured a Monitory you should be informed if you are missing a log file on the secondary server if it doesn't get there during the allotted time. If you don't have the monitor set up you could use the xp_cmdshell dir to insert the directories files into...

Using: Microsoft SQL Server 2005 SP3 Can you move the .ldf file on the secondary database that's involved in logshipping? If so any special precautions that I need to be aware of?

Guess I'll have to dig a little harder to find out what it is... Thanks

Ok, I'll grant you that, but when pulling the value from the table it does not remove it i.e. SELECT REPLACE(<column_name>, '?', '') FROM <table_name> That select statement fails to remove the "?

I am trying to remove "question marks" (?) from a string of data. Example: SELECT REPLACE(<column_name>, '?', '') FROM <table_name> However it does not remove the question mark (?). I also tried using CHAR(63) in place of '?' and it still doesn't work. Is there something special about "?"...

Figured as much, nice to have some confirmation. I'll probably pull it out. Thanks

I've inherited an application that calls a number of stored procedures. In quite a few of them I've been finding updates that look like the following: UPDATE tbl_name SET field_name = 'some value' FROM tbl_name WITH (NOLOCK) WHERE field_name = 'some other value' I didn't think you could use...

I got it to work by doing the following: 1)Created job to backup the logs on the old server, I didn't want them getting to large 2)Copied them up the new server. 3)Detached the database on old server 4)Copied .mdf/.ldf to new server 5)Re-attached the Database 6)Renamed computers (new server got...

What about detaching the db and re-attaching on the new server would that preserve the log chain? Thanks

We are going to be moving databases from one sql 2005 server to another sql 2005 server as part of a hardware upgrade. One of the databases participates in logshipping. If I backup the database and restore it on the other server will this break logshipping? I realize I will have to redo...

Thanks everyone. I believe this was my problem: "The user account that is used to run the package under SQL Server Agent differs from the original package author." So I logged onto the server as the account that runs SQL Agent Services. Opened the package, resaved, rebuild, re-import, then...

Well guess what, after complaining to Dell (for the umpteenth time) they agreed to completely swapped out the motherboard, RAM and harddrive. After that I had no problems connecting. Thanks everyone for the suggestions I did learn something along the way!