I went through security and added. Checked the owners and added sa and admin account. I just can't seem to figure out what I have missed! DBs detached, copied, and moved from test server to actual network server seems to have not included a "setting" or "configuration". Any ideas? Using Windows Authentication.
The odd is that I can connect and see the Master, but not the attached databases that were added. And yes, they were attached and brought online. The fact that I can see the master tells me that I have the router rules set correctly. I am open to any suggestions. Throw it at me. I have to have missed something obvious.
The problem exists in policy, whether group or user I did not explore further. Installed SQL Server as a local machine with local admin. I completely took the server offline for the initial setup. Reconnected using the suggested username/password as well.
I would have agreed, but I created a new database on the SQL server. I went to a client machine to connect, and once again, the new database does not show in the list. I get the SQL list with master and such.
Truly, this is really bothersome. It is almost as if there is a "scope" problem. Could the GPO affect this? It is an Admin of the domain, but what was given to me was that this admin account has full access. I would think to differ only because ... SQL installs with a local machine admin yes?
Creator/Owner does have special permissions by default on 2008 ... would any portion of this effect the DATA folder where the database has been relocated for attachment?
Lastly, I will try using nonintegrated methods and consider troubleshooting ID values as well per Mycroft Holmes' post.
I have set up a second instance of SSRS 2005 on a Microsoft 2003 server using the custom security extension sample. I have the report server login working with the custom security extension, but cannot seem to get the report manager working with this.
The error I am getting is "The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version."
Now what I thought was that the logon form would display, the admin would login and then be able to add roles, etc. Is this wrong? If so, how is it supposed to work and how to I configure it to work that way?
Below is how I have my report manager config's configured.
I get "The filename, directory name, or volume lable syntax is incorrect" error messsage. I have googled for this error to no avail as to do with mysql.
- My mysql server is up and running with no problem. (Even the mysqldump command works)
-Problem is the same even if I open the command prompt from C:\Program Files\MySQL\MySQL Server 5.5\mysql
-I have tried to remove "", did not help.
- I tried to change / with \ but no success.
Hi all,I have a problem with back up command!
I use this code but it doesnt work:
string constr = @"DataSource=.\SQLEXPRESS;AttachDbFilename=C:\Users\EHSAN\Documents\Visual Studio 2010\Projects\hokm\hokm\App_Data\Database1.mdf;Integrated Security=True;User Instance=True;";
System.Data.SqlClient.SqlConnection con = new System.Data.SqlClient.SqlConnection ();
con.ConnectionString = constr;
comm.CommandText = @"backup database Database1 to disk ='c:\Users\EHSAN\Documents\Visual Studio 2010\Projects\hokm\hokm\DBbackup.bak' with init,stats=10";
comm.Connection = con;
and when I run it, I get this error:
Database 'Database1' does not exist. Make sure that the name is entered correctly.
BACKUP DATABASE is terminating abnormally.
but I use the database1 and I connect it successfully!
what is the problem?
ohhh,it was a typing mistake ,
I still have this error !
and another note is that the DBBackup.bak file doesn't exsit for the first time and I wanted to use the directory.createdirectory,file.exist or directory.exist method but I dont know what name space(s) should I use!
any suggession for my tow questions????
plz help me!
but I use the database1 and I connect it successfully!
Are the connectionstrings the same? Sql Server databases are usually attached to that server, with the server assigning a database-alias to that attached file.
You are attaching a file "on the fly", without specifying an alias. I doubt that Sql Server will use the filename as the database-alias. Add a "Database=database1;" part to your connectionstring, similar to the example given below;
Is it bad practice to open a connection when the application starts, to avoid delays caused by opening the connection each time a query is executed?
Yes. Opening/closing a connection takes very little time. There's a connection-pool that manages the connections.
Another advantage of closing your connection is that you'll be able to handle more client-connections. If your server can handle 25 clients simultaneous, how much would it be able to handle if they only connect when required?
Will the connection stay open, or will SQL server drop it if it is unused for some time?
That'd be easy to test, wouldn't it? Write a console-app and tell us if it indeed stays open as it should; there's only a timeout on creating a connection and on executing statements, not on the lifetime of the connection. That doesn't mean that the server will guarantee an open connection. A single Windows-update could force a reboot and close the connection. Or the cleaning-lady, when she unplugs the server and plugs in her vacuum-cleaner
To minimize the cost of opening connections, ADO.NET uses an optimization technique called connection pooling. [...] It manages connections by keeping alive a set of active connections for each given connection configuration. Whenever a user calls Open on a connection, the pooler looks for an available connection in the pool.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]