MrEdmundo's questions

This question potentially sits somewhere between ServerFault and DBA Admins but the Domain element of this as led me to put it here.

We have been developing an SOA product and are thinking about different deployment scenarios for our managed servers at client's office. The trigger for this question was discussion about using SQL Server FILESTREAM which requires integrated security

SQL logins will not work with FILESTREAM containers. Only NTFS authentication will work with FILESTREAM containers. FILESTREAM MSDN

At the moment FILESTREAM is the only reason we have for using Integrated Security which makes the potential requirement to deploy Domain Controllers (and their redundancy requirements) to the manager servers unappealing.

I've had a look around and there's a few questions suggesting that you can use WORKGROUPS with Integrated Security.

Integrated Security (SSID?) in a no-domain...

My question is, is there a recommended practice for the scenario described above? Should we give WORKGROUP security a go and see how we get on or is there a reason that's a big no no and we should either use a domain or not use FILESTREAM?

An employee at a client has just got married and as a result they have changed her details, login name et al., in Active Directory (AD).

The problem is SUSER_NAME() in procedures and the NTUSERNAME in SQL Server Profiler still shows her original maiden name.

All connections by this login are made using Windows Authentication and there aren't any indvidual logins set up in SQL Server, access is granted through the "Everyone" AD group.

Is there some kind of cache in SQL Server or a storage of login name somewhere that I don't know about that might be causing this to happen.

I'm informed by the client's IT team that every possible location in AD has been changed to the new name.

I have a SQL Server 2005 log shipping set up, with a primary server and two secondary servers. The process goes like this:

• Primary backs up to independent network drive (not on any of database servers)
• Secondary(s) copy from network drive to local drive
• Secondary(s) restore locally

This has been working well for sometime, however, recently first thing in the morning the larger databases are raising exceptions when backing up the first transaction log of the day.

The exception follows this theme:

BackupDiskFile::RequestDurableMedia: failure on backup device '**_20100927050120.trn'. Operating system error 64(The specified network name is no longer available.)

I've researched this error and any others and it seems that directly backing up to a network drive isn't advised (even though supported) as the network can cause unreliable backups.

That's fine, I'll heed that advice and backup the logs up locally first and then copy them to my independent drive. The reason I want an independent network drive is because I want the backups somewhere off a database server and also to keep them for 3-5 days and the Primary server does not have space for this.

What I would like to know is, what is the best way to go about copying these files from the primary server to the independent drive, so the secondary servers can then copy them to their local drives?

Hi there I'm a developer looking at introducing ClickOnce deployment for an internal .NET Winforms application that will be distributed via the corporate network.

Currently the product roll out and updates are handled by Group Policy however I would like to control the updates via ClickOnce deployment now.

What I would like to know is, how should I initially roll out the package to make sure that all users have got it. Can I use a combination of Group Policy (the roll out) and then rely on the ClickOnce deployment model for any further updates?

Hi there I'm a developer looking at introducing ClickOnce deployment for an internal .NET Winforms application that will be distributed via the corporate network.

Now I would like to deploy this application under the full trust model however in order for that to happen I need to sign the software with a certificate. I can do that with a "test" certificate that has no information of the publisher etc, however that means an extra step will occur on the users workstation where they will have to confirm that the software is OK.

So what I want to know is. is there a way I can get my IT Infrastructure guys to create me a an "internal" certificate from the domains Certificate Authority, or do I have to go and pay for a certificate from somebody like VeriSign?

Thanks

I've got Database Mail set up successfully, I can send test emails, however when I go to set up an alert to be sent by email to an operator I don't have a checkbox to check to say email should be sent.

I've checked the following:

• SQL Agent Alert System has Email set up

• I've restart SQL Agent

• I have a default mail profile

• The profile is a public profile

• Operators are set up (that's where I can't see the email checkbox)

• SQL Server & Agent are running under the same account the SQLMail is set up for

I'm using SQL Server 2005 SP3, if anybody has any thoughts it would be much appreciated.

I am having a problem with one database on my SQL Server 2005 production server.

A number of databases are already set up for mirroring, however when I right click and go to properties in SSMS, on one particular database there is no "Mirroring" property page available.

I have done the normal tasks, such as setting Full Recovery model, running a full backup of the database and backing up the logs.

I can't see that this is a server specific issue as other databases are happily mirroring.

I've looked around and I can't see that I'm missing a setting, any help would be appreciated.

Thanks.

EDIT: This is nothing to do with the Mirror Database yet, I can't get as far as specifying the Mirror Database, I cannot see the "Mirroring" page on the principal.

EDIT: I have managed to set up mirroring using t-sql commands. However I am still unable to see the "Mirroring Page".

UPDATE: This applies to the Transaction Log Shipping option as well. I can successfully set it up in SQL but not through SSMS.

I am setting up a Standby Server for disaster recovery and high availability reasons. My product relies heavily on SQL Jobs, as such, these jobs need to exist (Disabled) on the Standby server.

I have the database replication setup, however I can't find information on techniques for syncing jobs between two servers.

Does anybody do this, and what techniques can you suggest?

I'm currently using SQL Server 2005.

Thanks

I have about 10 databases on a server that I have in Full Recovery model and all are mirrored using Sql Server Mirroring.

My current backup strategy is as follows:

Full Backup 1am

Differential Backup every 2 hours

Transactional Log Backup every 15 minutes

The problem I have is that the differential backups are very slow for a couple of the databases, the diff backup takes roughly 11 minutes on average.

The reason for this is the databases are synced regularly with another system for a large number of rows, thus creating a large number of differences to backup.

On the flip side my transaction log backups are obviously very quick.

This has started to become a problem as at differential backup time the server is struggling with the load, in some cases causing time outs on client machines.

What are the downsides to dropping the differential backup and going with full/ transaction backups? Obviously the restore time would increase with no diff backups but then I do have mirrored databases, so should that be a concern at all?

Any thoughts would be appreciated, the server is currently running Sql Server 2005.

Cheers

Our IT Support Dept. releases an internal software product that I write via group policy.

Is it possible to force an update of a particular group policy software install without asking the users to log off and log back on to their machines?